The one-person monolith
You want one codebase, one deploy and batteries included — models, admin, jobs and email built in — and you'd rather write product than wire services together.
1 makers' products and 14 open-source projects use at least half of these 7 tools.The picks
Built for one person shipping a whole product — the framework decides the boring parts, from jobs to email to caching.
Chosen for backend framework by 24 makers' products we track · the alternatives →One database behind the whole app; Rails' tooling for it is mature.
Chosen for database by 74 makers' products we track · the alternatives →One capable server for a flat price; the monolith and its database fit on it.
Chosen for hosting by 100 makers' products we track · the alternatives →A mature Ruby SDK, and community gems that wrap subscriptions and the customer portal.
Chosen for payments by 891 makers' products we track · the alternatives →Reliable delivery for the mailers the framework already gives you.
Chosen for transactional email by 615 makers' products we track · the alternatives →Errors with the request, user and release attached, from one gem.
Chosen for error monitoring by 162 makers' products we track · the alternatives →A convention-heavy framework is exactly where a coding agent is most reliable — it knows where everything goes.
Chosen for AI coding assistants by 738 makers' products we track · the alternatives →What this costs you
One server and one framework mean one way of doing things; fighting the conventions costs more than in a thin stack. Laravel fits the same shape if you prefer PHP; Django if the product leans on Python.
Who builds this way
Using at least half of these tools, each with a source: makers' products from their own words, customer stories, subprocessor lists or websites; open-source projects from their code.