Open-Source CMS · hunvreus

pagescms

Pages CMS is an open-source, GitHub-integrated content management system designed for static site generators and JAMstack applications. It allows non-technical users to manage content and media directly within a GitHub repository without leaving a web interface, supporting tools like Next.js, Astro, Hugo, and Jekyll.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/hunvreus/pagescms

3.8k

GitHub stars

496

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	hunvreus/pagescms
Owner	hunvreus
Primary language	TypeScript
License	MIT — OSI-approved
Stars	3.8k
Forks	496
Open issues	55
Latest release	2.1.8 (2026-06-08)
Last updated	2026-06-23
Source	https://github.com/hunvreus/pagescms

What pagescms is

Built in TypeScript, Pages CMS provides a web-based editor backed by PostgreSQL and GitHub OAuth authentication through a custom GitHub App. It operates as a Git-native CMS layer, committing changes directly to repositories while supporting multiple static site generators and frameworks.

Quickstart

Get the pagescms source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/hunvreus/pagescms.git2cd pagescms3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Static Site Content Management

Ideal for documentation sites, blogs, and marketing websites built with Jekyll, Hugo, VuePress, or 11ty where content authors need a GUI but projects remain version-controlled in Git.

Multi-Author Markdown-Driven Projects

Suits teams requiring collaborative content editing with Git history tracking, enabling non-developers to contribute without direct repository access or command-line tools.

JAMstack Applications with Content-Heavy Workflows

Works well for Next.js, Astro, or Gatsby projects where content lives in the repository (JSON, Markdown, YAML) and requires a polished editorial interface without a backend CMS.

Implementation considerations

Requires PostgreSQL instance (local dev: Docker; production: managed RDS or equivalent) plus GitHub App registration and OAuth credential management.
Content structure must align with supported static generators; migration from legacy CMS or manual Git workflows may require content reformatting.
Authentication is GitHub-only; no support for other identity providers (SAML, LDAP). Admin access controlled via email allowlist in environment variables.
Hosting setup requires managed database, secure secret rotation (BETTER_AUTH_SECRET, CRYPTO_KEY), and canonical BASE_URL configuration for production deployments.
Local development demands Node.js, npm, Docker, and PostgreSQL CLI familiarity; team onboarding should include GitHub App setup documentation.

When to avoid it — and what to weigh

Real-Time Collaborative Editing Required — Pages CMS commits to Git on each save; simultaneous multi-user editing may cause merge conflicts. Not designed for real-time co-authoring like Google Docs or Notion.
Complex Workflow Approvals and Role-Based Permissions — Limited to admin email allowlist. No built-in draft/publish workflows, editorial calendars, or granular permission models beyond basic admin/user separation.
Existing Non-Git-Based Content Workflows — Requires GitHub integration and assumes repository-first workflow. Not suitable for teams using traditional CMS backends (WordPress, Contentful) without redesigning content architecture.
Self-Hosted Environments Without DevOps Support — Local setup demands PostgreSQL, GitHub App creation, environment variable management, and database migrations. Hosting requires familiarity with Docker, environment configuration, and deployment infrastructure.

License & commercial use

MIT License. Permissive OSI-approved license allowing commercial use, modification, distribution, and private use with only attribution required.

MIT License permits commercial use. No restrictions on building commercial sites or applications with Pages CMS. No commercial support, SLA, or warranty stated in publicly available data; reliance on community support via Discord, GitHub issues, or sponsor contributions.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	High
DEV.co fit	Good
Assessment confidence	High

Security considerations

GitHub OAuth used for authentication; users must trust GitHub's OAuth security. No independent security audit data provided. Secrets (BETTER_AUTH_SECRET, CRYPTO_KEY) must be securely generated and rotated. PostgreSQL credentials must be protected. No information on input sanitization, SQL injection prevention, or XSS mitigations. Admin access controlled by email allowlist (basic but not role-based). Webhook URLs must be validated to prevent replay attacks. Self-hosted instances require HTTPS and secure secret management practices.

Alternatives to consider

Contentful

Headless CMS with API-first design, real-time collaboration, and enterprise workflow support. Differs from Pages CMS by decoupling content from Git and offering managed infrastructure, but adds cost and vendor lock-in.

Sanity.io

Headless CMS with structured content, portable JSON APIs, and flexible hosting. Similar API-driven approach but richer permission models and real-time editing; not Git-native.

Forestry.io / TinaCMS

Git-backed CMS with visual editing. Direct competitors targeting static sites; Forestry acquired by Tina Labs. Offer similar workflows but with additional commercial support and managed hosting.

Software development agency

Build on pagescms with DEV.co software developers

Try the hosted version at app.pagescms.org to assess fit, or contact our team to discuss self-hosting requirements, integration with your static site stack, and customization needs.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

cms tinacms ujcms

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CMS Web App Development Custom Software Development Talk to DEV.co

pagescms FAQ

Can I use Pages CMS with a site already in production?

Yes. Pages CMS integrates with existing repositories. Create a GitHub App, connect your repo, and start editing content. No site rebuild needed unless you want to adopt Pages CMS's data structures. Existing Markdown/JSON is compatible if structured appropriately.

What happens if multiple users edit the same content simultaneously?

Pages CMS commits each edit to Git sequentially. Simultaneous edits by different users may cause Git merge conflicts. Not designed for real-time concurrent editing; best for serial editorial workflows.

Do I need to host Pages CMS myself, or is there a managed option?

Hosted version free at app.pagescms.org for immediate use. Self-hosting requires PostgreSQL, Node.js, Docker, and DevOps setup. No SaaS subscription tier mentioned; hosted version may have usage limits or future monetization.

Does Pages CMS support scheduling content or draft workflows?

Not mentioned in available documentation. Pages CMS appears to commit content immediately upon save. Draft/publish workflows, scheduling, and editorial calendars are not clearly described; requires review of advanced docs or GitHub issues.

Software developers & web developers for hire

Need help beyond evaluating pagescms? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source cms integrations — and maintain them long-term.

Ready to evaluate Pages CMS for your team?

Try the hosted version at app.pagescms.org to assess fit, or contact our team to discuss self-hosting requirements, integration with your static site stack, and customization needs.

Talk to DEV.co Schedule a Consultation