1. Write
Define a flow in plain TypeScript and keep your logic in one place.
trigger: { type: 'webhook' } Write flows locally. Deploy them globally. No infrastructure.
Trigora is the developer-first runtime for event-driven backend systems. Define flows in code, test them locally with real data, and deploy the same flows globally as production-ready event handlers.
Triggered by webhooks, scheduled jobs, or queues - all in one global runtime.
One runtime for all your backend events.
Webhook-first today. Scheduling, queues, retries, and more are on the roadmap.
import { defineFlow } from '@trigora/sdk';
export default defineFlow({
id: 'stripe-payment',
trigger: { type: 'webhook' },
async run(event, ctx) {
const body = event.payload.body;
if (body?.type === 'payment_intent.succeeded') {
await ctx.log.info('💰 Payment received', {
amount: body.data.object.amount_received / 100,
email: body.data.object.receipt_email,
});
}
},
}); $ trigora deploy
✔ Deployment complete
Endpoint
https://acme.trigora.dev/stripe-payment
✓ Ready to receive events The loop
A complete backend workflow, reduced to one simple loop.
Define a flow in plain TypeScript and keep your logic in one place.
trigger: { type: 'webhook' } Deploy the exact same flow globally with one command.
trigora deploy Trigger it from webhooks, schedules, or queues.
webhook • schedule • queue [INFO] 💰 Payment received {
amount: 20,
email: "user@example.com"
} No servers. No API setup. Just code.
Why Trigora
Today, even simple event-driven workflows are spread across APIs, cron jobs, queues, and glue code.
Existing options push developers toward low-level serverless infrastructure, rigid workflow engines, or no-code tools that break down when real logic shows up.
Existing options
With Trigora
Use cases
Start with one flow. Replace a surprising amount of backend glue.
Receive Stripe, GitHub, Slack, or custom events without setting up an API server.
Run backend tasks on demand for support tools, admin actions, and one-off workflows.
Schedule logic cleanly instead of scattering jobs across infrastructure.
Turn backend workflows into simple functions that run when something happens.
Test locally with real payloads before touching production.
Use the same code locally and in production without managing infrastructure.
How it works
Trigora acts as the event ingress, orchestration, and execution layer for your backend.
Connect flows to external providers like Stripe, GitHub, and Slack, or trigger them from your own internal services without building separate API routes, cron workers, and queue consumers.
Write a function with a trigger and a run() method.
Use real payloads and iterate instantly with a fast local loop.
Push the same flow to production with one command.
Run the flow from webhooks today, with more trigger types coming next.
Trigora is local-first today, and is growing into a full runtime for event-driven backend systems.
Platform vision
Trigora is evolving into a complete platform for event-driven systems.
Manage flows, inspect deployments, and understand what is running across your runtime.
Track logs, failures, retries, and deployment state across your flows.
Webhooks first. Scheduling, queues, and more coming next.
Deploy flows to a global edge runtime that runs close to your events with no infrastructure setup.
Expose production endpoints on your own domain as Trigora grows into a full deployment platform.
Secure environment variables, per-flow configuration, and multi-environment support for real production workflows.
Get started
Deploy your first flow in minutes and see the full loop end to end.
Early development. Webhook-first. More platform features coming soon.