Concepts
Four ideas cover everything in Nebulae: the nebula, the plan, the pool, and the two ways you drive them.
Nebulae
A nebula is a real Ubuntu LTS container — not a sandbox. Each one comes up with:
- An automatic HTTPS URL at
<project>.<you>.spaceport.host, wildcard certificate already issued. - Root, a shell, and SSH you can toggle on per container.
- Its own CouchDB 3 instance with generated admin credentials.
- Nginx and a JVM preinstalled.
If it runs on Linux, it runs in a nebula.
Projects
A nebula hosts one or more projects. Each project is a repo that runs as its own supervised service, on its own port, reachable at its own subdomain. A fresh deploy makes a one-project nebula; add more to the same box whenever you like. See Deploy from the CLI.
Plans
Your plan sets how much compute you can run. Every plan uses the same one-click deployment system; higher ranks raise the ceilings and add support and backups.
Pools
From Commander up, resources are a shared pool rather than a fixed slice per container. Your nebulae draw vCPU, RAM and storage from the pool as they need it, so a busy container can use more while an idle one uses less — you're never stranded by a too-small per-box limit.
| Plan | Containers | vCPU | RAM | Storage |
|---|---|---|---|---|
| Ensign | 1 | 2 vCPU | 2 GB | 20 GB |
| Commander | 3 | 6 shared | 8 GB pool | 80 GB pool |
| Captain | 10 | 20 shared | 32 GB pool | 250 GB pool |
| Planetary | ∞ | 48 dedicated | 128 GB | 1 TB + 4 TB |
See the full breakdown on the pricing page.
Two ways to drive it
Everything you can do, you can do from either surface:
- The CLI — deploy a GitHub repo with one command, like Vercel. Best when your code already lives in a repo. See Deploy from the CLI.
- The dashboard — spin up a container in the browser, then work on it directly over SSH or an IDE. Best when you want a live box to build on. See Work over SSH.