Glue is where projects die
The evening spent making an ORM, a queue, and a mail library agree is the evening the idea loses momentum.
Teams
The whole stack fits in one head.
Building alone means every integration is yours forever. A framework that ships the database layer, the queue, the mail, the admin, and the deploy removes the part of side-project work that is not the project, and keeps the surface small enough to hold in memory.
What this always turns out to involve.
The work that arrives whether you planned for it or not.
Context is expensive
Coming back after three weeks away should not mean relearning your own wiring.
Hosting costs attention
A stack that needs four managed services costs money and vigilance you do not have.
No one to review you
Types and tests are the code review a solo developer actually gets.
What is already in the box.
All of it in the same install, typed against the rest of your application.
One install
Auth, models, queue, mail, storage, search, dashboard, and deploys arrive together and are already wired.
SQLite that scales further than you think
A single file in development and, for many projects, in production too, with Postgres or MySQL a config change away.
Scaffolding
buddy make:* writes the file, the test, and the registration, so starting a feature is one command.
One process in development
buddy dev runs the site, the API, the docs, and the reverse proxy with SSL together.
Deploy without a platform team
buddy deploy handles the build, the infrastructure, DNS, and certificates.
Types as a safety net
The compiler catches what a second pair of eyes would have, which matters most when there is no second pair.
The layers it leans on.
Every one of these ships in the same install. Follow one to see what it covers.
From the command line.
Buddy scaffolds, runs, and ships this the same way it does the rest of the app.
buddy make:action CreateNote
buddy dev
buddy deploy
Next door to this.
Projects of this shape usually grow into one of these.