Ruby on Rails development

Ruby on Rails development by a team that runs Rails 8 in production

Rails is still one of the fastest ways for a small team to ship a complete product, and the latest Rails is better at it than ever. We build new Rails applications, upgrade old ones and move apps to Kamal and the Solid adapters. All three of our own products run on Rails 8 today.

  • Three Rails 8 apps of our own in production
  • Hotwire front ends, background jobs and caching without Redis
  • Automated tests and security scans in CI, deploys with Kamal

A modern Rails 8 stack

  1. Hotwire front end

    Server-rendered pages with Turbo and Stimulus, with live updates and no heavy JavaScript app.

    • Turbo
    • Stimulus
    • ViewComponent
  2. Rails 8 application

    Business logic, background jobs, caching and websockets in one codebase.

    • Solid Queue
    • Solid Cache
    • Solid Cable
  3. PostgreSQL

    Data, jobs, cache and websockets on PostgreSQL, with continuous backups to two storage providers.

  4. Kamal deploys

    Docker images built in GitHub Actions and rolled out with Kamal.

    • Kamal 2
    • Docker
    • GitHub Actions
The setup behind Postcrest, Twelve Lumens and Salestreak.
What we can build

Rails work we take on

From a fresh Rails 8 app to keeping a codebase that's been around for years healthy.

New Rails applications

SaaS products, platforms and internal tools on Rails 8, with accounts, billing, background jobs and tests from day one.

Rails and Ruby upgrades

Step-by-step upgrades across major versions, with the test suite and deprecation warnings guiding each step.

Moving to Kamal

Containerised deploys with Kamal on servers you control, with Thruster in front of Puma and rollouts without downtime.

Solid Queue, Cache and Cable

Background jobs, caching and websockets on your database instead of a separate Redis, with a dashboard for every job.

Performance and reliability

Slow pages, heavy queries and stuck jobs found and fixed, with error tracking so problems surface early.

Takeovers and maintenance

We take over existing Rails apps, start with a code review, then keep dependencies, security patches and the test suite in shape.

Proof, not promises

Three Rails 8 apps we build and run

Postcrest runs on Rails 8.0; Twelve Lumens and Salestreak run on Rails 8.1 with Ruby 4.0. All three use Hotwire for the front end, ViewComponent for shared UI and the Solid adapters for jobs, cache and websockets. Postcrest dropped Redis entirely when it moved to Kamal.

Each app ships through GitHub Actions to Kamal on European servers, with continuous pgBackRest backups of PostgreSQL to two storage providers. Twelve Lumens and Salestreak translate their URLs with route_translator, so every language has its own paths.

  • Between 1,400 and 1,900 automated tests per app, in Minitest and RSpec
  • RuboCop, Brakeman and bundler-audit in CI
  • A design-system test that fails when a view uses colours or UI patterns outside the system
  • Mission Control dashboards for every background job
  • Container deploys without downtime, with Thruster in front of Puma in our newest apps

How our Rails apps stay healthy

  1. Checks

    RuboCop, Brakeman, bundler-audit and the full test suite, run in CI.

    • RuboCop
    • Brakeman
    • bundler-audit
  2. Builds

    Docker images built in GitHub Actions and pushed to the GitHub container registry.

  3. Deploys

    Kamal swaps containers without downtime, on servers we control.

  4. Monitoring

    Sentry for errors, Mission Control for background jobs and PostHog for product analytics.

The same setup across all three products.
Rails 8 apps in production
3
automated tests per app
1,400+
Redis servers needed
0
languages with translated URLs
5
Who it's for

Who we work with

Startups choosing a stack

Rails lets a small team ship a complete product quickly. We help you start on a setup that still works at scale.

Companies with an ageing Rails app

An old Rails or Ruby version, slow tests or no tests at all. We upgrade step by step, without a risky rewrite.

Teams that want more control over hosting

Move from a platform-as-a-service to Kamal on servers you control, with backups and monitoring in place.

Teams that need extra Rails capacity

Senior Rails work alongside your own developers, from a single feature to a complete module.

How it works

How we work on Rails projects

Every engagement starts with understanding the codebase or the product, then moves in small, safe steps.

  1. 1

    Review

    For existing apps: code, tests, dependencies, hosting and data. For new apps: the product and its first version.

  2. 2

    Plan the steps

    A phased plan with the riskiest changes first and a way back for each one.

  3. 3

    Make it testable

    Tests around the parts we're about to change, so every step can be verified.

  4. 4

    Build or upgrade

    Features, upgrades or migrations in small pull requests, deployed often.

  5. 5

    Deploy safely

    Containers rolled out with Kamal, with health checks and a quick rollback if something looks wrong.

  6. 6

    Keep it healthy

    Dependency updates, security patches and performance checks, so the app never falls years behind again.

The Rails stack we use

Modern Rails with as few moving parts as possible: one codebase, one database and containers you can run anywhere.

  • Ruby 4
  • Rails 8
  • Hotwire
  • Turbo
  • Stimulus
  • ViewComponent
  • Tailwind CSS
  • PostgreSQL
  • Solid Queue
  • Solid Cache
  • Solid Cable
  • Kamal 2
  • Thruster
  • Minitest
  • RSpec
Cost & timeline

What does Ruby on Rails development cost?

It depends on whether you're starting fresh, upgrading or taking over. These factors move the estimate most:

New app or existing codebase
A new app is scoped by its features. An existing one is scoped by what the review finds.
Version gap
Upgrading one major Rails version is a different job from catching up on five.
Test coverage
Apps with few tests need a safety net before big changes. That adds work upfront and saves it later.
Hosting move
Moving to Kamal covers containers, servers, backups, monitoring and a plan for the cut-over.
Integrations and data
External APIs, background jobs and data migrations that have to keep running during the change.
FAQ

Questions about Ruby on Rails development

How much does Ruby on Rails development cost?

It depends on whether you need a new app, an upgrade or a takeover, and on the state of the existing code. After a free intro call you get a written scope and estimate, split into phases.

How long does a Rails upgrade take?

That depends on the version gap, the number of dependencies and the test coverage. We upgrade one step at a time, and the review at the start gives you a timeline per step.

Is Ruby on Rails still a good choice?

For most web products, yes. Rails 8 runs background jobs, caching and websockets on your own database and deploys simply with Kamal, so a small team can build and run a complete product. We run three on it ourselves.

Can you take over our existing Rails application?

Yes. We start with a review of the code, tests, dependencies and hosting, fix what's urgent first and then improve the rest step by step.

Can you move our Rails app to Kamal?

Yes. We containerise the app, set up servers, backups and monitoring, and plan the cut-over so users don't notice. All three of our own apps deploy with Kamal.

Do you need Redis for Rails background jobs?

Not anymore. Solid Queue, Solid Cache and Solid Cable run jobs, caching and websockets on your database. Postcrest dropped Redis when it moved to this setup.

Do you work alongside our own developers?

Yes. We can take on a module or an upgrade while your team keeps building, with code reviews and handover notes along the way.

Have a Rails app to build, upgrade or rescue?

Tell us where the app stands today and where it needs to go. You'll get an honest view on the work involved and the safest order to do it in.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to