Trigora | Event-driven backend runtime for developers.<br>Search docs... Ctrl ⌘ K Search docs

Esc

Search docs by title, guide, API reference, or keyword.

Why Use Cases How It Works Pricing GitHub Docs Get Started<br>Get Started

Hosted control plane is live

Run code when things happen.

Write flows locally. Deploy them globally. No infrastructure.

Trigora is the developer-first runtime for event-driven backend systems. Define<br>webhook and cron flows in code, test them locally, and deploy the same flows globally.

One runtime for all your backend events.

Get Started

Read Docs

Create a workspace, generate a deploy token, and deploy your first hosted flow.

Every workspace gets hosted endpoints with custom routing. Pro workspaces can connect<br>custom domains like events.acme.com.

stripe-webhook.ts

export default defineFlow({<br>id: 'stripe-webhook',<br>trigger: {<br>type: 'webhook',<br>route: '/hooks/stripe'<br>},<br>async run(event, ctx) {<br>// handle Stripe event<br>}); → https://acme.trigora.dev/hooks/stripe

Deploy<br>hosted runtime

✔ deployed stripe-webhook<br>Webhook endpoints

Default

https://acme.trigora.dev/hooks/stripe

Custom domain

https://events.acme.com/hooks/stripe

See full Stripe example →

The loop

From function to running flow in seconds

A complete backend workflow, reduced to one simple loop.

1. Write

Define a flow in plain TypeScript and keep your logic in one place.

trigger: { type: 'webhook' }<br>2. Schedule

Use the same flow model for webhooks or scheduled work.

cron: '0 2 * * *'<br>3. Deploy

Ship to a workspace-scoped production URL — no tunnels or extra infra.

trigora deploy

Runtime output

[INFO] 💰 Payment received {<br>amount: 20,<br>email: "[email protected]"<br>No servers. No API setup. Just code.

Why Trigora

Backend logic is more complicated than it should be

Today, even simple event-driven workflows are spread across APIs, cron jobs, queues, and<br>glue code.

Existing options push developers toward low-level serverless infrastructure, rigid<br>workflow engines, or no-code tools that break down when real logic shows up.

Existing options

wire low-level serverless infrastructure<br>adopt a rigid workflow engine<br>accept no-code limits on logic<br>split APIs, cron jobs, queues, and workers apart<br>debug across multiple systems

With Trigora

define flows in code<br>test locally with real payloads<br>deploy once to a global runtime<br>handle webhooks and cron schedules together<br>keep business logic close to your app

Use cases

Built for real workflows

Start with one flow. Replace a surprising amount of backend glue.

Handle webhooks<br>Receive Stripe, GitHub, Slack, or custom events without setting up an API server.

Automate internal operations<br>Run backend tasks on demand for support tools, admin actions, and one-off workflows.

Replace cron jobs<br>Run scheduled backend logic as hosted cron flows with logs, secrets, and the same deploy path as webhooks.

Build event-driven backends<br>Turn backend workflows into simple functions that run when something happens.

Prototype faster<br>Test locally with real payloads before touching production.

Deploy globally<br>Use the same code locally and in production with hosted endpoints, custom routes, and custom domains on Pro.

How it works

A simpler model for backend workflows

Trigora acts as the event ingress, orchestration, and execution layer for your backend.<br>Connect flows to Stripe, GitHub, Slack, or your own services without separate API routes<br>and cron workers.

Create a workspace, connect the CLI, deploy to production endpoints, and operate flows<br>from one hosted control plane.

Create a workspace<br>Set up your hosted workspace in the dashboard and organize flows for production.

Connect the CLI<br>Authenticate the local CLI with your hosted workspace.

Deploy globally<br>Ship flows to hosted endpoints, then attach a custom domain when you need one.

Operate flows<br>Monitor invocations, runtime output, and failures from the dashboard.

Develop locally with the CLI, then use the hosted control plane to deploy and operate<br>flows in production.

Platform vision

More than a CLI

Trigora is a complete platform for event-driven systems — CLI for development, dashboard<br>for operations.

Dashboard<br>Manage workspaces, deploy tokens, flows, secrets, invocations, and logs.

Execution history<br>Track invocations, failures, and runtime output across your hosted flows.

Composable triggers<br>Build flows around webhooks, schedules, and future queue-driven workflows in one runtime model.

Global execution<br>Deploy flows to a global edge runtime that runs close to your events with no infrastructure setup.

Workspace endpoints<br>Deploy flows to production-ready endpoints like acme.trigora.dev/hooks/stripe, or connect your own domain such as events.acme.com.

Production workflows<br>Secure secrets, isolated configuration, deployment environments, and operational controls for real production systems.

SECURITY & OWNERSHIP

You own your code — always<br>Trigora does not store your source files<br>Build artifacts are used only to run,...