Trigora | Event-driven backend runtime for developers.
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 webhook and cron flows in code, test them locally, and deploy the same flows globally.
One runtime for all your backend events.
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 custom domains like events.acme.com.
stripe-webhook.ts
``` export default defineFlow({ id: 'stripe-webhook', trigger: { type: 'webhook', route: '/hooks/stripe' }, async run(event, ctx) { // handle Stripe event } }); ```
→https://acme.trigora.dev/hooks/stripe
Deploy hosted runtime
`✔ deployed stripe-webhook`
Webhook endpoints
Default
https://acme.trigora.dev/hooks/stripe
Custom domain
https://events.acme.com/hooks/stripe
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' }`
2. Schedule
Use the same flow model for webhooks or scheduled work.
`cron: '0 2 * * *'`
3. Deploy
Ship to a workspace-scoped production URL — no tunnels or extra infra.
`trigora deploy`
Runtime output
``` [INFO] 💰 Payment received { amount: 20, email: "[email protected]" } ```
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 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
- wire low-level serverless infrastructure
- adopt a rigid workflow engine
- accept no-code limits on logic
- split APIs, cron jobs, queues, and workers apart
- debug across multiple systems
With Trigora
- define flows in code
- test locally with real payloads
- deploy once to a global runtime
- handle webhooks and cron schedules together
- 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
Receive Stripe, GitHub, Slack, or custom events without setting up an API server.
Automate internal operations
Run backend tasks on demand for support tools, admin actions, and one-off workflows.
Replace cron jobs
Run scheduled backend logic as hosted cron flows with logs, secrets, and the same deploy path as webhooks.
Build event-driven backends
Turn backend workflows into simple functions that run when something happens.
Prototype faster
Test locally with real payloads before touching production.
Deploy globally
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. Connect flows to Stripe, GitHub, Slack, or your own services without separate API routes and cron workers.
Create a workspace, connect the CLI, deploy to production endpoints, and operate flows from one hosted control plane.
1
Create a workspace
Set up your hosted workspace in the dashboard and organize flows for production.
2
Connect the CLI
Authenticate the local CLI with your hosted workspace.
3
Deploy globally
Ship flows to hosted endpoints, then attach a custom domain when you need one.
4
Operate flows
Monitor invocations, runtime output, and failures from the dashboard.
Develop locally with the CLI, then use the hosted control plane to deploy and operate flows in production.
Platform vision
More than a CLI
Trigora is a complete platform for event-driven systems — CLI for development, dashboard for operations.
Dashboard
Manage workspaces, deploy tokens, flows, secrets, invocations, and logs.
Execution history
Track invocations, failures, and runtime output across your hosted flows.
Composable triggers
Build flows around webhooks, schedules, and future queue-driven workflows in one runtime model.
Global execution
Deploy flows to a global edge runtime that runs close to your events with no infrastructure setup.
Workspace endpoints
Deploy flows to production-ready endpoints like acme.trigora.dev/hooks/stripe, or connect your own domain such as events.acme.com.
Production workflows
Secure secrets, isolated configuration, deployment environments, and operational controls for real production systems.
SECURITY & OWNERSHIP
- You own your code — always
- Trigora does not store your source files
- Build artifacts are used only to run, redeploy, or roll back your flows
- Logs are temporary and exist only for debugging
Get started
Stop wiring infrastructure.Start writing logic.
Sign in, deploy your first flow, and see the full hosted loop end to end.
Create a workspace, generate a deploy token, and deploy your first hosted flow.
Questions or feedback? Join the Discord community.