The web changed.No CMS caught up.
Amanta is the human layer on open source. Your website is code you own. What your company knows lives in a brain you can host anywhere. Anyone on the team changes what the company says, and nothing stops working if Amanta goes away.
The whole thing, in one picture.
Four parts, in a row. The brain is what the company says about itself. The studio is where the team changes the site. The repository and the host are yours, and keep working if the first two are switched off.
Every CMS still assumes a developer builds the templates and an editor fills in the fields. That is a 2010 shape for a web where pages are written, drawn and shipped in one sitting.
Open source won.
The best web stack today is free, React-based and yours to keep. A CMS that rents that stack back to you, in its own schema, on its own servers, is the wrong layer to build a company's voice on.
Code is the format.
A page is a section of React with words in it. Kept as code, every developer, every tool and every model can read and change it. Kept in a vendor's content model, only the vendor can.
Knowledge is the asset.
What a company offers, who it talks to and how it sounds is the thing worth keeping. It belongs to you, in your database, in plain records, usable with any model or with none.
One brain. Any model. Your site, as code you keep.
The whole system is four parts, and you can stop at any of them. The brain alone is useful. The studio without a model is useful. The site without Amanta still works.
The brain
Everything public about the company, written once: what you offer, who you talk to, how you sound, the facts, the people, the brand. Nothing confidential. Plain records in Postgres.
Any model, or none
The brain is handed to whichever model you allow. Claude, GPT, Mistral, a model running on your own machines. Or to no model at all: the studio works by hand, with a library of your own sections.
The studio
A canvas where you click on the page and change it. A chat that writes and redraws when you let it. Every change is a version you can take back. Staging first, live when you say.
Your repository
Publishing writes a frozen build into a repository you own, on a host you choose. The published site calls nothing of ours. If Amanta disappears, the site does not.
The brain is the public mind of the company, written down once.
It is not a CMS database with pages in it. It is what you would tell a new colleague on their first week, kept as records a person can read and a model can use.
- Sovereign cloud4 capabilitiesUsed in 123 d
- AI platform3 capabilitiesUsed in 71 w
- Enterprise AI2 capabilitiesUsed in 32 w
- Regulated enterprisesCIO, head of security, architectUsed in 95 d
- Public sectorIT lead, procurementUsed in 42 w
- DevelopersPlatform engineerUsed in 51 w
- Enterprises, on the websiteCalm, exact, no superlativesUsed in 141 w
- Developers, on LinkedInShort, concrete, shows the commandUsed in 63 w
- RegionsStockholm, Paris, FrankfurtUsed in 8Changed
- Founded2022, in StockholmUsed in 34 w
What goes in
- What you offer, and the capabilities under each offer
- Who you talk to: audiences, the roles inside them, their situations
- How you sound, per audience and per channel
- Facts: figures, dates, names, with their source
- People, places, events, resources
- The brand: colours, type, imagery, the rules for using them
What never does
- Customer data
- Contracts, prices, pipeline
- Anything marked confidential, which no generator ever receives
Where it lives
A Postgres database. Ours, or one in your own cloud, or exported as plain files in your repository. Moving it is a dump and a restore. Every change is logged and can be reverted, one row at a time.
The studio is a canvas, not a form.
A CMS gives editors fields and developers templates. Amanta gives the whole team the page itself, with the brand kit keeping it straight.
The cloud for European companies whose data has to stay in Europe, from Paris and Frankfurt to Stockholm.
Compute, storage and AI models in three European regions, run by a European company.
Three ways to run on it.
Sovereign cloud
Compute and storage under European law, in the region you pick.
AI platform
Open models served from the same data centres as your data.
Enterprise AI
Assistants for your teams, on data that never leaves.
Chosen by teams in banking, health and the public sector
A library of your own sections
Your existing site, taken apart into sections you can reuse: a hero, a feature row, a team grid. New pages are made from them, so nothing drifts off brand.
Click on the page and change it
Text, images, order. The canvas is the live site. Nothing to learn beyond what a document editor already taught you.
Ask, when you want to
Point at a section and say what should change. One model call rewrites it, you see it at once, and you can take it back. Or make a whole page from a sentence and the brain.
Staging first, live when you say
Every change is a version. Your team sees staging; the public sees live only after someone presses Publish.
One brain, every surface.
The web comes first. The same records also write a LinkedIn post, a short film, an image brief or a mockup, and all of them say the same thing, because they were told the same thing.
- yourcompany.com
Regions: Stockholm, Paris, Frankfurt
Web page
- Your company2 h
Regions: Stockholm, Paris, Frankfurt
LinkedIn post
Regions: Stockholm, Paris, Frankfurt
Short film
Regions: Stockholm, Paris, Frankfurt
Image brief
Compared with a CMS.
A fair table. The open-source ones are good software; the question is which layer you want a company's voice to live in, and who holds it.
| Amanta | Payload | Sanity | Strapi | Webflow | |
|---|---|---|---|---|---|
| Made in, owned by | Stockholm. Wiking Media. | Michigan. Figma, San Francisco, since 2025. | Oslo roots. San Francisco. | Paris. | San Francisco. |
| Where your content lives | Your repository and your Postgres. | Your database. | Sanity's cloud. | Your database. | Webflow's cloud. |
| What a page is | A React section with words in it, in your repo. | Fields in a schema a developer wrote. | Fields in a schema a developer wrote. | Fields in a schema a developer wrote. | A design in Webflow's designer. |
| Who changes the site | Anyone on the team, on the page itself. | Developers shape, editors fill. | Developers shape, editors fill. | Developers shape, editors fill. | Designers. |
| If the vendor goes away | The site stays up. The brain exports. | The code stays. The admin needs their package. | The content lake is gone. | The code stays. | The site is gone. |
| AI | Optional. Any model, including yours. Or none. | Plugins. | Hosted assist. | Plugins. | Webflow's. |
| Runs entirely in your European cloud | Yes. | Yes, self-hosted. | No. | Yes, self-hosted. | No. |
Built in Stockholm, for companies with rules about where things run.
Sovereignty is not a tier on a pricing page. It is how the thing is shaped: open code at the bottom, your database in the middle, a studio that can sit anywhere on top.
The studio
Switched off
Your repository
Your host
Your visitors
Live
Studio off. Site live.
- Your cloud
- The studio is a Node application and a Postgres database. It runs on our servers in Stockholm, or in your account on any European cloud.
- Your models, or none
- Generation goes through one door. Behind it: the models you allow. A European provider, an open model on your own GPUs, or nothing at all.
- A site that calls nothing
- The published site is a frozen build with its fonts and images inside it. No Amanta, no Google, no US content network in the path to your visitors.
- Two parties in the delivery path
- You and us. Everything else is software you run.
Where it stands.
Amanta is made by Wiking Media in Stockholm. Its brain runs a client’s public knowledge in production today, and their site is being rebuilt on it. The studio is in development, and we are choosing the next company to build it with.
That means two honest things. The shape you read about here is real and running. The polish is not finished, and the next company gets a say in what it becomes.