---
title: "Deploy Ruby on Rails with your AI in 2026: the MCP guide"
url: https://while.sh/en/guides/deploy-rails/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Deploy a Ruby on Rails app and its PostgreSQL database with your AI, over MCP (2026)

Your Rails app is leaving Heroku, or never went there. Connected to while over MCP, your AI deploys it in France, with its PostgreSQL database backed up every day and a ready-made Rails Dockerfile.

> **The short version.** Over MCP, your AI deploys your Rails app and its PostgreSQL database with while, in France, with a Rails Dockerfile ready to build. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A Ruby on Rails 7.1 app or newer, with its Gemfile.lock.
- An AI that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.

## Step 1: Give your AI this message

Open your AI in your app's folder, and paste this message into it:

```text titre="The message to give your AI"
Connect to while with my account (while.sh/agents), then put my app on while.
```

Without an account, your AI deploys your app as a trial, in one request. To keep it, open the link it gives you and create your account.

With your account, your AI adds while's MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn't open, type /mcp, choose while, then Authenticate. On that page, choose your app, or "A new app", then click Authorize.

## Step 2: Open your app

Your AI gives you your app's address, for example `https://mon-appli.while.cloud`, over HTTPS.

## What your AI does

It writes while.yaml at the root of your app:

```yaml titre="while.yaml"
apiVersion: while/v1
project: mon-appli
services:
  - name: web
    port: 8080
    health:
      path: /up
    resources:
      memory: 512Mi
databases:
  - name: main
```

Rails is detected from its Gemfile, and your AI receives a Dockerfile ready to build: several stages, precompiled static assets, and a user without administrator rights. Your AI adds it to your app. If your app already has the Rails Dockerfile, your AI adapts it, starting with the port.

At startup, `bin/rails db:prepare` creates the database or applies the migrations (source 2), then Rails serves your pages. The Rails `/up` route tells while that your app is ready (source 1). Your AI also generates the `SECRET_KEY_BASE` key and stores it in while's vault. With Rails 8, it connects the Solid Cache, Solid Queue and Solid Cable databases to the same PostgreSQL database.


<figure class="illus"><img src="/illustrations/guide-cadre-production-1200.webp" srcset="/illustrations/guide-cadre-production-768.webp 768w, /illustrations/guide-cadre-production-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="What your AI does to put a Ruby on Rails app and its PostgreSQL database in production on while: the while.yaml file, the build and tests, the HTTPS address, the PostgreSQL database backed up every day and a person's approval, in France" /><figcaption>Your AI writes while.yaml, while builds and serves the app over HTTPS, and the previous version stays ready.</figcaption></figure>

## Set up Rails behind PgBouncer

> You, to your AI: Check that the migrations work behind PgBouncer.

`DATABASE_URL` goes through PgBouncer in transaction mode. Your AI turns off the migrations' advisory locks, which PgBouncer doesn't keep from one transaction to the next:

```yaml titre="config/database.yml"
production:
  primary:
    url: <%= ENV["DATABASE_URL"] %>
    advisory_locks: false
```

## Add a Sidekiq worker

> You, to your AI: Add a Sidekiq worker to send the emails.

Your AI declares a worker, with the same image and the `bundle exec sidekiq` command, and a Redis-compatible cache for its queue, connected with its password. It declares the cache with `durable: true`: pending jobs survive a restart, and none is evicted when memory is full.

## Query your database from your AI

> You, to your AI: How many orders did we get yesterday?

Your AI reads your database in SQL through while's MCP server, with your permissions on the data, and it can't write to it.

## Back up before a migration

> You, to your AI: Take a backup before the migration.

Your AI starts a backup, followed right away by a test: a throwaway database is created from it, and its tables are read back. Each database is also backed up every day.

## Restrict your app to your colleagues

> You, to your AI: Restrict the app to people in the company.

Your AI makes the service internal:

```yaml titre="while.yaml"
    access: internal
```

Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.

Once your Google Workspace or Microsoft 365 is linked to while, on the Pro plan, your colleagues sign in with their usual account, and your code receives their name and email address, with no sign-in page to write.

## Move to your own domain

> You, to your AI: Put the app on app.acme.com.

Your AI declares the domain, you add the DNS records it gives you, and the HTTPS certificate follows.

## Fix a vulnerability in your dependencies

> You, to your AI: Fix the vulnerabilities in our dependencies.

Your app's dependencies are checked against known vulnerabilities at every deployment, then every day. Your AI is warned about a serious vulnerability, and updates the package involved.

## Go back to the previous version

> You, to your AI: Go back to the previous version.

In the 30 minutes after a production release, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your AI reads what broke in while's logs, fixes it and deploys again.

## Next steps

- [Leave Heroku for while](/en/guides/migrate-from-heroku/)
- [Compare the Heroku alternatives](/en/comparisons/heroku-alternatives/)
- [Deploy a Docker container](/en/guides/deploy-docker-container/)

## Sources

1. [Ruby on Rails, the /up route (Rails::HealthController)](https://api.rubyonrails.org/classes/Rails/HealthController.html), 2026-11-02
2. [Ruby on Rails, preparing the database with bin/rails db:prepare](https://guides.rubyonrails.org/active_record_migrations.html#preparing-the-database), 2026-11-02

## Questions

### Do I need to write a Dockerfile?

No. Rails is detected, and your AI receives a Dockerfile ready to build. If your app already has the Rails one, your AI adapts it: the port, and the Solid Cache and Solid Queue databases.

### Are my migrations applied?

Yes, at every startup, by bin/rails db:prepare, which also creates the database the first time.

### I'm on Heroku: how do I move over?

Your AI takes over the code, copies the database from a Heroku export (pg_dump) restored by a job, and carries over your environment variables.

### What about Sidekiq?

Your AI adds a worker, with the same image, and a durable Redis-compatible cache for its queue: its jobs survive a restart.

### Where is my app hosted?

In France, by Nextmap, a French company.
