How do I deploy Basecut Agent on Railway?

You can deploy Basecut Agent on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: basecut-agent-161e6730, or click "Get template help" for this template for more assistance.

Deploy and Host Basecut Agent on Railway

Basecut Agent is a self-hosted worker that continuously polls Basecut for snapshot jobs, executes extraction workflows against your PostgreSQL database, and writes outputs to configured storage. It runs in your infrastructure, keeps credentials in your environment, and reports heartbeats for reliable job orchestration.

About Hosting Basecut Agent

Hosting Basecut Agent on Railway means running the agent as a long-lived container service with secure runtime configuration. You deploy the agent image, set BASECUT_API_KEY and BASECUT_DATABASE_URL, and optionally provide cloud credentials for S3, GCS, or S3-compatible outputs. Railway manages runtime health, restarts failed processes, and lets you scale replicas as workload increases. For production environments, use a least-privilege read-only database user and private network paths where possible. You can also tune polling and heartbeat behavior with agent flags to balance responsiveness and API overhead.

Common Use Cases

Continuous production snapshot extraction to S3/GCS/S3-compatible storage for lower-environment refreshes
Running snapshot jobs against private/VPC databases without exposing credentials externally
Always-on agent workers for CI and test pipelines that need fresh, realistic data

Dependencies for Basecut Agent Hosting

Basecut TEAM plan with an organization API key (BASECUT_API_KEY)
Reachable PostgreSQL connection string (BASECUT_DATABASE_URL) and optional cloud storage credentials (AWS/GCP) for remote outputs

Deployment Dependencies

Basecut Agent CLI reference: https://docs.basecut.dev/cli-reference/agent
Self-hosted agent deployment guide: https://docs.basecut.dev/advanced/agent-deployment
Railway environment variables: https://docs.railway.com/guides/variables

Implementation Details

Railway service image

ghcr.io/basecuthq/basecut-agent:latest

Required variables

BASECUT_API_KEY=bc_live_xxx BASECUT_DATABASE_URL=postgresql://readonly_user:***@db-host:5432/app_db

Optional runtime args (set as command arguments)

--poll-interval=5s --heartbeat-interval=1m

Why Deploy Basecut Agent 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 Basecut Agent 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.