For leaders
Your content, in files you can take with you.
Moteur keeps each project as plain files in a Git repository, the engine that reads them is open source, and each site has its own plan. Cost, risk and the way out, in plain words.
The Moteur Journal, on disk
moteur-journal/
├── models/ 11 models, 146 entries
│ └── article/
│ ├── model.json
│ └── entries/issue-03-1/entry.json
├── pages/ 17 pages
├── templates/ 5 templates
├── blocks/ 17 block types
├── forms/ 3 forms
├── navigations.json
├── assets.json the media library's record
└── project.json
$ git log --oneline | wc -l
1062The exit test
Try leaving
The question to ask any content platform before you sign. Pack up the demo journal, and see where each part goes.
In the Git repository
Plain JSON, and every change since the first. Moteur pushes it to a Git address you give it.
Downloaded separately
From the Studio, one form at a time.
Not with you yet
Kept by Moteur Cloud, outside the repository.
- 11 modelsWhat each kind of content holds
- 146 entriesOne JSON file each, every language in it
- 17 pagesWith their 5 templates and 17 block types
- Menus and formsHow they’re set up, not the letters
- The media library’s recordTitles, alt text and focal points for 88 files
- 1,062 commitsWho changed what, and when
- 28 form lettersAs CSV, form by form
- The 88 files themselvesPictures and documents live in storage, not in Git
- Notes, reviews and activityKept beside the repository, not in it
- People and their sign-insAccounts belong to Moteur Cloud
The counts are the demo project’s. The Git address is set in the Studio, which also says whether every save has reached it.
Before you sign
The questions you’d ask
Cost, risk and control, answered by what the product does today.
Cost
A plan per site
Each project has its own plan, from free, so each client’s site carries its own cost.
- Monthly or yearly, in US dollars
- Change plans or cancel any time
Lock-in
Open source underneath
The engine is MIT-licensed. Read it, run it, and keep it reading the same files.
- The Studio and AI come with Moteur Cloud
- No database to export from
Limits
No surprise deletions
Reach a limit and only adding more is refused. A downgrade keeps everything.
- The message says which limit
- Grace when a payment fails
Control
Who can do what
Eight roles per project. With reviews on, nothing goes live until someone has read it.
- Billing is a role of its own
- A content lead can always fix a typo
AI
AI that asks first
Helpers are off until an admin turns them on, and agents can write but never publish.
- Costs shown before asking
- Agents’ changes carry two names
Record
A name on every change
Every save is a commit with who made it, so the record is there when someone asks.
- Restore any version
- In plain Git
Questions leaders ask
A CEO asksWhat if Moteur shuts down?
MoteurYour content is plain JSON in a Git repository, and the engine that reads it is open source under the MIT license. Nothing is locked in a format only we can read.
A CTO asksCan we host it ourselves?
MoteurThe engine, yes: it’s open source. The Studio, AI help and live collaboration come with Moteur Cloud.
A finance lead asksHow do we pay?
MoteurBy card, per project, monthly or yearly. Plans change or cancel any time, and invoices are in the Studio.
A CEO asksWho on our side can see the bills?
MoteurWhoever has the Billing role. It’s separate from admin, so the person who pays doesn’t need to touch the content.
A CTO asksCan we move everything to another Moteur?
MoteurYes. An admin exports the project as one bundle: models, pages, entries, menus, redirects and files by their address. Imported into an empty project, on Moteur Cloud or on your own server, it makes the same site.
Start small. Leave easily.
A free project costs nothing, and its files are yours from the first save.