CremindDiscovery document and self-hosting
How Cremind apps discover a Connect relay, and pointers for running your own relay instead of the hosted one at connect.cremind.io.
Cremind apps locate a Cremind Connect relay through a discovery document the relay publishes at a well-known URL. It tells the app everything it needs to start an OAuth flow and subscribe to events — the public OAuth client id, the scopes, the organization's event infrastructure identifiers, and the WebSocket endpoint. By default, apps point at the hosted relay at connect.cremind.io, but because Connect is open source you can deploy and point at your own.
Documentation in progress
The full guide to the discovery document format and self-hosting your own relay is being written.
In the meantime, the discovery endpoint and per-provider setup are documented in the source repo:
github.com/cremind-ai/cremind-connect. You can
also inspect a live discovery document directly — for example with
curl https://connect.cremind.io/.well-known/cremind-connect.
Privacy and trust
What Cremind Connect can momentarily observe, what it provably never keeps, and why being stateless at rest and fully open source makes it auditable.
Contributing to Cremind
How the Cremind monorepo is organized, the two maintainer roles, and the path from a clean checkout to a merged PR.