Migrations Migrating from Heroku, Render, Hatchbox or Cloud 66? We move your production app within 48 hours →

For maintainers

One button in your README.

Let your users deploy your project to a server in their own cloud account, in a few clicks, without writing a deploy guide for every platform.

Deploy button

Create your button.

Paste your repository URL. The link opens Railyard's new-app form with your repository filled in, and your user picks a server they own.

Deploy to Railyard

Markdown
[![Deploy to Railyard](https://app.railyard.run/deploy/badge)](https://app.railyard.run/deploy?repo=https%3A%2F%2Fgithub.com%2Fyou%2Fyour-project)
HTML
<a href="https://app.railyard.run/deploy?repo=https%3A%2F%2Fgithub.com%2Fyou%2Fyour-project"><img src="https://app.railyard.run/deploy/badge" alt="Deploy to Railyard"></a>

Detection

What Railyard reads from your repo.

For a GitHub repository, Railyard inspects the files at the branch you link to before anything is built. Try it on the homepage with your own repo to see what it finds.

How it builds

A Dockerfile if there is one. Otherwise Railyard detects your language and framework automatically and picks a matching runtime version, with no config needed.

Its processes

Web and worker processes declared in your project, plus common background workers such as Sidekiq, Solid Queue or Celery.

What it needs

Databases and services your project depends on, such as Postgres, MySQL, Redis, MongoDB, Elasticsearch, RabbitMQ, Memcached, ClickHouse or InfluxDB. Railyard adds them and wires the connection strings.

Its settings

The environment variables your project documents, so the deploy form asks for the ones that matter.

A published image

If you already publish your project to GitHub Container Registry or Docker Hub, Railyard can run that image instead of building.

railyard.yml

Override detection with railyard.yml.

Put a railyard.yml at the root of your repository and Railyard uses it over what it detected: the build method, the port, a release command that runs before each release, a seed command, your processes, default variables and add-ons. Every key is optional. An app.json or render.yaml is read too.

Deploy button docs → Browse templates →

railyard.yml
build: dockerfile            # auto or dockerfile
runtime:
  container_port: 3000
  release_command: bin/rails db:migrate
  seed_command: bin/rails db:seed
  processes:
    web: bin/rails server
    worker: bundle exec sidekiq
env:
  RAILS_LOG_TO_STDOUT: "1"
addons: [postgres, redis]

Ready to own your production infrastructure?

Start your 14-day trial or book a 48-hour migration call.

14-day trial on every plan. One flat price per team, your servers at your provider's price.

Theme
Colors