One infrastructure problem.
HTTPS destinations, customer domains, DNS instructions, certificates and registered-host routing. Not a general-purpose cloud platform.
A deliberately narrow infrastructure product
A focused control plane, built in Europe.
subdomain.to is being built so software teams can offer customer-owned domains without turning DNS, certificate issuance and edge routing into a second product.
Control plane · eu-west-3Your origin stays yoursExplicit lifecycle statuses
Custom domains look like a CNAME until they become an operational system.
The real work spans apex records, DNS propagation, ACME challenges, renewal, certificate storage, route isolation, origin policy and support tooling. The product exists to put that surface behind one domain resource without taking ownership of your application hosting.
The principles behind the scope.
These are product and engineering constraints visible in the implementation—not values invented for a brand page.
Statuses before slogans.
DNS, certificate and routing statuses remain separate so a product UI or support team can identify the failing layer.
Your application stays put.
Each HTTPS destination resolves to a validated public origin. The domain layer should not force an application migration.
What exists now
Built from the lifecycle outward.
Control-plane resources
Organization-scoped HTTPS destinations, customer domains, API keys, widget sessions and webhook deliveries.
DNS and certificate workers
DNS sweeps, ACME issuance, certificate validation, renewal scheduling and guarded route publication.
Edge enforcement
Dynamic certificate lookup, SNI/Host matching, explicit route lookup and public HTTPS origin forwarding.
Developer surfaces
REST API, OpenAPI contract, server SDKs, framework packages and an embedded browser widget.
Europe, precisely stated
A European control-plane configuration—not a vague geography claim.
The production configuration places the control plane and certificate storage in AWS eu-west-3. Customer traffic still travels between end users, the edge and the HTTPS destination chosen by the customer; we do not describe all traffic as Europe-only.
- Application control plane
- Symfony · eu-west-3 target
- Source of truth
- PostgreSQL
- Routes and live material
- Valkey + OpenResty
- Certificate persistence
- S3 with KMS encryption
Go deeper than the company page.
The useful evidence is in the lifecycle and the controls. These pages explain what the product does and where its boundaries are.
Follow a customer domain from creation to live routing.
See DNS records, lifecycle statuses, HTTPS destinations and recovery paths.
How it works →Inspect the route before it reaches an origin.
Review hostname filtering, SSRF policy, certificate storage and organization scopes.
Security model →