Deploy and Host Starter Stopper on Railway

This template allows you to start and stop a Railway service on a schedule, so it only runs when you need it. Handy for development environments, demos, or services you only use during the day.

This template creates two Railway Functions: one starts your service, the other stops it. Each runs at its scheduled time, calls the Railway API, and exits. Compared to an always-on scheduler, you avoid spending compute just waiting for the next scheduled action, while also saving compute when your target service is stopped.

About Hosting Starter Stopper

By default, the service starts at 06:00 UTC and stops at 21:00 UTC, every day. You can change both times in the cron settings.

You’ll need three variables: TARGET_SERVICE_ID: the ID of the service to start and stop. TARGET_ENVIRONMENT_ID: the ID of the environment it belongs to. RAILWAY_PROJECT_TOKEN: a Project Token for the target project, scoped to that environment.

Common Use Cases

Staging environments: Run your staging app during working hours and shut it down overnight
Demo apps: Keep a demo available during scheduled sessions without running it around the clock.
Internal tools: Start a dashboard or admin panel when your team needs it, then stop it after hours.

Dependencies for Starter Stopper Hosting

This template has no dependencies, you only need to provide the service to start and stop.

Implementation Details

[Include any code snippets or implementation details. This section is optional. Exclude if nothing to add.]

Why Deploy Starter Stopper on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Starter Stopper on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.