Hello, Velocity
Why we built a batteries-included full-stack Go framework, and what to expect from this blog over the coming months.
Most Go web stacks ask you to assemble the framework yourself: a router here, an
ORM there, a queue library borrowed from someone's blog post, auth glued on by
hand. It works, but every project starts from zero and ends with a pkg/ folder
full of opinionated wiring no one else can read.
Velocity takes the opposite bet. One framework. One mental model. Thirty-plus services behind a unified API. Routing, ORM, auth, cache, queues, mail, storage, scheduling, WebSockets, Inertia — all first-class, all sharing the same conventions.
What this blog is for
Three things, in roughly this order:
- Tutorials. End-to-end walkthroughs — building an app, deploying it, adding features without ripping out scaffolding.
- Design rationale. Why a particular API looks the way it does, what we tried first, what failed. The stuff that's hard to extract from docs.
- Field reports. Real production stories from teams running Velocity at scale, including the sharp edges they hit and how we smoothed them.
What's next
Subscribe to the RSS feed or follow @velocitykode on X to catch new posts as they go up.
If there's a topic you want covered, open a discussion on GitHub. We read every one.