Product
The distribution layer for AI standards.
Cendis gives engineering orgs a governed registry to publish, version, and distribute AI development assets — so every team works from the same source of truth.
Publish & Govern
Own every standard at the source.
Centralized registry
Publish rules files, skills, templates, and commands to a single governed registry. Every asset gets a version, an owner, and an approval workflow.
Role-based access
Publishers govern what ships. Consumers pull what's approved. Clean separation of concerns, enforced by the platform.
Approval workflows
Multi-stage phase gates. Version comparison diffs. Automatic notifications. Nothing ships without sign-off.
Consume & Sync
Pull, don't copy-paste.
CLI-native workflow
One command to pull any approved asset into your local environment. No browser, no manual downloads, no Slack threads asking 'where's the latest version?'
Automatic placement
Assets land exactly where they belong — .claude/skills/, .cursorrules/, project templates. No guesswork about directory structure.
Version pinning
Pin to specific versions or track latest. Lock critical assets. Get notified when updates are available.
Drift Detection
Know when teams fall out of sync.
Automatic drift scanning
Cendis continuously compares local assets against the registry. When a team's copy diverges from the approved version, you know immediately.
Diff visualization
See exactly what changed — line-by-line diffs between local and registry versions. Understand drift before deciding how to resolve it.
Resolution workflows
Accept the registry version, keep local changes, or merge. Teams stay aligned without losing legitimate customizations.
Asset Taxonomy
Four asset types, purpose-built
Every artifact your team creates for AI development has a type. Cendis governs each one through its full lifecycle.
Skill
A reusable AI capability unit — an action your AI tools can execute on demand.
Command
A slash command callable by name during an AI coding session.
Template
A scaffolding template for new projects or files — consistent starting points.
Rules File
A configuration file — CLAUDE.md, .cursorrules, AGENTS.md, or similar — that governs how AI behaves in a codebase.
Scope Hierarchy
Built for how AI tools are configured
Modern AI coding tools use layered configuration — from org-wide policies down to project-level rules. Cendis governs which assets are approved at each level, across every tool your teams use.
Enterprise (org-wide)
Cendis manages
Project
Cendis manages
User
Cendis distributes to
Conversation
Assets active here
CLI
First-class terminal experience
Engineers pull approved assets directly into their environment. No context-switching, no manual downloads.
Integrations
Works with the tools your team already uses
Cendis's governance engine is tool-agnostic. Approval workflows, version control, and drift detection work the same regardless of which AI tool your teams use.
Claude Code
LiveDeepest integration — skills, commands, and rules sync directly into .claude/ configuration
Cursor
Coming soonNative .cursorrules distribution and governance
Codex
Coming soonAGENTS.md and rules file governance
REST API
LiveIntegrate any AI tool or internal system via the Cendis API
Trust & Security
Enterprise-grade security from day one
Your AI standards are sensitive. Cendis treats them that way.
Row-Level Security
Organization data is isolated at the database level. Every query is scoped to your org.
Encrypted at Rest & In Transit
TLS everywhere. Tokens are hashed. API credentials are encrypted at rest.
Role-Based Access Control
Granular permissions per workspace. Publishers, consumers, and admins have distinct capabilities.
Full Audit Trail
Every approval, version change, and distribution event is logged and queryable.
Ready to ship your AI standards?
We're onboarding teams in waves. Get on the list and we'll reach out when your spot opens.