Experiments

Turn on the features that are still new, for every team at once.

Settings -> Deplo -> Experiments, instance admins only.

Some features are still new. Each one has a switch here, off until an instance admin turns it on. On, it is offered to every team. Off, nobody sees it.

Every experiment is in beta: it may still change, and it is not recommended for production yet. Try it, and share your feedback on our GitHub.

ExperimentWhat it addsWhere it shows up
Cron jobsA command on a schedule inside an app or a databaseSettings -> Advanced of each app and database
Zero-downtime deploysThe old version stays online until the new one is readySettings -> Advanced of each app
Pull requestsA deploy and a URL for every pull requestSettings -> Pull requests of each GitHub app
Server clustersSeveral servers that act as oneSettings -> Servers -> Add
TunnelsThe panel and domains served through Cloudflare TunnelPanel access, and Add domain
Canary releasesEvery new version of Deplo, before it is marked stableSettings -> Deplo -> Updates

Turn one on

  • On is for every team. Each app still opts in on its own: turning on Cron jobs shows the switch on every app, and starts no job.
  • Each row says what uses it now, like 2 apps, 5 jobs.
  • Activity records who turned it on or off, and when.

Turn one off

Cron jobs, Zero-downtime deploys and Pull requests pause. Nothing is deleted, and each app keeps its own switch, so turning the experiment back on picks up where it left off.

ExperimentWhile it is off
Cron jobsNo job runs, on any app or database
Zero-downtime deploysA deploy replaces the running version in place, with a short gap
Pull requestsNew pull requests and new pushes are ignored. A live preview stays until its pull request closes

Turning one off while something uses it asks first, and says what stops. Canary releases asks the other way round, when you turn it on: canary versions can break the panel or a server's agent. Off, only stable versions show up as updates, and a canary already installed stays until the next stable one.

Server clusters and Tunnels can't be turned off while one exists. The switch says what is left: delete the cluster, turn off the panel's tunnel under Advanced, or remove the domains served through a tunnel.

After an update

The update that adds Experiments turns on every experiment the instance already uses:

ExperimentOn after the update when
Cron jobsAn app or a database has Cron jobs on
Zero-downtime deploysAn app has it on
Pull requestsAn app has previews on, or a preview is live
Server clustersA cluster exists
TunnelsThe panel or a domain is served through a tunnel
Canary releasesIt was on before, under Advanced

A new install starts with all six off.

Good to know

  • Off, a feature is hidden everywhere: menus, settings and search. A link to one of its pages says it is not turned on, and shows an admin the way here.
  • The API and MCP follow the same switch. A call that would turn on or create something is refused with a message that names this page. MCP has list_experiments and set_experiment.
  • A migration brings cron jobs and previews across paused while their experiment is off.
  • An app on a cluster gets its own tunnel from Server clusters, not from Tunnels.

Did this page help you?

On this page