Hypercerts records live in the repositories of the people and organizations who publish them, spread across many servers. A set of services, most of them operated by the Hypercerts Foundation, lets people sign in and publish records, and lets applications find and read them.
This section describes each service at the level a project needs to integrate with Hypercerts: what it does, how it works, and how your application uses it. Applications can query indexed records through the Hypercerts API, or use the SDK where available. Running your own copy of a service is outside the scope of this documentation for now; each page links to the service's source code.
Records stay in each account's PDS. The relay and Jetstream deliver changes to the Hypercerts API for network-wide queries, while the entryway and CGS handle signing in and writing.
All running endpoints are listed here and nowhere else, so there is one place to keep current as services are added or moved. Production is for live applications. Staging and test endpoints are listed when available; test instances may run development code and can be reset without notice.
