Pengin-Pi-3 Alpha

Pengin-Pi-3 Alpha is close to release. It is a self-hosted CMS and ERP development kit: the starting point we reach for when a project needs to become a real website instead of a brochure, with users, roles, content, and internal tooling all handled from day one.

Most starter kits give you a login form and leave the rest to you. Pengin-Pi-3 ships the parts that usually take a quarter to build.

What you get

• RBAC core infrastructure. Roles and permissions are part of the foundation, not a package bolted on later. Every surface in the platform respects them.
• Page and slug editor. Every slug-addressable page in the site is editable in place, by the people who own the content.
• Built-in wiki editor. Create a wiki, or a single page, whenever you need one.
• CMS media handling. Upload files, video, images, and documents, and publish articles or share material with your user base without touching the filesystem.
• Ticket system. Intake, assignment, and tracking, wired to the same user and role model as everything else.
• Events and calendar. Scheduling that lives alongside your content rather than in a separate tool.
• Security and analytics tooling. Strong defaults on the security side, with analytics available out of the box instead of pasted in from a third party.

New pages without migrations or a restart

The piece we are proudest of: creating a wiki or a page does not require a server reboot or a migration run.

Content structures are stored through a FerretDB document-store implementation, so new page types and new content shapes are defined at runtime. An editor adds a page, and the page exists. No schema change, no deploy window, no coordinating with whoever holds the database credentials.

For anyone who has waited on a migration to add one field to one model, this is the difference between a platform your client can actually use and one they file tickets against.

Why we built it this way

The design came out of real migration work. Several clients came to us with mundane, dated sites. With their permission, we crawled their existing files and rebuilt a modernized clone on top of this stack: the same content, now behind a proper login, user, and role system, with events and a calendar, a ticket queue, a wiki, editable slug pages, and CMS tools that make publishing an article or distributing a document routine.

The result was not a redesign. It was the same organization with software that could keep up with it.

Built to work with LLMs

Pengin-Pi-3 is written to be read. The codebase is consistent, the abstractions are explicit, and the SDK exposes management tooling rather than hiding it behind conventions you have to reverse-engineer.

That matters more now than it did two years ago. A clean, well-structured codebase is what lets an LLM scaffold a new feature correctly on the first pass instead of producing something that compiles and quietly breaks your permission model. Pengin-Pi-3 is meant to be extended quickly, by humans and by the tools they work with.

What "Alpha" means here

Alpha means the core is running and the edges are still moving. Expect the following:

• APIs may change between alpha builds.
• Documentation is being written alongside the code.
• We want bug reports, and we want them early.

If you are evaluating Pengin-Pi-3 for production, talk to us first so we can tell you honestly where the sharp corners are.

Getting it

Pengin-Pi-3 Alpha ships September 21st, 2026. Access details, install requirements, and the SDK reference will be posted here at launch.

If you are interested in a professionally hosted and supported setup, please contact sales.