White-label client reports, down to the URL.
Your domain in the link, your name in the preview, no badge on the page. Publish the report as a private page, bind reports.youragency.com, and send one link. The client sees your work under your name; the tooling never shows. And because the page updates in place, the link you sent stays current when the report changes.
No card · 3 pages free · about a minute
How do I white-label a client report?
Publish the report as a private page on Stacktree, bind a subdomain you own, and send that link. The address reads reports.youragency.com, paid plans render no Stacktree badge on the page, and the link unfurls under your name. The client opens it in a browser with no account and nothing to download.
White-label is three surfaces, not one
A client meets a report in three places: the address bar, the page itself, and the link preview in Slack or email. White-labelling means all three carry your identity. The address reads reports.youragency.com rather than a vendor URL. The page shows your work with no host badge in the corner. And the unfurl shows your domain and your title, so the report reads as yours from the preview onward. Most hosting covers one of the three and leaks through the other two; a claude.ai or vendor-subdomain link gives the game away before the page even opens.
The badge, stated plainly
Free Stacktree pages carry a small "Made with Stacktree" footer. That is the deal on the free tier, and it is worth knowing before a client discovers it for you. Every paid plan removes it: from Solo at $19 per month upward, nothing on the page names the host. If the report is billable work, the badge-free plan is the one built for the job, and it is the same plan that includes the domain.
Your domain, two DNS records away
The setup is small. Publish the page, add your hostname in the dashboard, and create the two records it hands you: a CNAME pointing at Stacktree and a TXT proving you own the name. The SSL certificate provisions itself, and the page serves from your subdomain within minutes; nothing else in your DNS moves. The full walkthrough is on custom domains. Solo includes 1 domain, Studio 10 and Firm 25, and a verified domain re-binds to a different page whenever the next engagement starts.
File each client under their own subdomain
One report wants a domain; a client relationship wants an address. Bind a hostname to a client space instead of a single page and acme.youragency.com becomes where Acme's work lives: a portal at the root, each deliverable filed at its own path, one passcode the client types once and keeps for 30 days. Claim your parent domain once, with a single TXT record and one wildcard CNAME, and every client subdomain you add after that needs no DNS work at all.
Per-recipient links: know who opened it
White-label does not mean flying blind. Mint a share link per recipient and each one records its own opens, so "did the CFO read it before the call" has an answer without a follow-up email. Revoke one person's link and the others keep working. None of this puts an account in front of the client: a passcode, or on an email-gated page a magic link to their work address, is the whole ceremony, and passcodes exist on every plan, with three on free.
The link stays yours after you send it
Underneath the branding this is ordinary private hosting: the URL is an unguessable token that is never listed or indexed, and the page stays up until you say otherwise. When the numbers move after delivery, update the page and the link you already sent shows the current version, the pattern sending a report as a link walks through. And if the report came out of Claude, Codex, or another agent, nothing on the page says so. How agencies run that pipeline end to end is on AI deliverables for agencies.
Frequent questions
What counts as a white-label client report? +
Does Stacktree remove its badge on paid plans? +
Do I need to move my website or DNS to white-label a report? +
What does the client see when the link unfurls in Slack or email? +
Can I tell which client contact opened the report? +
How do monthly reports for the same client stay white-labelled? +
Related guides
- Custom domains The DNS shape in full: CNAME plus TXT, automatic SSL, parent-domain claims.
- AI deliverables for agencies The wider pipeline: AI-produced work, finished and delivered under your name.
- Send a client report as a link The delivery pattern: one URL that stays current instead of a PDF trail.
- Share an HTML file with a client Gates, per-recipient links, and revocation, in the technical wording.
- Host a private client demo site The same white-label shape for demos and prototypes, updated as the build moves.
- Pricing Badge-free starts on Solo at $19 with 1 domain; Studio at $79 carries 10.
Sources and further reading
- Cloudflare for SaaS: custom hostnames ↗ The infrastructure behind hostname verification and automatic certificates.
- The Open Graph protocol ↗ The metadata Slack, Teams, and email clients read to build a link preview.
- Slack: unfurling links in messages ↗ How Slack decides what to show when a link lands in a channel.
Send the next report under your own name.
Badge-free from Solo at $19 a month, domain included. Free to try first, no card.
Sign up free →