For developers
The whole stack, with only your service swapped
One command stands up a full copy of the application on the team's Docker hosts, with your branch's build in place of one service and everything else at the versions the team runs. No laptop that cannot fit the stack, no waiting for staging.
Rather run your service in your IDE, with a debugger? Local development against the same stack →
What you get
Productive on day one
A new developer deploys the real application from the same definition everyone uses, before lunch.
Redeploys that keep your data
Push again and only the service that changed restarts. The database and the search index stay as they were.
Yours until you are done
The copy is personal: colleagues see it, nobody else stops it, and it expires by itself once abandoned.
How it works
- 01
The team defines the stack once
Services as Compose templates, composed into an environment. Whoever maintains it opens your service for image tags, and nothing else.
What deployers may change → - 02
One command for your copy
fadebox instance up shop-1842 --wait --tag web=feature-shop-1842, and ninety seconds later there is a URL.
The deploy loop → - 03
Push, redeploy, repeat
Every redeploy converges the running stack instead of rebuilding it, and resets the expiry clock while you are working.
Redeploy restarts only what changed →
Other use cases
Running on your own host in 10 minutes
Two containers. Works offline. Your data never leaves your infra.