Your project runs on your machine. Put it online.
Drop the folder. We install it, build it and serve it — on real Kubernetes, over HTTPS, in about a minute. Nothing to configure.
From archive to a live address
Every step is explicit. When something is refused, you are told which rule it hit and where.
What you drop decides what you get
One thing today — but it works end to end, not on paper.
Workers (bots, scheduled tasks), HTTP services and MCP servers are written and tested, but none has run in production yet. They ship once proven, not before.
Your code runs once, in a sandbox
Building means running the install scripts of your whole dependency tree. That is treated as what it is.
The build runs under gVisor, non-root, with no service-account token: the pod cannot talk to Kubernetes at all.
The internet on 80/443 so npm works, and nothing private. A build that could reach Vault or another tenant would be worth more than the build.
The produced archive goes back through the same boundary as your upload. The build script's own checks are a service to you; they guarantee us nothing.
Private beta, and we say so
No three-column grid for a product with no billing. Here is what there is.
The real limits