Skip to main content
Deploy your agents to Railway with a starter railway.json and a single deploy command.
Starter templates ship in the git checkout, not in the PyPI wheel (MANIFEST.in excludes infra/). Run create from a monorepo checkout, or set PRAISONAI_STARTERS_ROOT / PRAISONAI_INFRA_ROOT.

​
Quick Start

1

Scaffold the project

The starter drops railway.json and agents.yaml into the current directory.
2

Authenticate with Railway

Log in with the Railway CLI.
3

Deploy

Push the service to Railway.

​
How It Works

The command shells out to railway up --detach.

​
Command Options

​
Starter railway.json

The railway starter deploys the prebuilt image (no Dockerfile needed).
Set the service’s source image to ghcr.io/mervinpraison/praisonai in Railway settings (pin a version tag for production). The image already exposes /health on port 8005.

​
Doctor

Check Railway readiness before deploying.
deploy doctor --provider railway now checks the Railway CLI — previously this reported “Unknown provider”.

​
Best Practices

Use a released ghcr.io/mervinpraison/praisonai tag instead of latest in the Railway service settings.
Add OPENAI_API_KEY and other secrets as service variables in the Railway dashboard, not in Git.
praisonai deploy destroy is not automated for Railway — remove the service in the Railway dashboard or run railway down manually.

Deploy Templates

Scaffold the railway starter.

Deploy to Render

Another one-command PaaS target.