Cut cloud spend with Coder workspace autostop and schedule defaults
At a glance
Coder admin docs let template owners set default autostop, activity bumps, and optional dormancy so idle workspaces stop (and eventually delete) instead of burning compute. This workflow is listed under sponsor, devtools, finops, platform.
- Agents / tools
- Coder
Building a tool for these workflows? See weekly rates.
What they did
Open the template's schedule settings. Set Default autostop (how long a workspace runs without activity before Coder stops it) and Activity bump (default 1 hour) so VS Code, JetBrains, Terminal, or SSH sessions extend the deadline. Optionally allow users to define their own autostart/autostop schedules and restrict which weekdays autostart runs. On licensed plans, configure Failure cleanup, Dormancy threshold/auto-deletion, Autostop requirement (forced stops on Daily/Saturday/Sunday every 1–16 weeks ignoring open connections), and User quiet hours via CODER_QUIET_HOURS_DEFAULT_SCHEDULE.
Worth knowing
Failure cleanup, dormancy, autostop requirement, and quiet hours are Premium. Autostop requirement is disabled while a template still uses deprecated max lifetime—pick one. Quiet hours default to UTC 00:00; set CODER_ALLOW_CUSTOM_QUIET_HOURS=false to force the org default.
