About
It started with a few blocks.
In 2025, Moteur was a small tool for one job: content blocks that any framework could read, so a site’s words didn’t belong to the way it was built. The blocks needed models, the models needed a Studio, and the Studio needed a team around it. It grew into a whole content system, and the first decisions held.
How it grew
From blocks to a content system
Each step came from a client site that needed it.
Blocks any framework can read
Content as plain data, not tied to a theme or a framework. Your site, in Astro, Next.js or anything else, draws it.
Models, pages and media
Blocks became entries, pages and menus, with pictures cropped for every screen and every language side by side.
A Studio for the client’s team
A place where people who never open a terminal write, review and publish, with roles for each of them.
Agents, with a person deciding
Every command became a tool for agents through MCP. They can ask for a review, never approve.
Early decisions
What we chose first, and kept
Git
Git is the content
Every save is a commit, in files you can read. The history is the backup, and leaving takes nothing more than a clone.
- Every version kept
- Pushed to your client’s own repository
API
Everything through the API
The Studio, the command line, agents and your site all use the same API. Nothing the Studio does is out of your reach.
- One API for people and code
- Documented on every server
Frameworks
No framework of ours
Moteur serves content. Your site, in whatever you build with, decides how it looks.
- Astro, Next.js, or your own
- A client for TypeScript
Open source
An engine you can read
The engine, API, command line, MCP server and client are MIT-licensed. Moteur Cloud adds the Studio and the services around it.
- On GitHub and npm
- Run it on your own server