Skip to main content

Fadebox 1.0

The 1.0 line: fadebox/fadebox:1.0 follows its newest release, and the 1.0 docs describe every release on it. Moving between releases is covered in Upgrading.

1.0.4 — 2026-09-03​

An agent can author templates. Fifteen new MCP tools cover the loop from a draft to a proven template: validate_template checks a Compose spec against the same parser a save uses and answers with what Fadebox understood; the create, update and file tools save it; a test run deploys the template alone and its logs say why a service died; and a catalog repository can be registered and re-read after every push. The check behind the first tool is also an endpoint, POST /api/template-validation, open to any signed-in account. See Authoring templates with an agent.

Fourteen more catalog entries — valkey, memcached, nats, clickhouse, prometheus, grafana, jaeger, redpanda, mosquitto, keycloak-mysql, meilisearch, smtp4dev, adminer and mockoon — 33 in all, each proved healthy on Docker before it was published. See The official catalog.

Upgrade notes. None.

1.0.3 — 2026-09-02​

The CLI comes from your installation. Every server serves the CLI it was released with at /cli/fadebox-linux-amd64, linked from the sidebar footer. After an upgrade, the same download is the new version. See Install.

Per-provider sign-out switch. Each OIDC provider has a new End the provider session on sign-out switch. On, the default, keeps single sign-out. Off signs you out of Fadebox only and leaves the provider session alone — useful for Entra tenants. See Single sign-on.

The image is on Docker Hub as fadebox/fadebox, with the same tags as before. The installation compose file uses it.

Upgrade notes. One migration (V002) adds a column to the provider table and runs on startup. Nothing else to do.

1.0.2 — 2026-09-01​

System images from your own registry. Administration → System (or FADEBOX_IMAGE_REGISTRY) sets a registry prefix for the images Fadebox pulls for itself: the ingress stack's Traefik and socket proxy. For hosts that cannot reach Docker Hub. See Hosts that cannot reach Docker Hub.

Upgrade notes. None.

1.0.1 — 2026-08-31​

Upgrade to Team from the License page. Administration → License opens the store's checkout with your installation ID filled in, or copies a purchase link for someone else. The store address is FADEBOX_LICENSE_STORE_URL. See Upgrading from the License page.

Disabled runtimes do not count against the cap. On the Free tier, disable local to use a remote runtime instead. See Remote runtimes.

Release line tags. fadebox/fadebox:1.0 follows the newest 1.0.x release; latest follows the newest release of any line. See Installation.

Upgrade notes. No schema change. If your compose file says latest, change it to 1.0.

1.0.0 — 2026-08-29​

The first release: a self-hosted orchestrator for ephemeral environments on Docker. See What is Fadebox?.

  • Templates — services as Compose YAML, from the bundled catalog, a git repository or a starter.
  • Environments — templates composed into a stack, with image tags, cloning, blueprints, start-order waves and git value sources.
  • Instances — isolated running copies: deploy, watch, logs, stop, expire.
  • Runtimes — local or remote Docker daemons, each with a managed ingress that gives every instance its own URL.
  • Access — global and project roles, groups, OIDC single sign-on, API keys and an audit log.
  • CLI for pipelines and an MCP endpoint for agents.
  • Licensing — Free tier without a key; Team and Enterprise by a signed file, verified locally.