Private namespaces

The same registry, for the markdown your team does not publish: skills, AGENTS.md, CLAUDE.md, rules. Content-addressed versions, the same deterministic audit, install pinned with the same CLI. Hosted on Cloudflare, one origin, no Java, no Kubernetes.

One plan

$29 per month per namespace

14 day trial, no card to start. Up to 50 members, up to 200 files per artifact, unlimited artifacts and versions.

  • Immutable versions by content hash, labels you choose
  • The audit every public artifact gets, on your private ones
  • API tokens per member, read or write, revocable
  • mdr add @yourteam/skill, pinned in mdr.lock like everything else
  • Isolated storage per namespace

Create a namespace

How it works
mdr login --token mdr_...
mdr publish ./skills/release-notes --ns yourteam --kind skill --label 1.0.0
mdr add @yourteam/release-notes@1.0.0
mdr outdated

Tokens come from the namespace page. Publishing sends the folder, the registry hashes every file, audits the entry file and stores the version; a second publish of identical files is the same version.

What stays the same

The public registry stays free and open. A private namespace is the same code path with an owner, members and a subscription in front of it. Questions: jack@dotcomjack.com.