Link PRs to previews and release reviews
Connect
SPIRITT
RailwayShip on Railway
Keep releases healthy
SPIRITT creates Railway services, manages environment configuration, and carries releases through deployment checks. Give it the operating rules to investigate failures and recover services using deployment evidence.
What you can do with Railway.
Releases carried through
Move from a connected repository or image to a deployed service, configured domain, and checked deployment status without losing the last mile.
Recovery with evidence
Use build, runtime, and HTTP logs alongside deployment history to choose between a restart, redeploy, or eligible rollback.
Environments with a purpose
Build staging and preview workflows around Railway environments, staged changes, service variables, and persistent storage.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for shipping applications and operating your Railway services.
02
Connect Railway
Connect Railway with access to the projects and environments you want SPIRITT to operate. Define production and recovery boundaries.
03
Delegate an outcome
Ask SPIRITT to launch a service, run release checks, or recover failed deployments. It executes the mission and verifies the result.
Hand over a mission.
Choose a mission. Make it yours.
Put Railway to work.
Give your releases an operator
Questions
Railway, with SPIRITT.
01What Railway resources can SPIRITT create and operate?+
SPIRITT can create projects, services, environments, domains, and persistent volumes. It can manage variables and environment-specific service settings, deploy connected repositories or images, and stage or deploy complete templates. Logs and metrics let it check what happened after a change.
02What access does the Railway connection need?+
Railway supports API key and OAuth connections. The connected credentials need access to the target workspace, project, and environment. Repository-backed missions also depend on the repositories Railway can access. Set the target environments and permitted production actions as part of the mission.
03Can SPIRITT keep watch over deployments and recover failures?+
Yes. It can schedule deployment checks, collect bounded build, runtime, and HTTP evidence, and apply an authorized recovery policy. It can cancel queued or building deployments, restart a running or crashed deployment, redeploy a selected release, or restore an eligible previous deployment.
04How can Railway work connect to GitHub, Slack, and Linear?+
SPIRITT can use Railway's repository access and associated pull-request information to connect code context to deployments. With the other apps connected, it can publish release results in Slack and carry failure evidence into Linear issues, then check later Railway deployments for recovery.
05What custom systems can SPIRITT build around Railway?+
Useful builds include a release console, a preview-environment desk, and a capacity dashboard. These can combine project and service inventories with deployment status, domains, logs, and resource or HTTP metrics. SPIRITT can also provision Railway services from repositories, images, or templates for the application being launched.
06How are restart, redeploy, and rollback different?+
A restart reuses the existing deployment image without rebuilding or creating a deployment. A redeploy creates a new deployment using the selected deployment's exact code and build/deploy configuration. A rollback restores a previous deployment's image and custom variables without rebuilding, subject to rollback eligibility.