ponzu-cms/ponzu

Headless CMS with automatic JSON API. Featuring auto-HTTPS from Let's Encrypt, HTTP/2 Server Push, and flexible server framework written in Go.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 11th, 2026
Created on September 17th, 2016
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 384
Total Stargazers: 5,756 (+0)
Total Subscribers: 128 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Ponzu is a headless CMS that generates automatic JSON APIs with built-in HTTP/2 support and automatic TLS certificates from Let's Encrypt.

The tool addresses the need for rapid development of content management systems that serve JSON APIs to web and mobile applications. It combines CMS functionality with a high-concurrency HTTP server framework written in Go. Ponzu generates content editors and API endpoints from simple type definitions, eliminating boilerplate code. It handles TLS automatically, using self-signed certificates in development and Let's Encrypt certificates in production, with automatic renewal. The framework includes HTTP/2 Server Push capabilities and uses an embedded database for simple deployment as a single binary.

Ponzu suits developers building modern applications that need both content management and fast JSON API responses in high-concurrency environments. It targets projects where traditional WordPress-style systems feel too heavy but where rapid development speed matters. The tool is particularly useful for teams wanting to avoid the complexity of separate CMS and API infrastructure. The README positions it as an alternative to WordPress for CMS functionality and Rails for rapid development, but specifically optimized for JSON API delivery at scale.

The project is abandoned and no longer maintained. The README explicitly states this status and directs users toward alternative solutions for HTTP server needs.