Get early access
Talk to usGet early access
Deploy Rails

Deploy Rails on your own server.

Deploy Rails with Puma on a server you own: db:migrate before each release, zero-downtime rollouts and one flat plan for the whole app.

Get early access →Talk to us
Rails on Beep
Build
Railpack (auto)
Start
bundle exec puma -C config/puma.rb
Port
$PORT, set by Beep
Pre-deploy
bin/rails db:migrate
Health check
/up

Step by step.

  1. Connect a server

    Use Beep Cloud, a server in your own cloud account, or any Ubuntu or Debian VPS. Beep installs its runtime and agent and locks the server down: inbound traffic is denied, and app ports are reachable only from Beep’s edge.

  2. Create a service from your repository

    Pick the GitHub or GitLab repository and the branch to track. In a monorepo, set the root directory for this service; watch paths limit rebuilds to changes that touch it.

  3. Let Beep build it

    Railpack detects Ruby and Rails from your Gemfile, installs gems and precompiles assets. You can override the install, build or start command on the service.

    Start command
    bundle exec puma -C config/puma.rb

  4. Listen on $PORT

    Beep sets PORT for every service unless you set it yourself, and routes traffic from its edge to that port. Bind to 0.0.0.0 so the edge can reach the container.

    config/puma.rb
    port ENV.fetch("PORT", 3000)
# Rails’ default Puma config already does this

  5. Add a database

    Add managed Postgres (16 to 18, with pgvector and PostGIS), Redis or Valkey to the project, then reference its connection string from your service. References resolve at deploy time.

    Environment variables
    DATABASE_URL=${{ postgres.DATABASE_URL }}
RAILS_MASTER_KEY=…

  6. Run migrations before each release

    Set a pre-deploy command. It runs before each release, so the schema is ready before the new version takes traffic.

    Pre-deploy command
    bin/rails db:migrate

  7. Set a health check and deploy

    Set the health check path to /up. Every push to the tracked branch builds and releases; traffic moves to the new version only once it passes, and rolling back re-releases an earlier image without a rebuild.

  8. Add your domain

    Every service starts with a URL on edge.usebeep.sh. When it works, point a CNAME for your domain at Beep; the certificate is issued and renewed for you. Each GitHub pull request also gets its own preview environment, removed when it closes.

Rails tips.

Rails 7.1 and later ship a /up health check route; use it as the health check path.

Add RAILS_MASTER_KEY as a secret variable so credentials decrypt in production.

Run Sidekiq or Solid Queue as a worker service from the same repository.

Rails on Beep, answered.

Straight answers. Anything missing, ask us directly.

Do I need a Dockerfile to deploy Rails?

No. Railpack detects Ruby and Rails from your Gemfile, installs gems and precompiles assets. If your project already has a Dockerfile, you can build with that instead.

Where does the Rails app run?

On the server you connected: Beep Cloud, your own cloud account or any Ubuntu or Debian VPS. Beep bills per server, so databases, workers and previews on the same server add nothing to the plan.

Can I SSH into the server?

No, and that’s deliberate: Beep manages each host end to end so manual changes can’t drift from its setup. To debug, open a shell inside any container from the dashboard, next to its logs and metrics.

Where to run it.

Rails on HetznerHetzner Cloud is some of the best value compute you can rent. Beep turns a Hetzner server into a platform with push-to-deploy, previews, HTTPS and rollbacks.From $16.09/mo→Rails on DigitalOceanAlready on DigitalOcean? Point Beep at a Droplet and get the App Platform experience without per-app pricing: every service on the Droplet shares what you already pay for.From $33.00/mo→Rails on VultrVultr has cloud servers in more than 30 locations. Beep gives any of them the same hardened setup, push-to-deploy and HTTPS, so you can put apps close to your users.From $29.00/mo→Hosting cost calculatorWhat your stack costs on Beep against a per-service platform→

Other guides.

Deploy Next.jsRun your Next.js app as a long-lived Node server on a machine you choose, with previews for every pull request and no per-function billing.→Deploy DjangoDeploy Django with Gunicorn on your own server: migrations before every release, Postgres next to the app, and HTTPS on your domain.→Deploy LaravelDeploy Laravel on your own server: artisan migrate before each release, queue workers and the scheduler as their own services, and Postgres alongside.→Deploy GoDeploy a Go service on your own server: a binary built for you, health-checked releases with no downtime, and HTTPS on your domain.→Deploy DockerBring your Dockerfile or a prebuilt image and run it on your own server, with zero-downtime releases, previews and automatic HTTPS.→Deploy BunDeploy a Bun server on your own machine: installs with Bun, Postgres through Bun’s built-in SQL client, and health-checked releases with no downtime.→Deploy DenoDeploy a Deno app on your own server: tasks from deno.json, npm packages for Postgres, and zero-downtime releases with HTTPS on your domain.→Deploy PhoenixDeploy Phoenix on a server you own: a mix release, migrations before each release, and LiveView sockets served over HTTPS on your domain.→Deploy RustDeploy a Rust service on your own server: a release binary built for you, health-checked rollouts with no downtime, and HTTPS on your domain.→Deploy .NETDeploy an ASP.NET Core app on your own server: EF Core migrations before each release, Postgres alongside, and zero-downtime rollouts.→Deploy Spring BootDeploy a Spring Boot app on your own server: a jar built for you, Flyway migrations on startup, and health-checked releases with no downtime.→

Own your infrastructure again.

Plans from $1 a month, billed per server, never per service.

Early access · We’ll set up your workspace

Or talk to us →