Docket

OWNING YOUR DATA

Your public roadmap is a URL you do not own

The address your customers bookmark, your docs link to and your support team quotes usually belongs to someone else.

6 MIN READ Last updated 23 August 2026

Most public roadmaps live at a URL the vendor controls: their subdomain, or their domain with your name in the path. Every link built to it, every bookmark, every doc reference points at an address you do not own, and you find out what that costs the day you try to leave.

Checked 22 August 2026, against each vendor's own pricing pages. This page is one part of a larger guide: see what feedback tools actually cost.

What happens when your roadmap lives at someone else's address?

There are two common patterns, and most teams end up on one without choosing. The first is a vendor subdomain: yourcompany.vendor.com, provisioned automatically the day you sign up. The second is the vendor's own domain with your name in the path: vendor.com/yourcompany. Either way, the vendor holds the domain, the DNS and the decision about whether that address keeps working tomorrow. It is the default setup for almost every hosted feedback tool, invisible right up until you need it not to be.

Why does every link to it build value somewhere else?

Every customer bookmark, every internal doc that references the roadmap, every support reply that quotes it, is a small vote of confidence pointed at wherever that URL sits. Search engines and AI systems read links as evidence about the domain they land on, not about you specifically. Build up a year or two of those against a vendor's subdomain, and the vendor's domain accrues the standing, not yours. Leave, and none of that comes with you: you start again from a new address, one link at a time. Custom domains and subdomains for a support site covers the DNS mechanism behind why a subdomain is generally treated as separate from the domain it hangs off; the point here is narrower. Whichever pattern your roadmap sits on, it is an address the vendor controls unless you have moved it.

What happens to that address when the vendor closes or rebrands?

It goes with them. Pendo's classic Feedback product, formerly Receptive.io, sunset on 1 August 2026. Delighted, a Qualtrics product, closed in June 2026. GetFeedback Direct, a SurveyMonkey product, is announced for discontinuation on 31 December 2026. Any public roadmap that lived on one of those products' own domains stopped resolving the day the product did, taking every link and bookmark pointed at it down with it. The graveyard has the complete, dated list since 2025. Even a rename rather than a shutdown can move the address, and that same list records one.

Which tools let you move it to your own domain, and at what price?

FeatureOS lists custom domains from its Starter tier, $60/mo; there is no free tier at all. Jira Product Discovery gates custom domains to Premium, $25/creator/mo, not Free (3 creators, free forever) or Standard, $10/creator/mo. LogChimp is worth reading twice: its free, self-hosted build includes a custom domain, but Boards, Roadmaps and Comments themselves are Pro-only, $24/mo billed yearly, on that same build. A custom domain with nothing to put a roadmap on is not the whole answer. Docket includes a custom domain on its free edition, no card or account needed.

For the rest of the category, this is genuinely not confirmed: check any vendor you use directly rather than assuming from this list.

On the vendor's domainOn your own custom domain
The addressOwned and controlled by the vendorOwned by you, on your own registrar and DNS
Links, bookmarks and doc references others madePoint at the vendor's domainPoint at your domain
If the vendor closes, rebrands or is acquiredThe address goes with itThe address survives; you re-point the DNS record
The content behind the addressThe vendor's, wherever it is hostedStill the vendor's, unless it is self-hosted too

Is a custom domain enough on its own?

No, and this is the honest caveat. A custom domain pointed at a vendor's servers moves the address to your side of the ledger, but the content behind it still sits in the vendor's database, under the vendor's terms. If that vendor closes, your domain keeps existing but resolves to nothing, because there is nothing left on the other end to serve it. A custom domain solves who owns the address. It does not solve who owns the data, and the two need separate answers.

Your own support centre, in your own repository

One payment, no subscription, unlimited products.

How do you check what you own today?

Look at the URL your roadmap is published at right now. Is it a subdomain carrying the vendor's name, or the vendor's own domain with yours in the path? Check your account settings for whether a custom domain is offered, and which tier it needs. Search your own docs for how many places already link to the current address. Confirm you hold the registrar and DNS access for whatever domain you would point at it.

What can a redirect rescue, and what can't it?

Set up a custom domain in good time and moving hosts later is simple: change one DNS record to point your address at the new destination, and every existing link, bookmark and doc reference keeps working without anyone noticing.

If you never set one up and the vendor's own URL disappears, because the domain lapses or the product is discontinued, a redirect cannot rescue what you never controlled. Nobody can forward from an address they do not own, and once a vendor lets a domain go, anyone can register it next. The only real recovery is publishing the new address as widely as you can and asking whoever runs your highest-value links to update them by hand. It gets you some of the way back. It does not get you the address you had.

Where does this leave Docket?

Docket's roadmap lives at whatever address you point your own DNS at, from the free edition onward, no card or account required. There is no separate custom-domain tier to unlock, because the whole site, roadmap included, is Markdown files in your own repository, served from wherever you choose to host it. That answers both halves at once: the address is yours because you registered it, and the content is yours because it was never anywhere else.

That is not the only way to solve either half. A custom domain from a vendor that offers one, pointed at their servers, fixes the address. Self-hosting an open-source board fixes the data. Doing both usually means picking a tool built to let you, rather than assuming any single feature ticks both boxes.

Frequently asked questions

Why does it matter that my roadmap's URL belongs to a vendor?

Because every link, bookmark and doc reference anyone makes to it points at an address the vendor controls, not you. If you switch tools, or the vendor closes, that address does not come with you, and you start again from a new one.

What happens to my roadmap's address if the vendor shuts down?

It stops resolving. The graveyard lists the feedback and product-planning tools that have closed, rebranded or gone quiet since 2025, several with dated shutdown dates. Any roadmap that lived on one of those products' own domains went with it.

Does a custom domain fully solve this?

No. It moves the address to a domain you own, so you can re-point it if you switch hosts. It does not move the data, which is still the vendor's, on the vendor's servers, unless the tool is also self-hosted. The two are separate problems with separate fixes.

Which tools let me put a roadmap on my own domain?

FeatureOS includes custom domains from its Starter tier, $60/mo. Jira Product Discovery gates them to Premium, $25/creator/mo, not Free or Standard. LogChimp's free self-hosted build includes a custom domain, though the roadmap feature itself needs their Pro tier, $24/mo billed yearly. Docket includes a custom domain on its free edition. Check any other vendor directly.

How do I check what I actually own today?

Look at your roadmap's current URL: does it carry the vendor's domain or your own? Check your account settings for a custom domain option and which tier it needs. Search your own docs for how many places already link to the current address, and confirm you hold the registrar and DNS access for whatever domain you would point at it.