Kryptkeeper
Open-source PKI · Apache 2.0

Run your own certificate authority, and stop finding out about expiry from an outage.

Kryptkeeper is a self-hosted CA and certificate lifecycle platform. It issues over ACME, EST, SCEP, CMP and Windows autoenrollment, finds the certificates you didn't know about, and renews and installs them without a person in the loop.

Single Go binary · SQLite or PostgreSQL · signed releases

Root CAdual control
Subject
CN=Example Root CA
Key
ECDSA P-384 · PKCS#11
Not after
2046-10-12
Issuing CAOCSP · CRL
Subject
CN=Example Issuing CA 1
Key
ML-DSA-65 + ECDSA P-256 (hybrid)
Not after
2031-10-12
api.example.comrenews in 12 days
Template
tls-server · P90D
Installed
nginx on 3 hosts · verified
Owner
platform-team
Capabilities

The whole certificate lifecycle in one place

Windows and Active Directory

Autoenrollment for domain machines and users, without an ADCS server.

Kryptkeeper serves MS-XCEP and MS-WSTEP natively, so domain-joined Windows machines and users enroll through Group Policy with Kerberos, exactly as they did with ADCS. Templates say whether they are offered to machines or users, ADCS templates can be imported, and a Windows agent and WinRM scanning cover the machine stores.

How it works →
kryptkeeper.example.com/templates

Discovery and inventory

Find the certificates you didn't know about.

Scan your network, pull inventory from other CAs, and watch Certificate Transparency logs for certificates issued in your name. Risky endpoints are flagged and can be accepted as risk with approval.

How it works →
kryptkeeper.example.com/discovery

Automation and enrollment

Speaks the protocols your clients already use.

Servers renew over ACME, devices enroll over SCEP, EST or CMP, and agents or agentless targets install certificates where they are used. Rollouts go to a canary first, and failures wait in one queue.

How it works →
kryptkeeper.example.com/acme

Approvals and guardrails

Sensitive changes need a second person, and show their impact first.

Requests, policies and exceptions can require a second approver. Before anything destructive, Kryptkeeper shows the blast radius: what will break and who owns it.

How it works →
kryptkeeper.example.com/inbox
Paths

Pick your path

Walkthroughs in the order a role needs them, from an empty install to a working setup.

  • PKI administrator

    Stand up your own PKI

    From an empty install to a root, an issuing CA, templates and the first certificate.

    7 steps →
  • Windows and AD administrator

    Replace ADCS for your Windows domain

    Keep Group Policy autoenrollment and move the CA behind it to Kryptkeeper.

    7 steps →
  • Platform and DevOps engineer

    Automate renewal for servers and devices

    Get certificates renewing and installing themselves, and hear about it only when one can't.

    8 steps →
  • Security lead

    Take over an existing estate

    Find what you already have, give every certificate an owner, and bring it under renewal.

    7 steps →
  • Security and audit

    Govern it and prove it

    Least privilege, a second person on sensitive changes, and evidence an auditor will accept.

    8 steps →
  • PKI administrator

    Keep the CA you already use

    Connect the CA you run today, put its root on your hosts, and plan the move to post-quantum.

    4 steps →
  • Platform engineer

    Machine and workload identity

    Identities for workloads, SSH and code signing, approved before they exist.

    4 steps →
  • Developer and integrator

    Integrate with your own tools

    Write a plugin for a device we don't support, and send every event to the tools you already run.

    4 steps →
Extend it

Build your own integrations

Delivery plugins are WASM modules with three functions: Validate, Push and Rollback. They run sandboxed, declare the capabilities they need, and come in signed tiers (first-party, verified, community); a new plugin starts disabled until an admin turns it on. Everything the console does is also in the REST API, with SDKs for Go, Python and TypeScript, a Terraform provider and an MCP server.

Enrollment protocols

Speaks the protocols your clients already use

certbot and acme.sh, network devices, MDM, and Windows clients all enroll against the same CA.

ProtocolSpecTypical client
ACMERFC 8555certbot, lego, acme.sh; http-01, and dns-01 for wildcards
ESTRFC 7030Enterprise devices and services
SCEPRFC 8894MDM and device enrollment with one-time challenges
CMPRFC 4210Certificate Management Protocol clients
MS-XCEP / MS-WSTEP[MS-XCEP]Windows Group Policy autoenrollment
OCSPRFC 6960 / 5019Real-time revocation checks
CRLRFC 5280Revocation lists for offline and legacy clients
Quick start

Running in a few minutes

Docker Compose with SQLite. Set two different secrets in .env; the hub creates its root CA on first boot. The dashboard comes up on port 3000 and the API on 8080.

git clone https://github.com/bpmforge/kryptkeeper.git
cd kryptkeeper
cp env.example .env
# set APP_BOOTSTRAP_TOKEN and KRYPTKEEPER_KEYSTORE_PASSPHRASE
# (different values): openssl rand -hex 32
docker compose up -d

Helm, Terraform, binary, deb/rpm and air-gapped installs are in the deployment guide. Homebrew (Apple Silicon) and the Windows agent MSI are in the packaging guide.

Verify the release

Signed without a key to leak

Checksums and images are signed keyless with Sigstore cosign, bound to the GitHub release workflow. There is no long-lived signing key to fetch or trust.

cosign verify ghcr.io/bpmforge/kryptkeeper:1.2.1 \
  --certificate-identity \
  "https://github.com/bpmforge/kryptkeeper/.github/workflows/release.yml@refs/tags/v1.2.1" \
  --certificate-oidc-issuer \
  "https://token.actions.githubusercontent.com"

Images: ghcr.io/bpmforge/kryptkeeper, -agent, -certmanager, -mcp for linux/amd64 and linux/arm64.

Lab proof

What's proven, what isn't yet

Every claim links to a lab record in the repository. A pass means a real run on a named build. Where the other side was a stand-in, the record says so.

  • Pass 12 real
  • Partial 2 real
  • Mock pass 3 mocks only

Real systems: 12 pass, 2 partial. Mocks only: 3. 1 record includes failed checks.

Not proven yet: 11 items need an account, 8 need partner hardware or a vendor service, 1 comes later.

All tested environments and proof →