HEY World with Custom Domain Support: What It Could Mean

Updated February 2026 with an expanded edit and clearer framing.

There’s a version of HEY World that would make perfect sense to me.

Not a version with themes, plugins, layout controls, analytics dashboards, or an “audience growth” toolkit. None of that fits what HEY World is trying to be.

The version I mean is simpler: HEY World as it exists today, but published on your own domain.

I wrote about the appeal of that stripped-back model here: HEY World: Everything Else Seems Overkill.

That one change would quietly rewrite what the product is. It would take HEY World from “a neat thing attached to your inbox” and move it closer to “a place you can build”.

Because the editor isn’t the issue. The constraint isn’t the issue. The issue is the address.

Publishing on someone else’s URL

HEY World is not a standalone service. You can’t sign up for it on its own. It’s bundled with HEY Email and only works for HEY for You personal accounts — you need a @hey.com address, and it only works on paid accounts in good standing (not trials).

I’ve written more about HEY’s wider trade-offs here: HEY Email: Brilliant Reinvention or Overpriced Experiment?

That bundling shapes the whole vibe. HEY World doesn’t arrive asking you to choose it instead of Ghost or WordPress. It arrives as a bonus feature inside something you already pay for.

The basic move is simple: you email [email protected] and HEY turns it into a public page at world.hey.com/you (and HEY says the pages ship without trackers, cookies, or JavaScript).

But it’s also clearly hosted. You’re publishing inside someone else’s namespace. Your work lives at an address that exists because HEY chooses for it to exist.

That’s not a moral problem. It’s just a different kind of commitment.

People often treat custom domains as one of those “advanced” features — something you add once you’re taking things seriously.

In practice it’s more basic than that. A domain is your stable name on the internet — it’s why I’m so insistent about using your own domain.

It’s the difference between:

“I wrote this somewhere”

and

“I wrote this here.”

A domain turns writing into a place.

It also solves the long, boring problem that only becomes obvious over time: what happens to your archive when a platform changes direction, changes pricing, changes priorities, or shuts down?

If you publish under your own domain, you keep your address even when you change tools underneath. Your links remain yours. Your back-catalogue doesn’t need to move homes every time the internet shifts.

Without that, even good platforms keep a slight feeling of being temporary — because the address is theirs, not yours.

HEY World already behaves like publishing

What makes the missing domain support so noticeable is that HEY World is already close to being a real publishing model.

It gives you:
• Individual post pages
• An index of everything you’ve written
• Email subscriptions and RSS
• Clean, readable pages with minimal surface area

That’s not “posting to a feed”. That’s a small web presence.

In other words: HEY World already does the work of turning writing into a durable page. It just doesn’t let that page live at your address.

Which means the thing it’s missing isn’t a feature so much as a foundation.

How it would work with your own domain

The practical version of this is straightforward: HEY World would let you map a domain (more likely a subdomain) to your HEY World page.

In reality, it probably works best as something like notes.yourname.com or world.yourname.com. That way it can sit alongside your main site rather than trying to replace it.

Under the hood, it would look like every other “domain mapping” feature: you add a DNS record (usually a CNAME), HEY verifies it, and then your posts resolve on your address instead of world.hey.com/you/….

The important bit isn’t the setup. It’s what happens later. When the address is yours, you can leave the platform without leaving the URL behind.

The “Forever yours” angle cuts both ways

HEY has a strong stance on identity: it doesn’t recycle @hey.com addresses when people leave, and it offers lifetime email forwarding.

That same persistence applies to HEY World. If you stop using HEY, anything you’ve already published can remain live at your world.hey.com/you address. Editing or removing posts depends on having an active account — so it’s not the same as “taking your site down” whenever you feel like it.

My own HEY World page is still there: https://world.hey.com/paul.obrien.

That can be comforting — links don’t rot — but it also raises the stakes. If your writing is going to sit there indefinitely, you start caring more about whether it lives under an address you control.

A custom domain would make that permanence feel like ownership rather than platform policy.

Exporting helps, but the address is the real asset

To be fair, HEY World isn’t a total dead end. You can export your posts while you still have access, and you can rebuild them elsewhere.

If you moved the content to Ghost or another platform, you could keep the same slugs where possible, and set up redirects for anything that changes.

The catch is that you can only do proper redirects when you control the address people are visiting. You don’t control world.hey.com, so you can’t redirect old HEY World links to a new home.

That’s the difference domain support makes. Export protects the writing. A domain protects the links.

What domain support would actually change

Domain support wouldn’t need to turn HEY World into a full blogging system to matter. It would change what the tool feels like — from a convenient place to post to a place you can actually build.

It would also make the writing feel more settled: part of your long-term body of work, not just a side channel.

It becomes easier to invest in short posts and quick thoughts too. When the address isn’t yours, even good writing can feel slightly provisional. Put it on your own domain and it joins your archive by default.

And it lets HEY World sit alongside your other work. Most people don’t want one platform to do everything — they want one address that gathers everything. A domain is how you use different tools without ending up with a fragmented public home.

It doesn’t have to mean complexity

The worry, of course, is that domain support is how it starts. First it’s domains, then it’s themes, then it’s settings, then it’s plugins, and before you know it HEY World is doing the same dance as every other publishing tool.

But it doesn’t have to go that way.

HEY could keep the fixed design, keep the constraints, keep the “email it to the web” workflow — and simply let the finished page live at yourname.com (or something like notes.yourname.com). No theming. No dashboard. Just the same HEY World, but on an address you control.

That’s the difference. This isn’t really a request for more features. It’s a request for continuity.

Why I keep coming back to this

I like HEY World for what it is: a quick, calm way to put writing out into public without turning it into a performance, and without dragging it through social media comments, incentives, and noise.

It’s the same reason I keep coming back to email as infrastructure, not just communication.

But I also know how the web works. The longer you write, the more you care about where that writing lives.

Early on, convenience is everything. Later, continuity becomes the point.

Domain support is the bridge between those two phases.

If HEY World ever adds it, the product doesn’t need to become bigger. It just becomes more real. The writing stops living in HEY’s space and starts living in yours.

And for HEY World, that would change everything.

Get the weekly email

A short weekly roundup on email, privacy, and digital trust. No promos. Unsubscribe anytime.

If you’re considering HEY more broadly, I’ve written a longer piece on whether it’s a brilliant reinvention or an overpriced experiment: HEY Email: Brilliant Reinvention or Overpriced Experiment?