How omg.dev works
omg.dev is the complete stack for web apps, games and native iOS and Android apps. Build in your omg.dev Computer, in chat or on your own machine, and omg.dev runs the result.
Build it
- omg.dev Computer. Your cloud workspace. Coding agents such as Claude Code and Codex build your app in it. You follow along and give instructions from a laptop or a phone. Start at omg.dev.
- ChatGPT or Claude. Describe the app in chat. See Build apps from ChatGPT or Claude.
- Your machine or CI. Write the code yourself with the SDK, then run
omg deploy. See Deploy with omg deploy.
All three paths end at the same hosting.
Your app
- Web apps and games are Vite and React projects. The omg.dev SDK adds a database, sign-in and live updates.
- Native apps use Expo. One codebase runs on iOS, Android and the web.
Where it runs
Static apps have no database and no server code. omg.dev stores the files once and serves them from the nearest Cloudflare edge. There is no server to start, so the first visit is as fast as any other.
Apps with data get their own sandbox: an isolated Firecracker microVM that runs your server code next to a SQLite database. When an app has no visits, its sandbox goes to sleep with its memory and data saved. The next visit wakes it from memory.
You do not choose between the two. If the project has a schema.ts with
collections or a functions/ folder, it gets a sandbox. If not, it is static.
Native builds for Android run in the omg.dev cloud and produce an app you can install.
Use the sandboxes directly
The sandboxes that run apps are also available to your own code. Create, sleep, wake and fork them over HTTP with the Sandbox API.