Skip to main content
A staging or demo environment you use a few hours a week doesn’t need to run the rest of the time. reliant forge env stop suspends a hosted environment: its workloads stop running and stop costing compute, and the environment keeps its URL, its release and its database’s data. reliant forge env start brings it back on the same release, with nothing to rebuild or redeploy. Hosting has no autoscaling and never stops an idle environment for you. Stopping is something you do by hand, and Stopping and deleting an environment compares it with env delete.

Before you begin

1

Stop the environment

Run it from the project, naming the environment:
terminal
Every deployment of the environment is set to suspended, the managed database included. OBSERVED is where the platform is now; it converges over the next few minutes. Stopping is never refused.
2

Check that it stopped

env status compares what the platform runs with the environment’s release:
terminal
UserSuspended confirms it, and the API’s URL now answers 503. The release stays bound: v9.9.1 is still what the environment runs once it is started.
3

Start it again

terminal
Starting takes a few minutes while the database and the workloads come back. The platform can refuse a start your organization isn’t entitled to, for example because of a billing condition. It then starts nothing and prints the reason and the fix.
4

Verify the data came back

The database was suspended, not deleted, so the API reconnects to the same data:
terminal
reliant forge env status prod reports 2 match, 0 drifted, 0 missing against the same release.
To stop one workload and leave the rest running, pass --target <name> to env stop and env start. The names are the DEPLOYMENT column above.

What this does not do

  • Nothing stops automatically. No idle timer, schedule or scale-to-zero suspends an environment for you. Run env stop yourself, or from a script you run.
  • It is not env down. reliant forge env down stops the processes env up started on your machine. env stop and env start act only on a hosted environment and refuse one that isn’t hosted.
  • It is not a delete. To remove the environment, use reliant forge env delete, which also deletes its database and its data unless you pass --keep-data. See Stopping and deleting an environment.

Troubleshooting

env stop --wait can time out while the environment is already stopped. The stop request was accepted, and the platform keeps converging. Run reliant forge env status prod: when it reports UserSuspended, the environment is stopped.
The organization isn’t entitled to run the environment, usually because of billing. Resolve the condition the message names (billing is in Reliant → Settings → Billing, or ask an org admin), then run reliant forge env start prod again. Nothing was started.

Next steps

Preview environments

Environments per pull request that expire on their own.

Detect configuration drift

Check that what runs is what you declared.

Inside Reliant hosting

How the platform runs, suspends and meters an environment.

env stop reference

Every flag of env stop, env start and env delete.