Past the demo, where the real app lives
AI builders are great at the flashy front end, then you hit the cliff. Orbit builds a web app with real sessions, a database behind it, and live data that updates the page the moment something changes.
Acme
Overview
Revenue
$48k
Orders
1,284
Active
312
The cliff
Great for a demo. Then there's a giant cliff past there.
“Great at hackathons, demos, or basic front-ends, but there's a giant cliff past there.” The prototype looks alive until you click, and nothing holds. Teams say the quiet part out loud: “we discard the code from these tools.” A screenshot that moves isn't an app. What runs is.
How it works
An app that holds state, not just a screen that moves.
Orbit builds the full client, keeps the user signed in, reads and writes a real database, and pushes changes to the page live. The interactive part isn't faked. It runs on a server that remembers.
Sessions, auth, and a database, not localStorage
Users sign in and stay signed in. What they save is written to a Postgres database and scoped to them, so the app remembers across visits and devices. State lives on the server, not in a browser tab that forgets.
Live data, pushed the moment it changes
On the reactive tier, a websocket pushes fresh rows to every open page the instant a workflow writes them. A dashboard updates itself, a queue moves without a refresh. No polling, no reload button.
Honest edge: push happens on write from your logic, not from arbitrary client-defined live queries.
A REST API under every screen
The same datamodel that backs your screens exposes a REST API with an OpenAPI schema, so the app you see and the API you'd integrate against are the same thing, always in sync.
Where it fits
The screen is the front of a real app.
What you see reads from your data model, runs your workflows, and ships on managed infrastructure. The interface isn't the app. It's the front of one.
Build the app, not the demo of one
Describe what it should do, and watch Orbit build a web app that actually runs, state and all.