Self-hosting
Self-hosted Relay enrollment exists as an early deployment preview. It is not a general-availability Team or Enterprise feature yet.
Before you begin
Contact Pubto before deployment. Define who owns server access, certificates, monitoring, updates, capacity, incident response, and emergency revocation.
Shortest path
Contact support for a controlled Relay enrollmentKeep the endpoint workflow consistent
An enrolled Relay can become an approved choice while projects and endpoints keep the same publish, verify, expiry, usage, rotate, stop, and delete workflow.
Plan operations first
Assign owners for server access, updates, health, certificates, capacity, configuration, and emergency revocation. A second Relay entry alone is not automatic failover.
Understand the preview boundary
Public checkout, user-level self-service deployment, production SLA, SSO, and private Control deployment are not part of the current release.
Before you share
- Relay owner and network path are documented
- Monitoring and upgrades have an owner
- Enrollment and revocation are tested
- Failure behavior is understood
Do not treat a copied install command or a listed Relay as evidence that production failover, isolation, monitoring, and upgrades are complete.