Jaeger engine v0.5.0
A CMS that gets out of the way.
Schema-driven, server-rendered, no database. Jaeger turns one PHP array into a clean admin and a site that loads instantly. We build every client site on it.
Define schema in code. The admin builds itself — labels, forms, validations, all of it. Edit, save, live. No build queue, no preview deploy, no rebuild after every comma.
See the admin build itself.
Pick a starter, click a field type to add it, or edit the PHP schema directly. The admin updates as you type.
This is the entire admin-building workflow. Edit a PHP array. Save. That's it.
Real admins, in production.
Three screenshots from production Jaeger admins we've shipped for clients. What the demo above shows is what these sites actually run on.
-
List Karriere Filterable index with search, sort, status pills. Built from the same schema as the edit form below. -
Edit Leistung Edit form for a content type. Title, icon slot, bullet tags, markdown body with live preview. Status and metadata sidebar on the right. -
Edit Projekt More involved content type — category select, tags, hero image with alt text, locked URL path. All driven by the schema.
Feedback on the page itself — not in an email thread.
How a review round works with us: before launch we share a staging link. The client clicks the real layout, leaves comments, approves pages or requests changes. We pull the points locally, implement them, and resolve each thread in place.
Click anywhere on the layout to leave a comment yourself.
What makes it different
Five things about how Jaeger works that matter in practice — and the reason every client site we ship runs on it.
-
No database
Content lives in flat JSON files, versioned with your code and shipped with git. Nothing to provision, nothing to back up.
-
No build step
Server-rendered HTML on every request. Plain markup over the wire — nothing to hydrate, nothing to bundle.
-
Schema-driven
One PHP array defines your content shape. The admin UI follows automatically — labels, forms, validations, all of it.
-
Vanilla PHP
Runs on any PHP 8.1+ shared host. The same hosting your client already pays for — nothing new to learn.
-
DSGVO-clean
Every dependency vendored, every request same-origin. No CDN calls, no third-party scripts, no consent banner needed.
Built for speed
Targets we hold ourselves to — until we publish measured numbers from a live deployment.
Benchmarks pending — measured numbers from a production Jaeger deployment, coming.
Questions
The things that come up in every first conversation. Kept short, no marketing fluff.
Is Jaeger open source?
Not yet. It's the engine we ship every client site on — stable, battle-tested across our project base. If there's enough interest in seeing the source, we may open it. Write to us.
Can I install Jaeger myself?
Technically yes — it's a Composer package. But Jaeger isn't a turnkey product right now. We use it to build sites for clients; we don't sell it as a standalone tool. If you'd like a site built on it, that's the conversation to have.
What about WordPress migrations?
Yes. We've moved a number of sites onto Jaeger. Content typically maps into structured JSON cleanly; URL structure is preserved via redirect maps.
What hosting does it need?
Any PHP 8.1+ shared host with a few hundred megabytes of disk. No database. No Node runtime. We've deployed on Hostinger, all-inkl, and bare VPSes.
How does the admin work for non-technical clients?
Forms. Just forms. Each content type — pages, blog posts, team members, whatever the site needs — gets a clean editing form generated from the schema. Save drafts, publish when ready, upload images. No code, no plugins.
How does sign-off before launch work?
The client gets a staging link, clicks elements and comments right on the page, approves pages or requests changes — no login, no tool to learn. We implement the points and resolve each thread in place. Review data stays on staging and is purged after sign-off.
DSGVO / GDPR?
Clean by default. No CDN calls, no Google Fonts, no analytics, no third-party scripts. Every dependency lives on your server. You can add analytics if you want — you just don't start with a consent banner.
What if Jaeger needs a feature you haven't built?
We extend it. Jaeger is our own engine. If a client needs a feature, we add it, and every site we ship gets it on the next update.
Pricing?
We don't price Jaeger; we price sites. Each project is scoped individually. Reach out for a quote.