skelpo

skelpo / cms

Public

A blazingly fast, opinionated, native TypeScript CMS. Designed for Perry AOT, runs on Node and Bun.

12
2
85% credibility
Found May 21, 2026 at 12 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
TypeScript
AI Summary

Skelpo CMS is a headless content management system designed for agencies and small businesses. It provides a backend admin panel where content editors can manage website content (pages, posts, forms, media, menus) while a separate customer-built frontend website fetches and displays that content. The system emphasizes speed, security, and simplicity - using a dependency-based cache that keeps sites fast, enforcing SEO and accessibility at publish time, and providing tools like webhooks so content changes propagate instantly to the public site. It's opinionated (MySQL only, no plugins, one rich text editor) to reduce choice paralysis and is designed to run efficiently on modern JavaScript runtimes.

How It Works

1
📋 Decide you need a website content system

You run a small business or agency and realize you need a way to let your team manage website content without touching code.

2
⚙️ Set up your content hub

You install Skelpo CMS on your server - it becomes the central place where all your website content lives and gets managed.

3
👥 Invite your team

You create user accounts for your content writers and editors, giving each person the right level of access to do their job.

4
Start creating content

Your team opens the admin panel and begins writing pages, blog posts, or documentation - filling in text, uploading images, and filling out SEO details.

5
Two paths for the public website
🔧
Build custom

Developer builds a unique website that connects to your content using the provided client library.

🚀
Use starter template

Developer sets up a pre-made starter site that automatically displays your content.

6
🌐 Visitors browse your live site

When someone visits your website, they see pages that were fetched from your CMS - fast, cached, and always up to date.

🎉 Content updates go live instantly

When your team publishes or edits content, your website visitors see the changes automatically through background sync - no code deployments needed.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 12 to 12 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is cms?

Skelpo CMS is a headless content management system built entirely in TypeScript, designed to serve agencies, small businesses, and marketing sites. It separates the backend (a single API-driven binary) from the public-facing frontend you build yourself, communicating via REST and webhooks. The admin interface is server-rendered with HTMX, so there is no SPA build step, and it ships with two client packages: a typed API client with automatic caching and ETag revalidation, plus a site-kit library for SEO helpers like sitemaps, OpenGraph tags, and JSON-LD structured data.

Why is it gaining traction?

The pitch is raw performance: under 50ms cold start, sub-2ms TTFB on cached responses, and over 100,000 requests per second on commodity hardware when compiled to native with Perry. This is not theoretical; the README shows an honest benchmark table against WordPress, Strapi, Directus, and Payload. The other hook is zero native dependencies in the core stack. Image processing uses an imgproxy sidecar rather than Sharp, and password hashing uses bcryptjs rather than native bindings, meaning the same codebase compiles cleanly to Perry, Node, or Bun with no `node-gyp` surprises in CI.

Who should use this?

Agencies building multiple client sites benefit most: the CMS binary upgrades independently from each customer's frontend, no file migrations, no theme merging. Frontend developers who want full HTML and CSS control without fighting a CMS template system will appreciate the clean separation. Teams already sold on MySQL and wary of the operational overhead of Redis will like the in-process cache with dependency-based invalidation. If you need e-commerce, membership features, or multi-tenant SaaS, look elsewhere -- the README explicitly calls these out of scope.

Verdict

The architecture is well-reasoned and the performance numbers are compelling, but at 12 stars with a 0.85% credibility score, this is very early. The v0.1 label and May 2026 date suggest it is not yet battle-tested in diverse production environments. Worth watching and piloting on a low-stakes project, but do not bet a client deployment on it until the v1 release and a larger community.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.