Théo Nguyen · Builder
Théo says what an article holds
Its fields, its languages, and the blocks its body may use. The Studio’s form and the API’s checks follow from it.
- Forty kinds of field
- Kept in Git
The product
Everything an article needs, from the model to the site.
Moteur is where a client’s content is shaped, written in two languages, reviewed and kept, then served to the site your agency builds. Follow one article through it.
Louise fixes the accent in an English headline, “Montreal” to “Montréal”, and publishes. The History tab shows the save. Then a terminal: the project’s Git log has the commit, and the site’s script reads the new headline from the API.
Follow it
One article, from start to site
Pick a step to see who does it and what happens. Each one has a page of its own.
Sophie Marchand · Writer
Sophie gives it a home in the site
A listing page gives every article its own address, and the menu links to the page, so it follows.
- /journal/[slug]
- Live entries only
Marguerite Fontaine · Writer
Marguerite writes it
French and English side by side, notes on the field they’re about. Nothing changes until she saves.
- Both languages at once
- Every save kept
Sophie Marchand · Writer
Sophie marks the face in the cover
Every crop the site asks for keeps what she marked, with alt text in each language.
- Eight shapes
- Any width on request
Sophie Marchand · Writer
The English gets filled in
Machine translation fills the empty side, marked until a person reads it.
- Marked until read
- For a credit or two
Louise Gagnon · Admin
Louise is in the same article
Each sees who’s in which field. When two saves cross, everything that doesn’t clash merges.
- Down to the field
- Crossed saves sorted out
Claude · AI agent
Claude suggests a shorter excerpt
Through MCP, as Louise. What it writes is marked, carries both names, and waits for a person.
- Review-only
- Two names on every change
Céleste Armand · Reviewer
Céleste reads what changed
Word by word, next to the live version. She approves, and it goes live, or sends it back with a note.
- Nothing live unread
- Content leads can still fix a typo
Louise Gagnon · Admin
Every step is a commit
Who, what and when, in the project’s own Git repository. Any version can come back.
- Plain JSON files
- No lock-in
Théo Nguyen · Builder
The site reads it
Through its own channel, with a read-only key and its own OpenAPI. Publishing can tell the site to rebuild.
- Published content only
- Pictures at any size
Louise Gagnon · Admin
Readers write back
The contact form on the site lands in the Studio’s Inbox. Bots go to Spam.
- The team is told
- A thank-you in their language
The people are the demo journal’s team. The steps are what Moteur does today.
Around it
Everything else in Moteur
The parts that aren’t one step of an article, but that every client site leans on.
Roles
Roles that hold
Eight roles per project, so the client’s team writes and reviews, and can’t change what the site depends on.
- Writer, translator, reviewer, content lead
- Builder, admin, developer, billing
AI
Help, when asked
Writing and translation helpers, off until an admin turns them on, costs shown first.
- Suggestions, never saved alone
- Credits per plan
Agents
For AI agents
Every operation as a tool, for Claude or any MCP client, signed in as a person.
- 176 tools, or three
- Review-only by default
Plans
A plan per site
Each project carries its own plan, from free, with limits it can see.
- Nothing deleted at a limit
- Extras on paid plans
Open source
An open engine
The engine, API, CLI, MCP server and client are MIT-licensed. Moteur Cloud adds the Studio.
- Read the code behind the claims
- Run it yourself
Changes
What’s new
What changed in each release, in plain words, by who it matters to.
- Calendar versions
- From the engine’s own changelog
Take your own article through it.
Start a free project, write one article, and read it from the API.