Framework
apostrophecms/apostrophe avatar
apostrophecms/apostrophe

ApostropheCMS: in-context editing on Node.js and MongoDB

A full-featured, open-source content management framework built with Node.js that empowers organizations by combining in-context editing and headless architecture in a full-stack JS environment.

4,667 stars654 forksJavaScriptLicense varies

At a glance

What is it?
ApostropheCMS is a full-stack content management framework for Node.js teams that want editors working on the live page. It is a real CMS with a real database requirement, not a drop-in widget.
Who is it for?
Adopt ApostropheCMS if your team writes JavaScript, can run MongoDB 6.0 or newer, and wants editors working on the rendered page rather than in a separate admin. Do not adopt it if you need a static build with no server, or if nobody on the team wants to own a Node process and a database.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • apostrophecms/apostrophe4,667 ★ · +41
Star history
Repository2026-09-232026-11-15
apostrophecms/apostrophe4.6k4.7k

41 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The problem ApostropheCMS solves for Node.js teams

Most CMS choices force a split. A traditional CMS gives editors a familiar admin screen but hands developers a theme layer they fight with. A headless CMS gives developers a clean API but pushes editors into a separate form-based interface where they cannot see the page they are editing.

ApostropheCMS is aimed at the second half of that problem. The README describes in-context editing as editing directly on live pages without switching between admin interfaces. The audience is a team that already writes JavaScript on the server, is comfortable with MongoDB, and has content people who will complain loudly if the editing experience is a grid of text fields.

It is not a page builder for non-technical owners. The templates are written by developers. Editors fill them in. That division is the whole design, and it is why the framework expects a Node process rather than a static export.

How the Node and MongoDB architecture actually fits together

ApostropheCMS runs as a Node.js server and stores content in MongoDB. The README lists both as system requirements, with Node.js 20.x or newer and MongoDB 6.0 or newer, either a local install or MongoDB Atlas. There is no file-based content store and no SQLite fallback documented for users.

The repository is a monorepo. The top level holds packages/, pnpm-workspace.yaml, a private root package.json named @apostrophecms, and a test/ directory. The root test script runs the suite four times, once per value of APOS_TEST_DB_PROTOCOL: postgres, mongodb, sqlite, and multipostgres. That is worth reading carefully. The maintainers test against multiple database backends in their own CI, but the README's system requirements still name MongoDB only. If you are hoping to run this on Postgres in production, the repository shows the test harness exists and the user-facing documentation does not promise it.

The root package.json requires Node >=18 for the monorepo itself, while the README tells users to install Node 20.x or newer. The two numbers disagree, and the README is the one written for people installing the CMS rather than building it.

On the frontend, the README names ESM modules and Vite as the build tool and development server. The headless path is a REST API, and there is an Astro integration that the README says handles content fetching automatically so you do not write REST calls yourself. React, Vue, Svelte and anything else go through the REST API directly.

Installing ApostropheCMS and creating a first project

The README gives two ways to scaffold a project. The first installs the CLI globally, which it recommends if you keep more than one Apostrophe project on the machine. The second uses npx for a one-off.

bash
npm install -g @apostrophecms/cli
apos create my-website
cd my-website
npm run dev

After npm run dev, the README states the site is served at http://localhost:3000 and the admin interface is reached at /login. If the port is already in use, the README does not document an override; you would be looking at the generated project's own configuration rather than the install guide.

For a single project without a global install:

bash
npx @apostrophecms/cli create my-website
cd my-website
npm run dev

Either way, MongoDB has to be reachable before the server will start, because content lives in the database rather than in files. The README points at MongoDB Atlas for a cloud instance or a local install, and links its own setup guides for the details. The demo at demo.apostrophecms.com is the fastest way to see the editing experience before you commit to the install.

Where ApostropheCMS is the wrong tool

The database requirement is the first hard boundary. If your deployment target cannot reach a MongoDB 6.0 or newer instance, this is not your CMS. That rules out purely static hosting, and it rules out teams who have standardised on Postgres or MySQL for operational reasons. The repository's test matrix suggests other backends are exercised internally, but the README does not offer them to users, and adopting an undocumented path is a decision you make alone.

The second boundary is operational. You are running a Node server and a database. Someone has to patch Node, watch the database, and handle the fact that the editing interface is the same process serving the public site. A team that wanted a static site generator with a Git-based content workflow is not the audience here, and no amount of configuration will make ApostropheCMS behave like one.

