Himalayan village and mountain landscape

Jade CMS

Structured publishing, without the heavyweight CMS.

Structure content, draft updates, upload assets, and deliver clean entries to blogs, websites, docs, and product surfaces from one workspace.

What belongs

Core modules for a serious first version.

The first version stays practical: content CRUD, assets, roles, API keys, and tenant boundaries before heavy workflow machinery.

Jade gives organizations the editing surface they need while keeping the system small enough for Kabeli to operate, extend, and trust across client projects.

01

Organize

Keep every client, site, and content type in a predictable place.

Multi-site context

Organizations, sites, users, and roles stay scoped.

Collection builder

Create pages, posts, reports, teams, and custom records.

02

Operate

Give editors the everyday publishing tools they actually need.

Drafts

Keep drafts private until content is approved.

Assets

Store files as portable CMS records.

03

Secure + deliver

Publish clean content without losing control of who can change it.

APIs

Serve published JSON with scoped keys.

Access

Roles, scopes, and audit history are built in.

Operating rules

Simple enough to run. Strict enough to trust.

If a client website depends on it, the CMS cannot feel experimental.

Every tenant-owned record carries workspace context.

CRUD stays boring before workflow gets clever.

Draft data and public responses remain separate.

Storage providers never become the content collection.

Delivery

Publish your content, the design stays yours.

Jade stores structured entries, exposes the published version, and leaves every frontend in control of the experience.

Publish

Only approved entries and asset metadata become public.

Preview

Drafts stay behind scoped preview access.

Render

Websites and apps choose the routes, layout, and components.

Who it serves

Built for editors, owners, and developers on the same project.

The product speaks to the same practical audience as Kabeli: organizations that need dependable software more than novelty.

Editors

Clear workspace context, draft states, media, and content forms that do not require touching code.

Workspace owners

Roles, API keys, activity, publishing history, and a CMS foundation that can serve more than one site.

Developers

Stable endpoints, scoped credentials, predictable payloads, and content that stays portable.

Start

Create the workspace, structure the content, publish only what is ready.

Jade keeps the CMS focused on the control plane, so each website can stay fast, custom, and cleanly integrated.