DEV Community: The One-Man Framework

Why Rails 8 is the Only Choice for the Modern Solopreneur

The One-Man Framework — Mon, 18 May 2026 22:06:26 +0000

In the world of startups, there is a dangerous myth. People think that to build a "real" application, you need a team of five: a frontend expert, a backend specialist, a database admin, a DevOps engineer, and a designer.

If you follow this path as a solo developer, you will fail. You will spend all your time trying to glue different technologies together instead of talking to customers.

In 2026, the goal isn't to write the "fastest" code in terms of CPU cycles. The goal is Developer Velocity. You need a framework that handles the boring stuff so you can focus on the features.

After trying everything from Next.js to Go, I am convinced that Ruby on Rails 8 is the best framework for a one-man team. Here is why.

1. The Death of the "Infrastructure Tax"

For years, even a simple Rails app needed a lot of "extra" stuff to run in production. You needed Redis for background jobs, Redis for caching, and usually a Node.js server to compile your JavaScript.

Rails 8 has completely removed this "tax." With the Solid Trilogy, your entire stack is now just your app and your database (Postgres or SQLite).

Solid Queue: Your background jobs live in your DB. No Redis needed.
Solid Cache: Your HTML caching lives in your DB. No Redis needed.
Solid Cable: Your WebSockets live in your DB. No Redis needed.

For a solo dev, this is huge. It means your production server is simpler, cheaper, and much easier to debug.

2. No-Build Frontend (The Hotwire Revolution)

I used to spend half my day fighting with npm, webpack, and node_modules. It was exhausting.

Rails 8 uses Importmaps and Hotwire by default.

No Build Step: You save a file, refresh the browser, and it’s there. You don't need a heavy compilation process.
Turbo 8 Morphing: You get the speed of a React Single Page App (SPA) but you write 100% Ruby code. The browser is now smart enough to update the page without a full reload.

You can build a fast, reactive dashboard in an afternoon that would take a React developer a week to wire up.

3. Deployment is Solved (Kamal 2)

Deployment used to be the scariest part for solo developers. You either paid $100/month for a "managed" service like Heroku, or you spent days configuration Nginx and SSL on a raw Linux box.

Kamal 2 changed everything. It allows you to deploy a Dockerized Rails app to a $5 Hetzner or DigitalOcean VPS with one command:

kamal deploy

It handles the SSL certificates, the zero-downtime switching, and the health checks. You get the power of a private cloud for the price of a sandwich.

4. The "Editor-in-Chief" Workflow (AI Readiness)

As I’ve written before, we are in the era of Vibe Coding.

Because Rails is built on Convention over Configuration, it is the perfect partner for AI tools like Cursor or ChatGPT. Because every Rails app follows the same folder structure, the AI rarely makes mistakes.

If you tell an AI: "Add a billing system with a 'Pro' and 'Basic' plan," the AI knows exactly where the models, controllers, and views go. In a "flexible" framework like Express or FastAPI, the AI often gets lost. In Rails, it is a superpower.

Summary: The Math for the Solo Dev

As a one-man team, you have 40 hours a week.

Framework A (JS/Microservices): 20 hours on plumbing, 10 hours on CSS, 10 hours on features.
Rails 8: 2 hours on plumbing, 8 hours on CSS, 30 hours on features.

The choice is obvious. Rails 8 is the only framework that truly respects your time. It is designed to let one person build an empire.

Goodbye Nginx and Redis: Building a Zero-Service Monolith in Rails 8

The One-Man Framework — Mon, 18 May 2026 16:08:35 +0000

The "Zero-Service" Monolith: How to run your entire app on a single server port

For years, I believed that a professional Rails app needed a small army of services to survive in production. You couldn't just run Rails. You needed Nginx to handle SSL and assets, Redis to handle background jobs and caching, and maybe a separate load balancer.

As a solo developer, managing all these pieces is exhausting. Every new service is another thing that can crash, another version to update, and another port to secure.

With Rails 8, we are entering the era of the "Zero-Service" Monolith. The goal is simple: your entire application should live inside a single Docker container and communicate with the world through one single port. No Redis, no Nginx, no headaches.

Here is how to collapse your stack into a single, powerful unit.

STEP 1: The "Solid" Trilogy (Deleting Redis)

In the past, Redis was mandatory for two things: background jobs (Sidekiq) and caching.

Rails 8 replaces Redis with the "Solid" gems. These tools use your existing database (Postgres, MySQL, or SQLite) to do the work that Redis used to do.

Solid Queue: Handles your background jobs.
Solid Cache: Handles your HTML fragment caching.
Solid Cable: Handles your real-time WebSockets.

By switching to these, you can literally uninstall Redis from your server. Your background jobs now have the same "ACID" guarantees as your data, and you have one less service to monitor.

STEP 2: Thruster (Deleting Nginx)

Puma (the Rails web server) is great at running Ruby, but it isn't great at serving images or handling SSL certificates. That is why we always put Nginx in front of it.

Rails 8 includes a new tool called Thruster. It is a tiny, incredibly fast proxy written in Go that wraps around your Rails app.

Thruster handles:

HTTP/2: Speeds up loading for your users.
SSL (HTTPS): It manages your Let's Encrypt certificates automatically.
Asset Compression: It Gzips your CSS and JS files so they download faster.

Because Thruster is bundled into the Rails Docker image, you don't need to install or configure Nginx on your server anymore. You just point your domain to the container, and Thruster handles the rest.

STEP 3: The Single-Port Configuration

When you use Kamal 2 to deploy your Rails 8 app, it packages everything into one container.

In your deploy.yml, you no longer have to define "Sidecars" for Nginx or link to a Redis container. You just define your web server.

# config/deploy.yml
service: my-app
image: yourname/my-app

servers:
  web:
    - 123.45.67.89

proxy:
  ssl: true
  host: myapp.com
  # Everything enters through port 80/443 and goes straight 
  # to Thruster inside the container.

When this container starts up, it boots Thruster, which boots Puma, which starts the background job workers. Every part of your app is now living in the same memory space, on the same timeline.

STEP 4: SQLite for the Win (Optional)

If you want to go for the "Ultimate Zero-Service" setup for a micro-SaaS or a side project, you can even skip the external Database server by using SQLite.

With the recent improvements in Rails 8, SQLite is production-ready for many use cases. If you use SQLite, your "database" is just a file inside your container. Combined with Litestream for backups, your entire "Cloud Empire" is now literally just one single Docker process running on a $5 VPS.

Why this is a game changer for you

Mental Bandwidth: You only have to think about one thing. Is the container running? If yes, the whole app is working.
Cheaper Hosting: You don't need a server with 16GB of RAM to run 5 different services. A small, cheap server is plenty.
Faster Onboarding: When you hire a freelancer or use an AI to help you, they don't have to spend two hours setting up a complex local environment. They just run the app.

Summary

The "Zero-Service" Monolith isn't about being lazy; it's about being efficient. As a solo developer, every minute you spend configuring a Redis config file is a minute you aren't building features for your customers.

Rails 8 and Kamal 2 have made it possible to own your infrastructure without being a DevOps expert. One container, one port, one successful business.