What is next
Grit ships every merged change as a release, so the changelog says what happened and says it in a lot of detail. This says what has not happened yet, which is the other half of deciding whether to build on something.
Reviewed 2026-11-22. Every line links to its issue, which is where the real state is: this page is a statement of intent, and intent is the part that only a person can refresh. Nothing here is a date, because a one-maintainer project that promised dates would be lying on a schedule.
Next
6Started, or the next thing to start.
- Fail CI when the shared types drift from the Go models
The generator already proves generate and sync agree. This turns that into a gate a project can run on its own code.
#255
- Migration safety: a dry-run plan and a lock-aware advisor
grit migrate already refuses to roll back a baseline. Seeing what a migration will do before it does it is the missing half.
#58
- grit eject: remove a battery from a project cleanly
The inverse of the removal work already done for resources and plugins, which is where the mechanism comes from.
#249
- What you can delete from a new project, and a --lean preset
A full project is a lot of files. Saying which are safe to delete is cheap and is the most common question after the first scaffold.
#248
- A stable tag for teams that cannot take a release every day
Every merged change ships, which is right for the project and wrong for a team with a change-control process.
#245
- A monthly digest of the changelog
The changelog is thorough and nobody reads 754 entries. A monthly summary is generated from the same source.
#266
Later
29Agreed it should exist, not scheduled. Say so on the issue if you need one sooner: that is how several of these moved up.
- OpenTelemetry: traces, metrics and correlated logs
Pulse answers the same questions inside one app. OTel is what you need once the app is not the only thing in the request path.
#41
- A History tab on every admin record page
The audit log already records the changes. This is the screen that reads it per record.
#261
- Per-resource data retention
A deletion policy expressed on the resource, which is where the rest of the resource policy already lives.
#260
- Ranked full-text search, and hybrid keyword plus vector
Vector search ships today. Ranked text search and a hybrid of the two is a bigger piece of query work.
#251
- An :embed modifier that keeps a vector in step with a text field
Pairs with the search work above, and should land with it rather than before it.
#252
- Stripe: per-seat and usage-based billing for organizations
The Stripe plugin handles payments. Subscription billing against the multitenant organization model is its own design.
#250
- Mobile money: M-Pesa, MTN MoMo, Airtel Money
The payment rails most of this project’s own users actually need, and each one is a separate integration with a separate sandbox.
#253
- The rest of the MCP plugin: grit mcp sync, doctor checks, admin screens
The server, the connections and a generated tool set per resource shipped in v3.548.0. What is left is the resync command, the doctor checks for a tools file that has drifted from its model, and making a connection from the admin rather than over the API.
#224
- A typed TypeScript SDK generated from the OpenAPI spec
The monorepo already shares types. This is for the clients that are not in the monorepo.
#16
- A notifications module: in-app, email and push
The pieces exist separately. The module is the one place that decides which channel a given notification uses.
#17
- One-command deploy to Dokploy, Fly and Railway
grit deploy covers several targets already; the rest is one provider at a time, and each needs testing against a real account.
#59
- Kubernetes output: manifests or a Helm chart
Docker Compose and a VPS cover the projects Grit sees. This is for the ones that outgrow that.
#259
- Preview environments per branch
A GitHub Action over the deploy work above, so it follows it.
#254
- grit generate suite: a whole management system in one command
The largest single item on the list. The blueprints cover the same ground today, by hand.
#66
- A double-entry accounting plugin
Money is exact in Grit already, which is the hard part. A ledger on top of it is a real piece of work and a real domain.
#63
- A hardware plugin: thermal printers, cash drawers, scanners
The desktop app is where this belongs, and it needs the hardware in the room to test.
#64
- An MQTT plugin for IoT
Companion to the websockets plugin. Waiting for somebody with a real device fleet to want it.
#65
- A pluggable adapter library for Stripe, Twilio, Resend and S3
Each of those works today behind its own interface. One common shape across them is a refactor, not a feature.
#52
- grit describe: propose models and handlers from a sentence
The agent skills do this well already with a human in the loop, which is the part this would remove.
#53
- An AI reviewer that knows the framework conventions
grit doctor covers the mechanical half offline. The rest is judgement, and a reviewer that cries wolf gets switched off.
#54
- A component playground and a design-token surface
The admin components are copied into each project rather than imported, so a playground has to be generated too.
#60
- Try grit generate in a browser, with nothing installed
The generator is Go and compiles to WebAssembly, so this is possible. It is a day of work and a surface to maintain.
#256
- A server-rendered frontend option: templ and htmx
A fifth frontend is a lot of surface. Worth it only if enough people want a Go-only stack to justify testing it.
#258
- Laravel Cloud as a deploy target
Five of the ten pieces shipped. The start command is still not settable through their API, which blocks the rest.
#92
- A Built-with-Grit case study page
Needs real numbers from a real team. Inventing them is the one thing a page like that must not do.
#265
- A video walkthrough series
Scripts and chapters are written. The recording is the part nobody else can do.
#264
- Multitenant follow-ups found on a real project
A list of small corrections from somebody using invitations in anger, each one its own fix.
#199
- Ten proposals from a business suite built in ten days
A field report rather than a feature. Several of its proposals have already shipped under their own issues.
#179
- grit-plugins modules store user_id as uint, core uses a UUID
A tracking issue against the separate plugins repository, not against this one.
#244
Waiting on a decision
1Open because a decision is owed before any code is worth writing. The decision is named, so it can be argued with.
- Rate limits per permission tier, and for API keys
The design question is whether a tier is a property of the role, of the key, or of the route. A proposal is on the issue and the decision is open.
#47
Not planned
Decisions already made, with the reason, so you can disagree with the reason rather than guess at one. A request nobody has got to yet is in the list above, not here.
A second web framework, ORM or CSS library
Gin, GORM and Tailwind are the stack, and the value of a convention-led framework is that there is one answer. Supporting Echo as well as Gin would double the generator and halve the conventions.
A Pages Router option for the Next apps
App Router only. Every generated page, layout and server action assumes it, and the second shape would be the one nobody tests.
Radix as the primitive library
Where a new primitive genuinely needs behaviour rather than appearance, it uses Base UI, which is the successor the shadcn maintainers point at. Existing hand-written primitives stay: they work and they are tested, and rewriting them would trade known behaviour for unknown.
A component registry inside every scaffolded project
It was there and was removed in v3.31.78. Every project carried a UIComponent model, a registry handler, a 91-component seeder and a browser page, for a feature almost nobody used. Grit UI is a standalone library instead.
An access column on the routes screen
gin exposes a route’s last handler and nothing in front of it, so the middleware chain cannot be recovered at runtime. The static table in internal/access is how anything learns which routes are protected, and inventing the column from path shapes would be a guess presented as a fact.
Want one of these sooner
Say so on its issue, with what you are building and what the absence costs you. That is not a formality: several items moved up because one person explained the case, and three of the things on this month's changelog exist because somebody filed the issue rather than working around it.
