Self-Hosting a Registry
Run your own Commerce Registry Protocol–compliant registry for full control and interoperability.
1 min read · Registry
Self-Hosting a Registry
You can deploy a Commerce Registry Protocol–compliant registry in your own environment. Self-hosted registries interoperate with gateways and resolvers the same way as the public registry — set REGISTRY_URL in your gateway configuration to your registry’s base URL.
Why self-host
- Data residency and policy — keep registration and verification data in your infrastructure
- Customization — extend workflows, approvals, or integrations behind the same API shapes your gateway already uses
- Interoperability — any compliant implementation can participate in the open protocol
Where to start
- Review the Commerce Registry Protocol overview and registration API.
- Point your gateway at your registry:
REGISTRY_URL=https://your-registry.example.com - Follow Register Your Gateway using your registry’s base URL instead of
https://registry.betterdata.co.
Implementation details for a reference registry server may be published alongside the open-source gateway stack; check the project changelog and main repository for the latest.