NEXT-GENERATION CMS
LuperIQ CMS — Built in Rust, Powered by Event Sourcing
A content management system that doesn't compromise. LuperIQ CMS replaces MySQL, PostgreSQL, and the entire LAMP stack with a single 26 MB binary. No database server. No query optimizer. No ORM. Just an append-only, cryptographically signed event journal that makes your site fast, tamper-proof, and auditable by design.
Why a Rust CMS?
WordPress powers 40% of the web, and attackers know every vulnerability by heart. SQL injection, plugin conflicts, database corruption, slow page loads from uncached queries — these aren't edge cases, they're daily reality. LuperIQ CMS was built from scratch in Rust to eliminate these entire categories of problems.
Memory-safe by default. Rust's ownership model prevents buffer overflows, use-after-free, and data races at compile time. The classes of bugs that lead to remote code execution in PHP simply cannot exist here.
No SQL, no injection. LuperIQ ForgeJournal stores data as cryptographically signed events in an append-only binary file. There is no SQL parser. There is nothing to inject into. The attack surface that defines WordPress security advisories doesn't exist.
Single binary, zero dependencies. The entire CMS — 28 modules, GraphQL API, theme engine, AI integration, admin panel — compiles into one 26 MB executable. No PHP, no Apache, no MySQL, no Redis, no Docker. Copy the binary, run it, done.
What Makes LuperIQ ForgeJournal Different
Traditional databases overwrite data in place. When you update a page title, the old title is gone. LuperIQ ForgeJournal never overwrites anything. Every change is a new event appended to an immutable journal, signed with BLAKE3 checksums and chained through hash chain roots.
- Complete audit trail — Every edit, every login, every published page, every deleted draft. Who did what, when, from where. Not a plugin or add-on — it's how the database works.
- Cryptographic integrity — Three layers of tamper detection (BLAKE3 hash, keyed BLAKE3 MAC, hash chain). If a single byte changes in the journal file, the system detects it on the next read.
- Instant backups — Copy one file. That's your complete backup. Every page, every user, every order, every event that ever happened. Restore by copying it back.
- Zero-copy reads — Binary serialization with bincode, not JSON parsing. Event lookups take microseconds, not milliseconds.
Deep dive into LuperIQ ForgeJournal architecture →
28 Built-In Modules
No plugin marketplace. No compatibility matrix. No "works with version 5.2 but breaks on 5.3." Every module ships with the CMS, tested together, deployed together.
Content & SEO
Pages, blog posts, full revision history, SEO meta (title, description, focus keywords), sitemap generation, robots.txt, 301 redirect management, SEO scoring.
Theme Studio
Visual design system with 50+ content blocks, mega navigation builder, popup scheduling, responsive layouts, dark mode, CSS generation from design tokens. No CSS knowledge required.
AI Content Generation
Two-stage AI pipeline: local Qwen3-14B for fast bulk generation, cloud Claude for SEO refinement. One-click website generation from 6 industry blueprints. Credit-based transparent pricing.
Commerce & Billing
Product catalog, Stripe checkout integration, subscription management, invoicing with line items and tax, estimates, payment tracking. Full order lifecycle.
Booking & Operations
Online appointment scheduling, availability management, technician dispatch, GPS check-in, work logging, material tracking, customer self-service portal.
Communication
SMTP email delivery, contact forms, customer messaging threads, multi-channel notifications (email, SMS, push), newsletter management.
Not Just Service Businesses
The industry modules (pest control, HVAC, plumbing, electrical, landscaping, restaurant) prove the platform handles complex domain logic. But the core CMS — content management, themes, SEO, commerce, AI, and the GraphQL API — works for any website that needs to be fast, secure, and maintainable.
- Marketing sites — SEO-optimized pages, blog, contact forms, analytics
- E-commerce — Product catalog, Stripe checkout, order management
- SaaS platforms — Multi-tenant deployment, API-first architecture, subscription billing
- Service businesses — Booking, dispatch, invoicing, customer portal
- Content publishers — Blog, revision history, AI content pipeline, SEO scoring
- Internal tools — Admin dashboards, data management, audit trails
GraphQL API — 141 Resolvers
Every piece of data in the CMS is accessible through a typed GraphQL API. 40+ query resolvers, 100+ mutation resolvers. Content, taxonomies, menus, users, sessions, commerce, modules — all queryable, all type-safe, all documented in the schema.
Build headless sites, mobile apps, or integrate with external systems. The API isn't an afterthought — it's how the admin panel itself works.
Multi-Site Architecture
Each CMS instance runs independently — its own LuperIQ ForgeJournal, its own modules, its own domain. Deploy one site or a hundred. Each gets full isolation with zero shared state. No "noisy neighbor" problems, no cross-tenant data leaks, no shared database bottleneck.
Currently running three production instances from a single server: luperiq.com (central platform), a pest control demo, and an HVAC demo — each with distinct content, themes, and industry configurations.
Performance — Real Production Benchmarks
Measured on the production server (Intel Xeon, 128 GB RAM, NVMe SSD) using Apache Bench. No caching. No CDN. Every request reads live data from LuperIQ ForgeJournal.
| Operation | Response Time | Throughput |
|---|---|---|
| GraphQL API query | 1.7 ms | 568 req/sec |
| Static file serve | 2 ms | 514 req/sec |
| Full page render | 19–55 ms | 18–53 req/sec |
| WordPress (same server) | ~700 ms | ~1.4 req/sec |
The 1.7 ms GraphQL response is faster than WordPress even when WordPress serves static HTML from a full-page cache (2–5 ms). And LuperIQ is reading live data, not serving a pre-rendered file. See detailed benchmarks →