Can non-technical teams make changes without a developer?

Yes. Editors create pages from approved sections, edit text and images, and publish on their own, within the permissions their role allows.

Where does our content live?

In a Firestore database in your own Google Cloud project. You control access, backups, and retention.

The software is free and open source. You pay for your own hosting and cloud usage, and for any AI or translation providers you choose to connect.

How hard is it to change the content structure later?

The structure is defined in code, so developers change it the same way they change the site, with code review and version history.

Root.js at a glance

Who it is for

Root.js is built for organizations whose website is a product: brand and marketing sites, product launches, localized campaigns, and content hubs that change every week and have many people involved.

Content and marketing teams get a friendly editor, previews, and scheduling, without waiting on a developer for every change.
Localization teams get one place to see what needs translating, with AI and vendor integrations.
Engineering teams keep the content model in code, reviewed and versioned like the rest of the site.
Leaders get governance: roles, approvals, publishing checks, and a full audit trail.

How content is organized

Content lives in collections, such as Pages, Recipes, or Products. Each collection has a clear structure that developers define for the site: a product page has a name, price, and photos; a landing page is built from a set of approved sections. Editors fill in the blanks and rearrange sections, so every page stays on brand and nothing breaks the layout.

Every doc shows at a glance whether it is a draft, published, or scheduled, and who changed it last. See Editing and live preview.

The Content page in the Root.js CMS, with the site’s collections on the left and the docs in the Pages collection listed with thumbnails, titles, publishing status, and who last edited them. — The Pages collection for a fictional garden store, with each page’s status and last editor.

From draft to live

Every change starts as a draft. Editors preview it on the real site, share a preview link, and publish when it is approved — right away, at a scheduled time, or together with other changes in a release. Automated checks can catch missing translations or other problems before anything goes live, and every version is kept so any mistake can be undone.

See Publishing, scheduling, and releases.

The publish dialog in the Root.js CMS, showing a scheduled publish time, an AI-written change summary, and passing publishing checks. — Scheduling a page to publish at launch time, with a change summary written by Root AI and automated checks.

AI, built in

Root AI is an assistant inside the CMS that understands your site’s content structure. It can answer questions about your content, draft copy, translate pages, write image descriptions, and prepare releases. Editors choose whether it can only read, must ask before changing anything, or may edit drafts on its own. It never publishes by itself. See Root AI.

Open source, and your data stays yours

Root.js, including the CMS, is open source under the MIT license, with no per-seat fees. Your content is stored in your organization’s own Google Cloud (Firebase) project, not in a vendor’s shared database, and people sign in with their Google accounts. You decide where the site is hosted and who has access.

For roles, approvals, and audit logs, see Roles, permissions, and governance.

Frequently asked questions

Can non-technical teams make changes without a developer?: Yes. Editors create pages from approved sections, edit text and images, and publish on their own, within the permissions their role allows.
Where does our content live?: In a Firestore database in your own Google Cloud project. You control access, backups, and retention.
What does it cost?: The software is free and open source. You pay for your own hosting and cloud usage, and for any AI or translation providers you choose to connect.
How hard is it to change the content structure later?: The structure is defined in code, so developers change it the same way they change the site, with code review and version history.

Next guideEditing and live preview