Rift is the CMS for publishers that require precision
Built from fifteen years of enterprise content management experience to improve your publishing operations and policy heavy workflows.
Frictions that compound over time.
Migrations that take months
The typical CMS migration takes way too long: extracting content, rewriting links, rebuilding navigation, applying design patterns page by page. Rift automates the mechanical work so you focus on the decisions only a human can make.
Broken links and content spraul
Delete a page without knowing what links to it and you've created broken experiences that won't surface until a reader reports them. Rift maintains a live graph of every content relationship — updated on every save, enforced at every deletion.
Design systems aren't enforced
The Figma file says one thing. The CSS says another. The published site says a third. Rift manages your design system as versioned, publisher-enforced content — tokens, components, and linting in one place, with AI agents able to consume it directly.
“Rift doesn’t offer a page builder or a block library. It offers a precise content management framework for expert web developers who write their own AI assisted HTML.”
Built for precision work at scale.
Know what breaks before you touch anything
Every reference between content items — anchors, image embeds, CSS references, navigation links — tracked on every save. Archive-blocking when inbound links exist. Depth-3 impact analysis in real time. Deeper analysis as a background report.
Sitemap in. Structured content out.
Provide a sitemap.xml. Rift crawls the site, extracts body content, downloads and deduplicates assets, identifies design patterns, generates an initial design system, and rewrites internal links to CMS references. All migrated content lands in draft.
Your design system is a managed content item
Upload tokens, components, and compiled CSS as a versioned package. The publisher resolves {{ds:component/alert}} references at build time. Authors browse the component library from the editor. A linting report surfaces deviations.
Git-push with zero downtime
Staging is a branch. Production is a branch. Each publish is one atomic commit. The published site has no runtime dependency on the CMS. Content hash change detection means only changed items republish — never the full site unnecessarily.
Government-grade content lifecycle
Draft, staging, public, archived — with paired staging versions so public content stays live during edits. Full version history with diffs. Optimistic locking with conflict resolution. Comprehensive audit log. Single-tenant deployment for data sovereignty.
Your content, readable by humans and AI agents
Every publish also emits an Open Knowledge Format bundle to a separate GitHub repository. AI agents traverse it. Compliance teams audit it. The git history is a cryptographically provable record of what was published, when, and by whom.
Built for publishers who know what they need.
Rift is purpose-built for the professionals who are too sophisticated for template-based platforms and too domain-specific for generic enterprise CMSes. If you’ve spent years knowing exactly what you need and watching vendor after vendor fail to deliver it — this is for you.
- Government Digital TeamsManaging policy, program, and regulatory content at scale — where audit trails, workflow governance, and content accuracy are compliance requirements, not optional features.
- Expert Web DevelopersProfessionals who write their own HTML and CSS and want a CMS that treats them as capable technicians, not users to be protected from complexity.
- Organizations on Aging InfrastructureTeams migrating off Drupal 7, legacy Sitecore, or hand-coded HTML who need the migration to take days, not derail a year’s roadmap.
- Teams Building AI-Native WorkflowsPractitioners who need their content corpus to be structured, machine-traversable, and AI-readable alongside being human-readable.
Let’s talk about your next CMS
If you manage large content operations, are planning a migration, or are building AI-native content workflows — I’d genuinely like to connect.
<-- Connect with Heitham on LinkedIn --/>linkedin.com/in/heitham →