The first successful request proves the path. Production requires a durable domain model, ownership checks, certificate operations, strict routing, lifecycle statuses and failure recovery.
This guide compares responsibilities, not headline feature checklists.
If the ownership decision is already made, continue with the implementation guide that matches your operating model.
Building can be rational when custom-domain infrastructure is strategically differentiating and an existing edge team already owns its failure modes. Buying is rational when the customer experience matters more than the certificate pipeline beneath it.
“Included” means subdomain.to owns that infrastructure responsibility. Your product responsibilities remain explicit.
Each domain continues to change after activation. Model pending_dns → validating → provisioning → active, the exception states misconfigured, failed, suspended and deleting, plus separate DNS, certificate and routing statuses.
portal.acme.euin.subdomain.toA managed domain layer removes infrastructure work. It does not make customer authorization, tenant isolation or origin reliability someone else’s product decision.
Enter your own loaded rate, engineering effort and operating costs. The calculation stays in this browser and starts at zero; subdomain.to does not infer a saving.
A controlled migration separates inventory, DNS change and traffic validation. Preserve a rollback path until the new route is confirmed.
It can route traffic, but it does not by itself provide domain ownership verification, certificate lifecycle management, a customer-facing state model or safe inventory synchronization.
When your differentiated requirements cannot fit the managed boundary and a team is already accountable for edge, PKI and ongoing incidents — not only the initial implementation.
No. You still integrate the API, design onboarding, authorize domain changes, resolve tenants and keep the HTTPS destination reliable.
Compare the managed service with the full ownership surface: implementation, on-call responsibility, certificate and DNS failure recovery, customer support tooling and future migrations.