All postsOur company runs several brands. Each brand has a website, articles, pages, and a team that fills them in. Managing all of that one by one slowly became a job of its own, and not the job that makes our brands better. That is where AtlasCMS came from.
The problem we had
One small change, such as fixing a sentence on a page or publishing a new article, meant opening one workspace, signing in, finding the right screen, and then repeating the same steps for the next brand. The more brands we had, the more places we had to remember, maintain, and secure.
We were not looking for the system with the longest feature list. We were looking for one workspace the team could use for every brand without mixing them up.
One place, many brands
In AtlasCMS, moving from one brand to another takes a dropdown. Pick a brand and you see that brand only: its articles, pages, media, settings, and team members. One brand's content never shows up in another, because every record belongs to its brand and the system refuses to read anything without a brand context.
Roles follow the brand too. An editor can write drafts for one brand without having access to another, while publishers and admins hold different powers over anything that touches the live site.
What you can do today
- Articles and pages managed in one place, with revisions, scheduled publishing, and a preview before anything goes live.
- A visual builder to put pages together from blocks, without touching code.
- Two languages side by side, Indonesian and English, for every article and page.
- SEO and media in the same flow: titles, descriptions, cover images, and alt text per language.
- AI help for drafting. The result always lands as a draft and never publishes itself, unless you turn on automatic publishing for a specific brand yourself.
Built for ourselves first
AtlasCMS is not a product we imagined and then went looking for users. We built it because we needed it. The Life Future website and the site you are reading now both run on it, and every change here comes out of our own team's real work.
Open for anyone with the same problem
If you manage several brands, clients, or sites and the story above sounds familiar, you are welcome to try AtlasCMS at atlascms.id. We want to know whether this way of working fits your case too, and your feedback will make it better.
Thank you, Kenari
A big thank you to Kenari (@kenarihq). Their AI model service feels "unlimited", and it helped us a lot with testing, security hardening, and end-to-end tests for AtlasCMS. With that much room to work, we could try and check far more before anything reached a user.
Thanks for reading. If you try it, tell us what is missing.
