About

Content should never wait on a deploy

RuleCMS exists because of a problem its founder watched repeat for twenty years inside large engineering organizations: marketing owns the words on the page, engineering owns the release that ships them, and every copy change has to cross that boundary.

How developers integrate →

Why RuleCMS exists

The content layer is where two teams with different clocks are forced to share one pipeline.

A marketer wants a headline changed before a campaign goes out. The change is one line of text, and it is correct on the first try. It still becomes a ticket, a pull request, a review, a release, and several days of waiting — because the words live inside the application, and the application ships on the engineering calendar.

The usual fix is a content platform that charges for every person who touches it, separates the visual editor from the headless API, and treats staging environments and granular permissions as an enterprise upsell. Teams end up paying per seat for a tool that still cannot let a marketer publish safely on their own.

RuleCMS takes the other position. The visual composer and the headless API are the same product. Permissions, staging, version history, and rollback are included rather than unlocked. Seats are unlimited, because charging per person taxes exactly the collaboration the tool is supposed to create.

Who builds RuleCMS

A content tool for engineering organizations, built by someone who spent twenty years inside them.

Vishal Kumar

Vishal Kumar

Founder & CEO

Vishal has spent more than twenty years building enterprise web applications in JavaScript and TypeScript — as a UI architect and team lead inside organizations where a bad release is measured in revenue rather than pull requests. Angular, React, Node, and AWS have been the day job for two decades.

RuleCMS comes out of the gap he kept hitting in every one of them. Marketing owns the words on the page, engineering owns the pipeline that puts them there, and each side ends up waiting on the other. The composer, the permission model, the publish history, and the SDKs all exist to remove that wait — designed by someone who spent two decades on the engineering side of it.

  • UI architect and team lead for Delta Air Lines, ADP, Deloitte, VMware, Anthem, State Farm, and CarMax
  • Speaker at ng-conf 2020, the official Angular conference, on advanced application architecture
  • Taught full-stack JavaScript to more than 50,000 students as a Udemy instructor
  • Presented reinforcement learning and Markov decision processes at DataSciCon.Tech 2017
  • Contributes to open source most days, with 20+ years shipping production JavaScript and TypeScript

20+

Years building for the web

50,000+

Developers taught

7

Enterprises delivered for

ng-conf

2020 speaker

How RuleCMS is built

Four commitments that shape what gets built, what gets published, and what happens when something breaks.

You reach someone who can fix it

Support does not route through a tier-one queue. Every conversation reaches someone who can change the code that day, rather than someone who files your question for later.

Shipped, not roadmapped

Everything described on this site runs in production today. Nothing here is a coming-soon tier, and no capability is gated behind a sales call before it has been built.

We run on it ourselves

ATL Fluid Art publishes a live consumer site through the same composer, custom component library, and edge cache that a free workspace gets. Bugs reach us before they reach you.

Your content is never trapped

Every published version is kept, and everything you compose is reachable through the headless content API. Content you build here stays portable — that matters more than any promise a vendor makes.

What is already shipped

Every capability below is live in production and available to evaluate on the free plan.

Composing and publishing

Drag-and-drop composer with phone, tablet, and desktop preview, plus direct JSON editing. Three environments, staging-to-production promotion, append-only version history, and visual or JSON diffs with one-click republish to revert.

Delivery on every surface

A React SDK with server rendering, a headless content API, a framework-agnostic custom element for any HTML page, and packages for Angular, React Native, and Flutter. Published widgets are edge-cached and invalidated automatically on republish.

Controls teams actually need

162 permissions across 70 roles, enforced at the data, API, and UI layers. Environment-scoped API tokens, separate staging and production publish rights, and unlimited organizations, teams, and members on every plan.

That surface area is the honest answer to the question every buyer should ask about a content platform: is there enough here to depend on? Read how ATL Fluid Art runs a live studio site on it, or go through the documentation before you write a line of code.

Talk to us before you commit

Evaluating a content platform is a long-term decision. It is worth a conversation first.

If you are weighing RuleCMS against another CMS, planning a migration, or wondering whether your own React component library will work inside the composer, write to vishal@rulecms.com. That address reaches the founder directly.

RuleCMS is operated by RuleCMS, LLC, and built in Atlanta, Georgia.

Explore RuleCMS

Dive deeper into what makes RuleCMS different.

Start with a free workspace

Compose a widget, publish it to staging, and embed it in your site — before you talk to anyone about pricing.