Run with Docker
Install and start Docker Desktop or Docker Engine with Compose v2. Download and extract a release, then open a terminal in its directory.
macOS and Linux
./community.sh startWindows PowerShell
.\community.ps1 startThe launcher pulls the versioned application image, creates unique local credentials and starts CatProof, PostgreSQL and a local HTTPS proxy. Follow the release’s installation guide to manually trust its local certificate, then open https://localhost:8443/signup. Your account belongs to this local installation.
Want to build from source? Clone the repository and run ./community.sh start --build, or .\community.ps1 start -Build. No remote shell pipeline is required. For explicit docker build commands and custom-image startup, see Build a Docker image.
The accountability workflow is included
- Agent records with purpose, accountable business owner, lifecycle and review notes.
- Deliberate links between source identities and canonical records.
- Configured read-only discovery, source observations and freshness.
- Team roles, change history, CSV import and export.
- A fictional demo you can explore before connecting a provider.
See connector coverage for supported scopes and validation limits. Provider access requires your own authorized credentials.
Two source connections per registry
Community Edition 0.2.0 supports two saved, unarchived source connections across all connector types. Paused connections count. Manual records, CSV import/export and the separate fictional browser demo do not use connection slots.
Owners can archive a connection to free a slot without deleting its imported agent records, source evidence or history. Archived sources cannot preview or sync. Restoring a connection requires a free slot and leaves it paused until you enable it.
Upgrading an older registry preserves all existing data. If it has more than two unarchived connections, only the two oldest may read sources until the owner archives unwanted connections. Existing 0.1.0 release artifacts are unchanged.
Local records, explicit connections
Records and encrypted connector credentials persist in local Docker volumes. The encryption key stays in your local configuration. Only the loopback HTTPS port is published; the database and application ports remain internal.
Setup downloads container images and dependencies. Configured source reads contact the selected provider, and browser assets may load third-party fonts. The community packaging adds no installation telemetry.
Keep your database backup and encryption key safe. The release includes backup, upgrade and removal instructions. Stopping the stack preserves data; deleting its volumes does not.
Early access, with visible limits
The repository includes source code, tests, release notes, architecture documentation, security reporting instructions and license terms. CI checks Linux container behavior and PowerShell syntax. macOS and Windows Docker Desktop host validation is tracked separately; a Linux build is not proof of those host workflows.
This laptop bundle is not a public production deployment guide. Governance records do not enforce runtime policies, and source discovery does not certify agent safety or runtime health.
Use GitHub issues for reproducible bugs with sanitized evidence. For managed hosting, use CatProof Cloud.