ToGO — a Go and React framework that ships as one binary
API-first full-stack framework: Go backend, React frontend, generators and a plugin microkernel, compiled into a single deployable artifact.
- Go
- React
- sqlc
- Atlas
- GraphQL
- OpenAPI
- MCP
The problem
A Go backend and a React frontend are normally two repositories, two deploy pipelines and two sets of conventions — and the glue between them is rewritten on every project. Go has the runtime for it but none of the developer experience a Laravel developer takes for granted: generators, an ORM, migrations, auth and queues that are already decided.
What I did
- Generate
- Model
- Migrate
- API + UI
- One binary
One repository and one command: a resource manifest generates the model, migrations, REST and GraphQL endpoints and the page that lists them, then the frontend is embedded and compiled into the same artifact. Everything above the kernel is a plugin, so features are added without forking the framework.
Technical detail
Generator-first
The resource manifest is the source of truth: it produces the model, sqlc queries, migrations, GraphQL and REST with OpenAPI, and the admin page. Registries are regenerated rather than hand-edited, so the code and the manifest cannot disagree.
Everything is a plugin
A microkernel with plugins for auth, realtime, queues, search, mail, AI and MCP. A plugin owns its own schema at runtime, which is how CaBrain ships as one rather than as a fork.
API-first, both protocols
Every resource is exposed over REST with OpenAPI and over GraphQL, generated from the same definition — so a mobile client, a web client and an agent read the same contract.
Where it stands
ToGO is MIT-licensed and runs this site and the studio's products. Its plugin marketplace lists 241 packages generated from the GitHub organisation, and the framework is MCP-ready so agents can call a togo application as tools.
All projects