Arch Framework

Most projects spend their first week wiring the same plumbing — sessions, sockets, data fetching, a build that doesn't fight you. Arch Framework was the attempt to make that week disappear: a robust full-stack foundation that folded modern best practices into the framework itself, so the boring-but-critical layers were already solid the moment you cloned it.

The idea was to hand you a strong starting line, not a blank file — and let you spend your attention on the part that's actually yours.

Four things came standard. Authentication — sessions, providers and protected routes ready out of the box rather than bolted on later. Real-time — a first-class live layer, so presence, updates and streams weren't an afterthought. API state management — an opinionated, optimized approach to fetching, caching and synchronising server state on the client. And an optimized build pipeline — tuned defaults for fast, lean production output.

The bet underneath all of it: a small set of strong, well-integrated conventions beats a large pile of loosely-coupled choices.

Arch was discontinued in December 2025. The full-stack-framework space moved fast, the meta-frameworks it sat alongside absorbed much of the same ground, and keeping an opinionated foundation current is its own full-time project.

It's kept here as an open, honest artifact — a record of a design stance about what a framework should hand you on day one, left public for anyone who'd rather read the source than the pitch.