The third is the split between the MIT core and the pro extensions. The README's pro list includes advanced user management with granular permissions and user groups, automated translation through DeepL, Google Translate and Azure, analytics and SEO features, and multisite management from a single dashboard. Those are described as pro features with a separate licence and a sign-up path, not as part of the open source package. If your requirements include any of them, the open source licence is not the whole cost story.

ApostropheCMS against a plain headless CMS

The honest comparison is with a headless CMS that has no rendering layer at all, such as a content API plus a separately built frontend. The difference is where editing happens.

With a pure headless CMS, the editor works in the CMS's own admin application, fills in fields, saves, and then either previews or waits for a build. The frontend is entirely yours, and the CMS never sees the rendered page. That model is simpler to reason about: one API, one contract, and the frontend can be anything, including a static build with no server.

ApostropheCMS inverts that. The live page is the editing surface, which means the server that renders the page and the server that manages content are the same Node application. You get in-context editing and you give up the clean separation. The README does support the headless shape through its REST API and the Astro starter kits, so the two are not mutually exclusive, but the framework's centre of gravity is the coupled version.

If your frontend is a mobile app or a set of clients that will never render an Apostrophe page, the in-context editing advantage disappears and you are paying for a rendering layer you do not use.

Maintenance, upgrades and what the MIT licence does not cover

The repository's last push was on 2026-11-02 and it is not archived, so the project is being worked on. That is a statement about the repository's activity, not a promise about release cadence; the repository has no published releases, so there is no version history to reason about here.

The monorepo layout matters for upgrade cost. The root package.json pins [email protected] as the package manager and declares onlyBuiltDependencies for better-sqlite3, sharp, vue-demi, @parcel/watcher, esbuild and unrs-resolver. If you contribute to or build from the repository rather than consuming the published packages, your toolchain has to match that. The .changeset/ directory indicates changesets are used for versioning across the workspace packages, which is the mechanism by which a change in one package propagates to release notes for the others.

On licensing, the README states the project is MIT and links the LICENSE.md file. MIT permits use, modification and distribution. The pro extensions are a separate matter: the README describes them as requiring a Pro licence obtained through Apostrophe Workspaces or a sales conversation. MIT on the core does not grant you those extensions. This is a description of what the documentation says, not legal advice; if the distinction matters to your organisation, read LICENSE.md and the extension terms yourself.

Editorial conclusion

Adopt ApostropheCMS if your team writes JavaScript, can run MongoDB 6.0 or newer, and wants editors working on the rendered page rather than in a separate admin. Do not adopt it if you need a static build with no server, or if nobody on the team wants to own a Node process and a database. Before committing, verify that MongoDB is available at the version the README requires, that Node is 20.x or newer, and whether the pro extensions you need (automated translation, multisite, granular permissions) are covered by a paid licence rather than the MIT core.

Frequently asked questions

What are the system requirements for ApostropheCMS?

The README lists Node.js 20.x or newer, MongoDB 6.0 or newer (either a local install or MongoDB Atlas), and npm 10.x or newer, which ships with Node. The repository's root package.json separately declares Node >=18 for the monorepo itself.

How do I install ApostropheCMS and start a project?

Install the CLI globally with npm install -g @apostrophecms/cli, then run apos create my-website, cd into the folder and run npm run dev. The README says the site then serves at http://localhost:3000 with the admin at /login. The npx @apostrophecms/cli create my-website form does the same thing without a global install.

Can I use ApostropheCMS headlessly with a different frontend framework?

Yes. The README describes a REST API for React, Vue, Svelte or any other framework, and provides Astro starter kits where the integration handles content fetching so you do not write REST calls. The headless guide and the pieces API reference are linked from the README.

Is the whole of ApostropheCMS open source under MIT?

The core is MIT licensed according to the README and the linked LICENSE.md. The README separately lists pro extensions covering advanced user management, automated translation, analytics and SEO, and multisite management, which require a Pro licence rather than the MIT grant.

Official sources

  1. apostrophecms/apostrophe on GitHub
  2. Issues
  3. Project website
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/apostrophecms-apostrophe.svg)](https://hysenlabs.com/projects/apostrophecms-apostrophe)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/apostrophecms-apostrophe.svg)](https://hysenlabs.com/projects/apostrophecms-apostrophe)

Was this useful?