Skip to contentRunning now · Software delivery · internal tool
Stagebox
Environments on demand: pick a template, watch it build, and get a real HTTPS address that removes itself when its time is up.
Try it here
Pick a template, deploy it and open the address you get. Watch the runner's log, then remove the environment or let it expire.
The problem
Every preview, review or test environment means setting up a server, a domain and a certificate by hand, and remembering to take it down afterwards. Often nobody does.
What it does
A visitor picks a template (a static site, a Node API or a PHP app), and Stagebox starts an isolated container from it, routes a new subdomain to it over HTTPS and streams each step of the build. When its time is up, the environment is removed, and nothing is left running that nobody remembers.
Templates only, never uploaded code: each environment runs on a read-only filesystem, with every capability dropped, capped memory and CPU, and no way out to the internet. The service that talks to Docker checks every value again against the allowlist before it acts.
In detail
- Templates
- Static site (nginx), Node API (Node 22), PHP app (PHP 8.4 with SQLite)
- Start-up
- About 2 to 3 seconds per template
- Lifetime
- 30 minutes from the moment it starts, then removed
- Limits per environment
- 128 MB of memory, 0.25 CPU, 64 processes
- Capacity
- 5 environments at once, 1 per visitor, 6 new ones per hour
- Isolation
- Read-only filesystem, every capability dropped, no host mounts, no outbound internet
- Access to Docker
- Only a separate runner, which builds every container from fixed values
- Clean-up
- Ended environments and their logs are deleted after 24 hours
What is in it.
- 01One-click environments from approved templates
- 02A fresh HTTPS address, with no DNS changes
- 03The build log, streamed live
- 04Expiry and clean-up on their own
- 05Memory and CPU limits per environment
- 06Isolated, with no access to the host
Built with
- Laravel
- Docker
- React