Docs · Getting Started · Examples · Changelog · Discord

Run code when things happen.

A hosted runtime for event-driven TypeScript workflows.

Get Started · Docs · Dashboard

---

Write a flow. Deploy it. Done.

import { defineFlow } from '@trigora/sdk';

export default defineFlow({
  id: 'hello',
  trigger: { type: 'webhook' },
  async run(event, ctx) {
    await ctx.log.info('Received event', event.payload);
    return { ok: true, received: event.payload };
  },
});

npx trigora init
npx trigora dev hello
npx trigora deploy hello

Your flow is live at:

https://<workspace>.trigora.dev/hello

Event happens → flow executes.
Schedule fires → flow executes.
Job enters queue → flow executes.

---

Build your first flow

One model for webhooks, schedules, and background work.

Webhook — receive HTTP events

import { defineFlow } from '@trigora/sdk';

export default defineFlow({
  id: 'stripe-webhook',
  trigger: { type: 'webhook', route: '/hooks/stripe' },
  async run(event, ctx) {
    await ctx.log.info('Stripe event', event.payload);
  },
});

Cron — run on a schedule

import { defineFlow } from '@trigora/sdk';

export default defineFlow({
  id: 'nightly-sync',
  trigger: { type: 'cron', cron: '0 2 * * *' },
  async run(event, ctx) {
    await ctx.log.info('Nightly sync started');
  },
});

Queue — process background jobs

import { defineFlow } from '@trigora/sdk';

export default defineFlow({
  id: 'process-image',
  trigger: { type: 'queue', queue: 'image-processing' },
  async run(event, ctx) {
    await ctx.log.info('Processing message', {
      queue: event.queue,
      messageId: event.messageId,
      payload: event.payload,
    });
  },
});

See a production-style example: Stripe checkout.

---

Why Trigora?

Writing a webhook handler, scheduled job, or queue consumer is usually the easy part. Running it in production means dealing with deployments, secrets, logs, infrastructure, scheduling, workers, and observability.

Trigora handles the operational layer so you can focus on the code that runs when something happens.

---

Everything around your workflow, included

Webhooks — Receive HTTP events through hosted endpoints.

Cron — Run workflows on a schedule.

Queues — Run asynchronous background work without managing workers.

Deployments — Ship flows directly from the CLI.

Secrets — Manage environment secrets from the control plane.

Observability — Inspect invocations and structured logs.

Custom domains — Expose webhook flows through your own domain.

---

Quick start

npm install trigora @trigora/sdk

If installed locally, run commands with npx trigora.

Local loop

npx trigora init
npx trigora dev hello

curl -X POST http://localhost:5252 \
  -H "Content-Type: application/json" \
  -d '{"message":"Hello from Trigora"}'

npx trigora deploy hello

---

Packages

Package	Description
trigora	CLI for local development, deploy, flows, queues, secrets, and invocations
@trigora/sdk	Flow authoring with defineFlow()
@trigora/contracts	Shared public contracts and API types

This repository contains the public Trigora packages and examples. The hosted control plane and runtime are deployed separately.

---

Documentation

• Docs
• Getting Started
• Deploy
• Webhook Endpoints
• Cron
• Queues
• Custom Domains
• CLI Reference
• API Reference

Website: trigora.dev · Dashboard: app.trigora.dev

---

License

MIT