Backend logic you can follow.
Build the logic your app needs. Orbit runs each workflow on your data, on a server, and lets you see what happened at every step.
Free to build. Your first live app is free too, on your own domain.

The building blocks
Add backend logic without writing code.
Build a workflow step by step. Each step does one job, then passes the work to the next step, so the whole process is easy to follow.
Trigger
Starts the run, on a schedule or on demand.
Agent
Hands a step to Claude or GPT, with your data as the context.
Branch
Splits the path on a condition, so different cases go different ways.
Integration
Calls out to Gmail, GitHub, Linear, Resend, and Google Calendar.
Code
For the step no node covers, run a snippet in a locked-down sandbox with no access to the outside.
Data
Reads and writes your app's database, the same records your screens use.
Where it runs
It runs on your server, on a schedule.
Your workflow runs in your deployed app, even when your browser is closed. It can run on a schedule, use your app's data, and retry automatically if something fails.
Straight answers
Workflow questions.
Do I have to write code?
No. You build the workflow by placing nodes on a canvas. A code node is there if you want it, but most workflows never need one.
Where does a workflow run?
On a server, as part of your deployed app, not in a browser tab. It runs on a schedule and keeps working whether or not you are online.
Which services can it reach?
Five you can act through today: Gmail, Google Calendar, GitHub, Linear, and Resend. Stripe is read-only, for financial signals. Agent steps call Claude or GPT, and a Code step can reach any HTTP API.
Can I see what a workflow did?
Yes. Open any run and see it move step by step, with what each step took in and put out, how long it took, and where it stopped if it did.
What happens if a step fails?
Orbit retries the workflow from a durable queue, backing off between tries, up to twenty times. A run that cannot finish is logged with the error, not lost.
Start
Put your logic on the canvas.
Lay out your first workflow, and watch it run on a server.