Every client site, one account.
Build each client’s site on the same platform, hand it over with roles that hold, and give each project a plan of its own.
- Roles set per project
- Keep the keys yourself
- A plan per client project
Louise Admin
Moteur
The content platform agencies build client sites on, and their clients like to edit.
Every save is a commit in Git. People and AI agents edit side by side, a person approves what goes live, and your site reads it through its own API. Bilingual from the first field.
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.
What happens when someone hits Save
No plugin, no sync job: three things, every time.
1. They edit in the Studio
Louise, on the client’s team, changes an article. She sees both languages and what still needs review.
git log
721f194 Update press-release/resultats-1977 Louise Gagnon 7238adb Update event/brunch-lecteurs Sophie Marchand c5f772f Create faq/vide Marguerite Fontainegit log
4947387Update article/issue-01-1 — Louise GagnonOct 25, 19:45115df6dUpdate article/issue-01-1 — Louise GagnonOct 25, 19:3193b6fc6Create article/issue-01-1 — Louise GagnonJun 10, 00:44
2. Moteur commits it
Every save is a commit in the project’s own Git repository: who, what, when, and a way back.
your frontend
const [article] = await moteur .channel('public') .entries.list('article'); article.data.title.en // "We Started in a Garage in Montreal"your frontend
const article = await moteur .channel('public') .entries.get('article', 'issue-01-1'); article.data.title.en // "We Started in a Garage in Montreal"3. Your site reads it
Once a person approves it, the published version is what your frontend gets through the project’s API.
Try it: this one runs in your browser. In Moteur, the answer changes once a reviewer approves the save.
Who it’s for
Built for everyone around a site
One API per site, from any stack.
Each site reads its own channel: the fields it needs, published content only, described by its own OpenAPI document.
- A read-only key per site
- Every change in Git
- A TypeScript client, or plain HTTP
Théo Builder
Both languages, side by side.
Write with your colleagues in the Studio: see who’s in which field, leave notes where they belong, and send your work for review.
- Nothing a machine wrote goes out unread
- Every version kept
Marguerite Writer
Your content, in a repository you can take anywhere.
An open-source engine, every save a Git commit, and a plan per project, from free.
- The engine is MIT
- Billing is a role of its own
- Plans from free
Agents that wait their turn.
Point Claude or any MCP client at a project. It drafts and translates. A person approves.
- OAuth, project by project
- Agents can never approve
Claude AI agent
With AI
Agents that wait their turn
Connect Claude through MCP and it can draft, translate and fix, with only the access you grant. Every edit says who asked for it and waits for a person, like anyone else’s.
- Its review reads “Louise Gagnon via Claude Code asks for a review”
- What it wrote stays marked “Written by Claude Code” until someone reads it
- An agent can never approve, so nothing it writes goes live on its own
- Access is granted through OAuth, project by project: read, content or developer
In a terminal, Claude Code updates an article’s excerpt through Moteur’s MCP server and asks for a review. Then Céleste opens the review: “Louise Gagnon via Claude Code asks for a review”, the new excerpt marked as written by Claude Code and not yet read. She reads it, and approves.
The groove
Four people, one history
Everyone works at once, each in their own lane: writing, translating, reviewing. Every save lands in the same history, and what goes live is what the reviewer approved.
- Marguerite Fontaine: Drafts the headline; Asks for review.
- Louise Gagnon: Fixes the French title; Adds the cover.
- Claude: Translates the excerpt; Marked: not yet read.
- Céleste Armand: Sees one word changed; Approves.
- Published
For agencies
Every client site, one account
Start each client project in minutes. Give their team a Studio they can’t break. Keep the keys yourself, and bill each project on its own plan.
- Switch between clients from the top bar
- Invite each client’s team with the roles their job needs
- Reviews before anything goes live
Start free, grow one project at a time
Every project has its own plan. Start on Free, and move a project up when its site needs room.
Free
$0 / month
To try Moteur, or for a small site. One per person.
- 1 person
- 1 project
- 10 AI credits a month
- 100 MB of files
- 2,000 API requests a month
- 1 GB of image traffic a month
- 1 API channel
- 1,000 entries
- 50 pages
- 100 form submissions a month
Personal
$9 / month$89 / year
For a personal site or a portfolio, with room to grow.
- Up to 2 people
- 1 project
- 500 AI credits a month
- 1 GB of files
- 10,000 API requests a month
- 10 GB of image traffic a month
- 2 API channels
- 10,000 entries
- 500 pages
- 1,000 form submissions a month
Most agencies pick this
Pro
$39 / month$389 / year
For a site with a small team behind it.
- Up to 5 people
- 1 project
- 5,000 AI credits a month
- 5 GB of files
- 100,000 API requests a month
- 100 GB of image traffic a month
- 5 API channels
- 200,000 entries
- 2,000 pages
- 10,000 form submissions a month
- Writing and translation help
Extra
$129 / month$1,289 / year
For a busy site and the team that runs it.
- Up to 20 people
- 1 project
- 25,000 AI credits a month
- 20 GB of files
- 200,000 API requests a month
- 250 GB of image traffic a month
- 10 API channels
- 2,000,000 entries
- 500,000 pages
- 20,000 form submissions a month
- Everything in Pro
Extras, on any paid plan
- More people1 person$8 a month
- More API requests50,000 API requests a month$10 a month
- More AI credits2,500 AI credits a month$10 a month
- More room for files10 GB of files$5 a month
- More image traffic50 GB of image traffic a month$5 a month
Built on open source
The Moteur engine is open source (MIT): read it, run it on your own server, extend it with plugins. Moteur Cloud adds the web Studio, live collaboration, AI help and the operations.
The open-source engineQuestions people ask first
A writer asksDo we need to know Git?
MoteurNo. People write and publish in the Studio. Every save becomes a commit on its own. Git is there when you want it: the history, a way back, and a copy you can push anywhere.
A developer asksWhich frameworks does it work with?
MoteurAnything that can make an HTTP request. Each site reads its channel through a plain REST API with its own OpenAPI document, and there’s a TypeScript client for JavaScript sites.
Everyone asksIs there a free plan?
MoteurYes. Free is one person and a small site. Move a project to Personal, Pro or Extra when it needs more people, requests or storage.
A leader asksIs our content locked in?
MoteurNo. Each project is a Git repository of plain JSON files. Push it to your own remote whenever you like, and the engine that reads it is open source.
A cautious editor asksCan AI agents publish on their own?
MoteurNo. Agents connected through MCP draft and translate. Their edits are marked and wait for a person to approve them.
Start your first project.
Free to start. Bring a site you’re building, or start from a blueprint and see where it goes.