I've been building side projects for a few years and the part I hate isn't the building — it's the hour you lose after. Dockerfile, cloud console, environment variables, reverse proxy, SSL. The app works on localhost but getting it to a URL someone else can open is a whole separate project.
I came across SuperNinja last week. Every app runs on a dedicated VM — not a sandboxed session or a container that spins down, but a real virtual machine that stays up and runs a server. It behaves like a developer sitting at a terminal, not a code generator handing you a zip file.
I tested it with JetSet AI, a flight search app in their App Store. Typed "cheapest flight from New York to London next Friday" and got back live results with real pricing. It's must be using a travel API but it is clearly not mocked data (I compared to Google Flights).
I didn't write anything. The agent provisioned the VM, wrote the integration, tested it and deployed it — 60 seconds from clicking Deploy to a live URL. (To be honest: the app was pre-built in the App Store so 60s is deploy time not build time)
Most AI tools give you a codebase. This gives you a running computer and that's extremely useful.
What I've been doing since: using SuperNinja to extend JetSet AI — adding filters, tweaking the UI, changing how results display. You describe what you want and the agent edits the running app. No redeployment, no touching the repo. Changes are live immediately.
If you want to try it: https://bit.ly/4besn7l
Happy to answer questions — I've only been using it a week so I'll be honest about what I don't know.
ptak_dev•6h ago
The VM runs a Node server that handles the natural language parsing, calls the API and formats the results.
The persistent VM thing is also worth explaining because it's not obvious why it matters. Most serverless setups spin up on request and tear down after. That means no persistent state, cold start latency and you can't install arbitrary system dependencies. The VM sidesteps all of that — it's just a computer that stays on.
Real limitations I want to be upfront about: — The App Store is curated right now. You can customise after deploying but you can't push arbitrary code yet. — It's not open source.
One thing I didn't mention in the post: you can build your own apps on top of this infrastructure. The VM handles the runtime — you bring the logic. There's also multi-agent support if you're building something with multiple moving parts.
Genuinely curious whether the VM-per-app model feels like the right primitive to people here, or whether it's solving a problem most developers don't actually have.