Detected for you
AutoWe read package.json and set up the build and the server. No build settings to fill in.
- SvelteKit
- Next.js
- Nuxt
- Remix
- Astro
- SolidStart
- Qwik
- Angular
- Vite · React
- Vite · Vue
- Node.js server
- Static sites
Push a repo and it goes live. We detect your framework, build it, and only call it live once it stays up. Anything else runs from your Dockerfile.
We tell you exactly which one your project uses before anything builds.
We read package.json and set up the build and the server. No build settings to fill in.
One-click templates are on the way: start WordPress or PocketBase and get a running app with its own storage.
If it builds in Docker, it runs here, exactly as you wrote it.
The same four steps for every project, each one logged so you can see where it stopped.
Connect GitHub or paste a Git URL. Choose the branch that deploys.
We read package.json or use your Dockerfile as written. Node 20 unless
you pick another.
npm ci when there's a lockfile, then your build.
We only call it live after the container stays up for 10 seconds. If it runs out of memory, we say so.
Managed from the same console as your domain and email.
Every address gets a certificate as soon as it points at your app, and it renews itself — including the default address every project gets.
A second copy of your app on its own address, so you can try a change before customers see it.
Postgres, MySQL and Redis on the same node, with credentials injected into your app.
Browse, edit, upload and delete files in your project from the console.
Run a command on a schedule, with the last run and whether it succeeded shown in the console.
Your first site, done right
₦24,000 billed yearly · save ₦6,000
Beast mode for growing brands
₦62,000 billed yearly · save ₦16,000
Mission-critical, fully managed
₦144,000 billed yearly · save ₦36,000
Every limit, in one table.
Connect GitHub or paste a Git URL and your project builds from that repo.
SvelteKit, Next.js, Nuxt, Remix, Astro, SolidStart, Qwik, Angular, Vite (React and Vue), plain Node.js servers and static sites, from your package.json. Anything else runs from a Dockerfile in your repo.
Yes, through a Dockerfile. We build it exactly as written and run your CMD or ENTRYPOINT. They are not auto-detected today.
After the build, we watch the container for 10 seconds and only mark it live if it stays up. If it crashes or runs out of memory, the deploy tells you which, and what to change.
The console shows your usage against your plan, so you can see where you stand.
Connect a repo in a minute. Your first deploy tells you exactly what it did.