Custom Domains in SaaS: Ownership Verification, CNAME Targets and TLS Traps
Serving a SaaS from a customer's own domain is not a single CNAME record. Tenant routing, proof of ownership and certificate issuance are three separate problems; which verification methods actually count as proof, the apex and CAA traps, and what keeps a departed customer's name from falling to another tenant.
Serving a SaaS product from a customer's own domain, so that portal.customer.com lands on your application, looks like a single CNAME record. It is not. Every request on that domain forces you to solve three separate problems: deciding which tenant the request belongs to, proving the domain really belongs to that customer, and presenting a TLS certificate the browser will accept. Get any of the three loose and you end up with either an outage or one tenant quietly receiving another tenant's traffic. This post walks through the three problems in order and points out where each one bites.
Routing: what the customer's record should point at
There are two options for the CNAME target you hand to customers. A shared target such as custom.example.net, or a per-tenant target such as t-4f9a2c.connect.example.net. The shared one is easier to explain, but the per-tenant one is better, because the target itself doubles as proof of ownership: only someone with access to that tenant's dashboard can learn a randomly generated target. It also solves offboarding. Delete the target when the customer leaves and the name stops resolving, so no other tenant can claim it later.
The apex domain (customer.com with no label in front) is its own headache. The DNS standard does not allow a CNAME at the apex. Unless the customer's provider offers an ALIAS or ANAME style record, the only option is an A record to a fixed IP address, and once you publish that IP you cannot change it for years. The healthiest decision is to ask for a subdomain in your documentation and to accept the apex only when genuinely required, backed by anycast or a deliberately long-lived address.
On the application side, routing is a table mapping domain to tenant. A Host header that is not in the table must return a clear 404, not fall through to a default tenant. Binding an unknown name to any tenant shows the wrong brand in the browser and, as described below, makes takeover much easier.
Proof of ownership: what each method actually proves
Three methods are common, and they are not equally strong.
HTTP file. The customer places content you provide at a well-known path on the domain. This is weak, because if the domain already points at you, you are the one serving that path. The party who needs to prove ownership passes without doing anything. It is fine for a certificate authority's HTTP-01 challenge, but useless for tenant ownership.
TXT record. The customer publishes a tenant-specific random value at a name such as _saas-verify.portal.customer.com. Whoever controls the DNS zone can do this; whoever merely receives the redirected traffic cannot. This is the correct proof. Query the domain's authoritative servers rather than your own resolver's cache, or the customer will see "not verified" for hours after fixing the record.
Per-tenant CNAME target. As noted above, an unguessable target is a proof on its own. Combined with the TXT record it is the lowest-friction flow: the customer adds one record and the system observes routing and ownership at the same time.
When designing a proof, ask one question: would this check pass even if the claimant did nothing? One method that skips this question is surprisingly common: checking whether the name servers are yours. If the domain sits under your own platform zone, say x.app.example.net, your name servers are authoritative by construction and the check says "verified" for every name in it. The result is one tenant adding another tenant's subdomain and being verified instantly. Never accept names under your own zone as custom domains, and compare suffixes with the leading dot: a rule rejecting anything that ends in app.example.net also rejects an unrelated domain like evil-app.example.net, while a rule on .app.example.net is the right one.
Proof must not be a one-time event. The customer can transfer the domain or delete the record. A daily or weekly re-verification, warning on the first failure and disabling after a grace period, keeps the table honest.
TLS: who obtains the certificate, and how
You obtain the certificate for the customer's domain, and HTTP-01 is your only option. DNS-01 requires writing to the customer's DNS, which you cannot do. HTTP-01 works naturally because the traffic already reaches you. The only requirements are an open port 80 and answering /.well-known/acme-challenge/ without redirecting it to HTTPS. A blanket "redirect everything to HTTPS" rule that also catches this path makes validation fail silently.
With cert-manager on Kubernetes, the whole thing comes down to one Ingress annotation:
Outside Kubernetes, Caddy's on-demand TLS does the same job on its own. The certificate is obtained during the first TLS handshake, and you decide which names are allowed through an HTTP endpoint:
Do not leave the ask endpoint out. It answers "does this domain belong to a verified tenant" with a 200 or a 403. Without it, a certificate is requested for every name that arrives via SNI, and both your rate limit and your disk fill up.
On rate limits, the good news is that the weekly caps of public certificate authorities are counted against the customer's registered domain, so a hundred customers do not consume your quota. The bad news is that repeatedly requesting a certificate for the same exact name has its own separate cap. A setup that does not persist certificate state durably re-requests the same name on every restart, and after a handful of deployments that customer is left without a certificate for days.
Traps
CAA records. If the customer's domain carries a CAA record that only permits a specific authority, yours cannot issue, and the error message rarely says so plainly. Querying CAA during onboarding and telling the customer up front is the only way to avoid the support ticket.
A proxy in front of the customer. When the customer routes the domain through a CDN, the CDN presents its own certificate and yours is used only between the edge and you. HTTP-01 can then be blocked by the CDN's HTTPS redirect. Document this scenario separately.
Requests before the certificate exists. The record is in place, the certificate is not yet issued. The server presents its default certificate and the browser warns. Telling the customer that the certificate arrives within minutes after adding the record, and showing the status in the dashboard, prevents the "it is broken" impression.
Cookies and caches. An application that scopes its session cookie to your primary domain cannot log anyone in on a customer domain. A cache key that does not include the Host header serves one tenant's page to another. Both surface only after routing works, on the first real user.
The departed customer. Removing the row from your table is not enough. If the customer forgets the CNAME in their own DNS, the name still resolves to you. The per-tenant target saves you here: delete it and resolution stops. With a shared target, another tenant can add the same name and, if verification is loose, receive the former customer's traffic.
When not to do this
If all the customer wants is to see their brand, a subdomain such as customer.app.example.net under a single wildcard certificate makes this entire machine unnecessary. No ownership check, one certificate obtained once, no CAA or CDN issues. Custom domain support brings a permanent support burden: DNS propagation, wrong records, expired domains. Reserving it for plans that pay for it is more sustainable than offering it to everyone.
[OK] 30 records · 9 featured · 1 retainer · 20 standard
/02 services
services.tree
> note
· Prices are in USD. Volume discounts of 7% for 6-12 day projects and 14% for 13+ day projects apply. Programs of 100+ person-days are priced individually. Prices are negotiable based on scope, urgency and long-term collaboration.
> ls ~/products/ --open-source
[OK] 2 entries · 1 live · 1 pre-release
/03 products
products.list
liveopen source · mit/prod/01
filex
the self-hosted file manager that embeds anywhere
single go binary · vue/react/web-component embed · 5 storage drivers · realtime collab · rbac · native multi-tenancy · mcp server for ai agents
We build infrastructure, automate everything, and keep systems running.
BRF Tech is a Bursa-based DevSecOps and software consulting firm. We operate across 30 service areas, from Kubernetes cluster management to serverless platform setup, CI/CD pipeline design to AI agent development.
What we do is simple: we set up your systems, automate them, and make sure they won't wake you up at 3 AM. We codify your infrastructure with Terraform, move your deployments to GitOps with ArgoCD, and monitor everything with Prometheus. If something breaks — we intervene before it does.
We're against vendor lock-in. We work with open-source tools, self-hosted solutions, and industry-standard technologies. We build your own serverless platform on Knative, isolate with Kata Containers, manage your secrets with Vault. Every project is delivered with clear scope, clear timeline, clear pricing.
DevSecOps & CI/CD
Kubernetes & Serverless
Infrastructure as Code
AI & Agent (MCP/ACP)
Security & Zero Trust
Full-Stack Development
Self-Hosted Solutions
> grep -i question ~/faq.md
[OK] 3 entries · click to expand
[?]What services are included in BRF Tech's DevOps solutions?▾
We offer CI/CD pipeline setup, Kubernetes cluster management, container migration, infrastructure automation with Terraform, monitoring & alerting, in-house technology installations and DevOps consulting services.
[?]What are your software development services?▾
We offer MVP development, existing software performance optimization, backend API development (Node.js, Go, Python) and full-stack application development. Every project is delivered with minimal technical debt.
[?]Which DevOps tools do you work with?▾
From Kubernetes and Docker to Talos Linux, from Terraform and OpenTofu to Ansible, and across Jenkins, GitLab CI/CD, GitHub Actions, ArgoCD, Flux, Helm and Rancher, we work with industry-standard tooling. For observability and error tracking we use Prometheus, Grafana, Loki, Tempo, OpenTelemetry and GlitchTip; for networking, Cilium and Envoy; for test automation, Playwright, Cypress, k6, Locust, Testcontainers and Trivy. We determine the most suitable toolset together, based on your project’s needs.
Automated build, test and deployment pipelines with GitHub Actions, GitLab CI/CD.
Automated build, test and deploy pipeline setup for existing or new repositories. GitHub Actions, GitLab CI/CD or preferred tool is used. Separate workflows are defined for staging + production environments.
Container architecture migration, cluster setup and orchestration.
Production-ready Kubernetes cluster setup on bare-metal or cloud. Includes Helm charts, Ingress, TLS certificate management, namespace isolation and RBAC.
Cozystack is an open-source cloud platform built on Kubernetes and the VMware alternative we recommend most. Virtual machines run on KubeVirt, while managed PostgreSQL, MySQL, Redis and Kafka services and dedicated tenant Kubernetes clusters are provisioned from the same dashboard and API. Includes installation on your own bare-metal servers on Talos Linux, replicated storage with LINSTOR/DRBD, network isolation with Kube-OVN, tenant and quota structure, monitoring, backup and a disaster recovery plan. After deployment we also handle upgrades, operations and support; since the platform is open source, there are no license fees and no vendor lock-in.
Packages
Virtual machine support on an existing Kubernetes cluster with KubeVirt
$2,800
4–6 person-day
Pilot setup (3 nodes, virtual machines + managed database)
$3,500
5–8 person-day
Production setup (HA + replicated storage + monitoring + backup)
$6,500
10–16 person-day
Multi-tenant private cloud (tenants, quotas, managed service catalog)
Planned, low-downtime migration of vSphere/ESXi environments to Cozystack, OpenStack or VHI.
A planned move to a VMware alternative for environments whose costs rose after Broadcom moved VMware licensing to subscription bundles, or whose renewal is coming up. We start with an inventory of your vSphere/ESXi estate (virtual machines, disks, networks, dependencies), then compare today's license cost with the total cost of the target platform. In most environments the target is Cozystack; OpenStack fits large-scale IaaS needs and Virtuozzo Hybrid Infrastructure fits storage-heavy service providers. A pilot runs on non-critical virtual machines, disks are converted with tools such as virt-v2v and Forklift, and the migration proceeds in waves within maintenance windows, with a rollback plan for every step.
Packages
Inventory + cost comparison + migration plan
$2,400
3–5 person-day
Pilot migration (up to 10 virtual machines)
$3,500
5–8 person-day
Phased migration (up to 100 virtual machines)
$9,750
15–22 person-day
Full data center migration (network + storage + backup)
OpenStack deployment, Neutron networking, Ceph/Cinder storage, upgrades and operations.
OpenStack deployment and operations in your own data center. A containerized, highly available control plane with Kolla-Ansible; Nova (compute), Keystone (identity), Glance (images) and Horizon (dashboard). On the network side, Neutron with OVN, VLAN/VXLAN, provider and tenant networks, floating IPs and the Octavia load balancer; on the storage side, Cinder block storage on Ceph RBD and optional S3-compatible object storage. For existing deployments: health checks, planned upgrades between releases, monitoring and alerting setup, and a backup strategy.
Packages
Health check + improvement report (existing deployment)
$2,400
3–5 person-day
Lab / PoC setup (single region, 3 nodes)
$3,500
5–8 person-day
Release upgrade (existing deployment)
$3,900
6–10 person-day
Production setup (HA control plane + Ceph + Neutron/OVN)
Hyperconverged infrastructure: multi-tenant cloud plus block and S3-compatible storage for service providers.
Hyperconverged infrastructure with Virtuozzo Hybrid Infrastructure, where compute, storage and networking run on the same servers. Block, S3-compatible object and NFS storage on software-defined storage, plus backup storage (Backup Gateway) for backup products such as Acronis. For service providers: a multi-tenant cloud with domains and projects, quotas, a self-service panel and an OpenStack-compatible API. Includes hardware sizing, network design, cluster deployment and expansion, version upgrades and operations support.
Packages
Pre-deployment assessment + hardware sizing
$2,400
3–4 person-day
Version upgrade / cluster expansion
$2,800
4–6 person-day
Hyperconverged cluster setup (storage + compute)
$3,900
6–10 person-day
Service provider setup (multi-tenant cloud + S3 + backup storage)
Migration of existing applications to container architecture.
Migration of existing applications to container architecture. Docker image design, Compose configuration and conversion to Kubernetes manifests. Kata Containers / gVisor can be included for advanced isolation.
Health check of your current environment, capacity planning, platform selection and a roadmap.
An independent assessment of your current virtualization environment (VMware vSphere, OpenStack, VHI or other KVM-based platforms). The health check covers cluster configuration, resource overcommit, storage latency, forgotten snapshots, backup and patch status. Capacity planning measures CPU, memory and storage growth to work out the hardware you will need next. Platform selection decides which workload should run where: Cozystack for teams running containers and virtual machines side by side, OpenStack for large-scale IaaS, VHI for storage-heavy service providers; staying on the current platform is also an option for some workloads. The deliverable is a written report with a cost comparison and a prioritized roadmap.
In-house tools like GitLab, Nextcloud, VPN, mail server.
Installation of tools like GitLab, Mattermost, Nextcloud, mail server, VPN, internal monitoring on company servers. Deployed on Docker Compose or Kubernetes.
DB + cache + code bottleneck identification and resolution.
Profiling of existing application, identification and resolution of bottlenecks. DB query optimization, caching layer (Redis), service-level improvements.
MCP/ACP agents, RAG pipelines, multi-agent orchestration, model serving.
LLM integration (OpenAI, Claude, Gemini, local models), tool-augmented AI agents with MCP (Model Context Protocol) and ACP (Agent Communication Protocol). RAG pipeline, multi-agent orchestration, model serving (vLLM/Ollama). AI layer for existing business processes.
Event-driven data pipeline with Apache Kafka, RabbitMQ, NATS. ETL/ELT orchestration with Apache Airflow, real-time data streaming, CDC (Change Data Capture). Data lake/warehouse design, schema registry, dead letter queue management.
Packages
Kafka/RabbitMQ setup + basic producer/consumer
$3,500
5–7 person-day
ETL pipeline (Airflow + source → warehouse)
$5,200
8–12 person-day
Full event-driven architecture (CDC + streaming + DLQ)
Hands-on technical training for your teams. Docker & container fundamentals, Kubernetes operations, Terraform IaC, CI/CD best practices, AI/LLM integration workshops. Practical exercises in live lab environments, content customized by skill level.
E2E test automation with Playwright, Cypress, load testing with k6/Gatling. Pre-deploy quality gate integrated into CI/CD pipeline, test coverage reporting, visual regression testing. Reduce test writing time by up to 60% with AI-assisted test generation.
Your Collected Personal Data, Collection Method and Legal Basis
Any information that identifies or makes you identifiable is considered "personal data." When you visit our website or use our services, contact information such as your name, surname, email address, phone number, as well as your IP address and browser cookie data may be collected through automatic or semi-automatic means. This data is processed based on the legal grounds specified in Article 5 of the Personal Data Protection Law No. 6698: "being directly related to the establishment or performance of a contract" and "being mandatory for the legitimate interests of the data controller, provided that it does not harm the fundamental rights and freedoms of the data subject."
Purpose of Processing Your Personal Data
Your collected personal data is processed for the purposes of providing and improving our services, fulfilling customer requests, meeting legal obligations, conducting information security processes and managing communication activities. Your data is processed in a limited and proportionate manner for the stated purposes; when the purpose ceases to exist, data is deleted, destroyed or anonymized.
To Whom and For What Purposes Collected Personal Data May Be Transferred
Your personal data may be transferred to public institutions and organizations as required by legal regulations, to our business partners and technical infrastructure providers for the purpose of delivering services, and to lawyers and consultants in legal disputes. Transfers are carried out in accordance with Articles 8 and 9 of the Law, with necessary technical and administrative measures in place.
Your Rights as a Data Subject
In accordance with Article 11 of Law No. 6698, you have the right to: learn whether your personal data is being processed; request information if it has been processed; learn the purpose of processing and whether it is used in accordance with its purpose; know the third parties to whom it is transferred domestically or abroad; request correction if it has been processed incompletely or incorrectly; request deletion or destruction within the framework of conditions set out in Article 7 of the Law; request that the operations carried out be notified to third parties to whom data has been transferred; object to any adverse result arising from the analysis of data exclusively through automated systems; and claim compensation for damages in case of unlawful processing. You may contact us through the communication channels on our website to exercise these rights.
Terms & Conditions
Terms & Conditions
1. Service Scope and Changes
BRF Tech conducts its software development, DevOps consulting, infrastructure setup and technical support services within the framework of these terms and conditions. The scope of service is determined separately for each project and finalized through mutual agreement. BRF Tech reserves the right to update the scope, pricing and technical details of its services, provided that prior notice is given.
2. Privacy Policy
Personal data collected within the scope of our services is processed in accordance with our Privacy Policy. For detailed information, please review our Privacy Policy page.
3. Service Usage and Responsibilities
Clients agree to use the provided services solely within legal and ethical boundaries. BRF Tech reserves the right to suspend or terminate services in the event of misuse, violation of third-party rights, or use for illegal activities. The client is responsible for the accuracy and currency of the information provided within the project scope.
4. Payment Terms
Payment terms are determined on a project basis and finalized through mutual agreement at the start of the project. Unless otherwise specified, invoices are payable within 15 days of project delivery. A monthly late payment interest of 2% may apply to overdue payments.
5. Cancellation and Refund Policy
Cancellation requests must be submitted in writing at least 7 days before the service start date. For projects already in progress, billing is based on the proportion of completed work. No refunds are issued for software and infrastructure components specifically developed within the project scope.