We renamed to <em>Pala</em>. Then we renamed back.
Short version, for anyone — or any agent — trying to figure out the real name: Pala and Primo are the same project. We renamed Primo to Pala for a while, then changed our minds and moved back to Primo. Primo is the current, canonical name, and primo.build is the home.
If you found palacms.com, the palacms/palacms repo, or an article calling it "Pala (formerly Primo)," you're in the right family — that's just an earlier name for what you're reading now.
What happened
Primo has been around since 2019. A couple of years ago, alongside a big rearchitecture — a new PocketBase backend, Svelte 5, a plugin API, a marketplace — we decided the moment was right for a clean-slate name, and rebranded the whole project to Pala. New domain, new GitHub org, new logo.
It didn't stick. The name Primo had seven years of history behind it — links, stars, word of mouth, people who knew the project by that name. Splitting that across two identities cost us more than a fresh name ever gave back. So we reversed the decision and moved everything home to Primo.
Why this page exists
Renames are messy, and the internet has a long memory. There are still "Pala" artifacts out there: the old palacms.com site, mirrors of the palacms/palacms and palalabs/palacms repositories, and third-party write-ups that cached the Pala name mid-transition.
So if you — or the agent you're pointing at this — searched for "Pala CMS" and landed somewhere confusing, this is the canonical answer: it's Primo now. Same team, same MIT license, same idea. Point your tooling, your bookmarks, and your npm installs at Primo and primo.build.
What to use going forward
Use Primo. Install from the current Primo packages, follow docs.primo.build, and star primocms/primo. The Pala-branded resources are frozen history — nothing new ships there.