What we ship.
What you build.
Short, practical reads on building full-stack apps with Grit, a new one most mornings. Getting started, CRUD in one command, framework comparisons, and production tips.
Grit FrameworkWhat's new in Grit: October 2026
179 releases in one month, which is too many to read. Here are the ten that change something for a project you already have, what to run, and the six security fixes you should not skip.
Grit FrameworkYour App Breaks in a Lift: How Offline-First Sync Actually Works
Two devices, one row, no network, and both people pressed Save. Every offline app has to answer that, and the answers are mostly not about networking at all. Here is the whole engine Grit generates: the outbox that squashes, the keyset cursor that stops losing rows, the tombstone that makes deletes travel, and the conflict you must never resolve silently.

A benchmark on a shared CI runner measures your code and the machine it landed on, so the threshold ends up too loose to catch a tenfold regression. An allocation count does not move with the machine or the load. It does move with the Go release, which I found out the way everyone does.

The lost update is the most common data-integrity bug in CRUD apps, because the obvious handler has it and nobody is ever told it happened. A transaction will not help you: the race is between two humans and a stale form. The fix is one WHERE clause and an HTTP header from 1999.

You add a read replica, latency drops, and one bug appears that nobody can reproduce: right after someone posts, their own post is gone. The textbook fix puts a Redis round trip on every read to solve a one-second edge case. There is a smaller answer that costs nothing and cannot be stale.

Publish then commit, and you announce an order that does not exist. Commit then publish, and the order exists with nobody told. There is no correct order for those two lines, which is the whole reason the outbox pattern exists. Including the lease that stops two replicas delivering the same message twice.

One row per INSERT takes an afternoon. Loading them all into a slice first runs the process out of memory. The answer is a two-pool pipeline with a bounded channel between it, and here is the whole thing: 999,800 rows in 59 seconds on a laptop, with the heap flat at 10 MB the entire time.

I built a shop, wrote two slow endpoints on purpose, and then went looking for them the way you would in production. One was wasted CPU in a function nobody would suspect. The other ran 200 queries per request and did not register as slow anywhere. Then I put 20 virtual users on both and got a flame graph of exactly that window. Here is which screen found which, and the file and line number each one gave me.

Bulk create and bulk edit as a spreadsheet grid, counted cards and charts generated per resource, a bin you can get a deleted record back from, one Operations page instead of two, one account page out from behind the System Hub, a grouped sidebar, uploads that work without Docker, and new Pulse, Sentinel and GORM Studio. Every one of them shown on a contacts app you can generate yourself in four commands.
Grit FrameworkYour app is already at stage four: what a framework can and cannot do about scaling
I took a well-known scaling guide, ten stages from one server to sharding, and worked out which ones a Grit app is born past. Five, it turns out, and two of the remaining five were missing entirely. This is what I built, what I refused to build, and the one decision no framework will ever make for you.

One project that uses everything new in Grit this month: ten field types that check and clean their own values, a seeder that fills a table with a million rows and picks up where it stopped, a live 'who else has this contact open' banner, import and export, and lint that passes on day one. Every command was run on a real project while writing this, and every number is the one it printed.

A complete ecommerce build for someone who learned Grit last week: catalogue, product variants, cart, Stripe checkout, order tracking for customers, and an admin your operations team can actually run the business from. Every command is one you can paste, every snippet says which file it belongs in, and the parts Grit does not do for you are named rather than glossed over.

You bought a dashboard template and you want its pages in your admin, without giving up URL-synced sorting, paging, filters, selection, bulk actions, toasts and cache invalidation. Grit's customisation system in eight levels, from patching one cell to replacing the page. For each one: what you get by default, why you would want to change it, and exactly how, with every snippet labelled with the file it belongs in.

Two admin surfaces every Grit app already ships with, a GDPR export/erase toolkit backed by a tamper-evident deletion journal, and access reviews that snapshot every role assignment for recertification. What they do, and the question that actually matters: how do they get populated?

A hands-on build that uses every one of Grit's new pieces in context, a Cloudflare-style theme, belongs_to and line-item relations, dropdown and toggle fields that carry their own options, atomic invoice numbering, the column you forgot added in place, and a Print button that was already there. One resource at a time, one command each, with a link to the docs for every step.

A Grit plugin doesn't hide in node_modules, it generates real code into your repo: models, routes, pages, migrations. And because every install is recorded, it's the one thing most plugin systems can't do: cleanly uninstall. Here's the model, the first-party plugins, and how to write one.

Every new Grit app now comes with a real authorization model (roles, granular per-resource permissions, and a permission editor that works on web, mobile and desktop) plus scheduled database backups you can restore with one click. No wiring. It's just there when you run grit new.

One command scaffolds a Wails desktop app that works online AND offline. grit generate resource fans out to the desktop too now: full CRUD screens backed by a local SQLite mirror that syncs to your server when you're connected. We build a real Point of Sale: categories, products, stock, clients, suppliers, purchases, and a custom checkout screen that completes sales and decrements stock even with no internet.

Point grit generate resource at your Expo app and it scaffolds typed hooks, list + detail screens, and the plumbing for a real store. We wire a Category → Product shopping flow with similar products in one sitting.

In one sitting: scaffold a Category → Product store, handle image uploads, model a one-to-many relationship, and manage all of it from a generated admin panel.

I kept rebuilding the same backend on every project (auth, roles, audit trails, rate limiting, storage, OTP, email, cache, jobs) before ever touching the actual product. So I combined all of it into one thing, on Go.
Founder of Grit and author of The Daily Grit. A 5-minute morning read on building full-stack apps with Go + React.