Docs

Run PubKeySpace locally first, then scale it across a team.

PubKeySpace can be used by one developer as a local inventory tool, or rolled out by an organization through managed deployment and scheduled collection.

Start here

Choose the path that matches how you work.

01

Solo Developers

Use the desktop app or CLI to inspect local SSH, Git, GPG, MCP, passkey, and repository posture without uploading anything by default.

 02

Organizations

Deploy with MDM, run per-user scheduled collection, upload signed reports, and track team posture through collector health.

 03

How It Runs

Understand scan scope, data boundaries, recommended check frequency, update rollout, and App Store tradeoffs.

Release channels

Direct distribution first, App Store later if it fits.

Private alpha and organizations

Developer ID signed and notarized downloads, plus MDM-friendly packages, are the practical path for design partners and managed teams.

Mac App Store channel

The App Store may become useful for solo developers, but sandboxing changes folder access, background collection, helper tools, and CLI distribution.

GitHub remote checks

Organizations can add a GitHub App to inspect repository metadata, branch protection, rulesets, deploy keys, and remote collection health from the team service.