Live demo
Try Fadebox without installing it
A running Fadebox with a sample team, Acme, where you can deploy. Everyone signs in with the same login.
- Username
demo- Password
demo
Things to try
Deploy Quick Start
In the project Acme, create an instance of the Quick Start environment and deploy it. It runs whoami and is up in a few seconds. Open its URL: it is public, so anyone you send it to can open it too.
Deploy PetClinic
The Spring PetClinic app on PostgreSQL. Watch the order as it deploys: PostgreSQL starts in wave 0 and is healthy before the app starts in wave 1, wired to the database by reference. Then open the app. Its URL is for the project's members only, so it asks you to sign in first, with the same login.
Look inside an instance
Open an instance for its status, its logs and its deploy history.
Read a template
On Templates, press View in PetClinic's row to read its Compose and files, read-only.
Connect your AI assistant
Any MCP client can connect. With Claude Code:
claude mcp add --transport http fadebox https://demo.fadebox.io/mcpYour client discovers Fadebox's OAuth sign-in and opens it in a browser; sign in as demo / demo. More on the MCP endpoint →
Good to know
- The account is shared.Other visitors see what you deploy, and can stop it.
- Instances are short-lived.Quick Start instances live 30 minutes, PetClinic instances one hour. At most five Quick Start and three PetClinic instances run at once; when they are all taken, stop one or wait for one to expire.
- A short tour starts when you sign in.It takes about a minute. Replay it from Take the tour in the user menu.
- You are a deployer.You can create, deploy, stop and delete instances and read templates, but not compose or edit environments or templates. The admin pages (runtimes, users, system, audit log) are not visible.
To run Fadebox on your own hosts, install it self-hosted. For a walkthrough on your own stack, talk to us about a guided demo.