Suspending Non-Production Environments and Databases

Non-production Environments — dev, staging, demo, and any other
non-production stage — can be automatically suspended during
off-hours to reduce infrastructure costs, on both AWS and GCP.
Databases can be put on their own schedule in the same way.

A suspended Environment has its workloads scaled to zero — no pods
running, no compute costs. Resuming restores all workloads.

Scheduled suspension can reduce non-production infrastructure costs by up
to 40%.

Scheduling automatic suspension

Suspension and resumption are configured in the Environment's
Override section in SVIEW. All times are in UTC.

1. Open the Environment from your dashboard.
2. Navigate to the Override section.
3. Configure the SUSPEND schedule:
   • Schedule type: Cron (recurring) or Date (one-time)
   • Every: recurrence interval (e.g. daily)
   • At: UTC time when the Environment should suspend
4. Configure the RESUME schedule with the same fields.
5. Click Save.

Example: Suspend at 20:00 UTC daily, resume at 07:00 UTC — the
Environment runs only during business hours.

Suspending immediately

1. Open the Environment in SVIEW.
2. In the Override section, enable Suspend now and click Save.

To clear it and return to the normal schedule: deselect Suspend now
and click Save.

Resuming a suspended Environment

1. Open the Environment in SVIEW.
2. Click Resume now in the Override section and click Save.

After the temporary need has passed, deselect Resume now and save to
restore automatic scheduling.

Resuming typically takes 2–5 minutes for all Components to reach a
healthy state.

What happens during suspension

• All application workloads scale to zero — no running containers.
• Persistent storage remains intact — data is not lost.
• The Kubernetes control plane stays running — only workloads are
  suspended.
• Databases (RDS, Cloud SQL) remain running unless separately
  scheduled — see below.

Suspending databases separately

Individual database instances can also be put on their own suspend/resume
schedule, independently of the Environment they belong to — supported for
AWS RDS, GCP Cloud SQL, PostgreSQL, and MySQL.

1. Open the database instance in SVIEW.
2. Configure its own SUSPEND / RESUME schedule in the Override
   section, the same way as for an Environment.

Production Environments

Automatic suspension should only be configured for non-production
Environments. If you accidentally suspend a production Environment, use
Resume now immediately or raise a request.

Related articles

• Key Concepts
• SVIEW — Overview