// roadmap

From owning names to selling them everywhere

Six stages, in plain language. Each one answers a single question: do we own it, does it work, is it safe, can we run it, can people buy it, and who is selling it for us.

secured · always adding in progress next up

// the six stages

What we do, and why it matters

The left column is the plain explanation. The highlighted line under it is the commercial reason the stage exists. The checklist is the actual work.

stage 01

Own the address space

secured · always adding

Before anything can be sold, the names themselves have to be ours. The namespaces we operate today are already acquired and held, with clear legal rights to run each one. This stage never really closes: whenever a strong name or a new sector opens up, we acquire it and add it to the roster.

commercially
This is the asset, and it keeps growing. Every name registered later is inventory sold out of address space we already own — and each new acquisition adds fresh inventory on infrastructure that is already paid for.

  • Parent domains acquired and controlled
  • Current namespaces secured under them
  • Legal ownership and right to operate
  • Ongoing: acquire strong new names and sectors as they become available

stage 02

Make them behave like real domains

in progress

A name is only useful if the internet resolves it. This architecture is being built out now: authoritative directory servers for each namespace, with redundancy and monitoring, so a namespace address loads anywhere in the world exactly like any other domain.

commercially
Answers the first objection a buyer has — 'will it actually work?'. It runs on the same plumbing every domain uses, and this is the work in progress right now.

  • Authoritative DNS infrastructure
  • Delegation for each namespace
  • Signed, tamper-proof records (DNSSEC)
  • Redundant nameservers and monitoring
  • Registration rules and renewal lifecycle

stage 03

Independence and trust between businesses

in progress

Two unrelated businesses can sit inside the same namespace, so each one must be fully walled off from the other — its own padlock, its own logins, no shared browser data. We get the namespaces recognised on the list browsers use to treat them as separate territory.

commercially
Turns a namespace into address space a business can trust for payments, logins and customer data — the difference between a novelty and something you'd put on a signboard.

  • Public Suffix List recognition
  • Cookie and session isolation per business
  • SSL/TLS certificate architecture
  • Certificate-issuance policy controls
  • HTTPS-first security defaults

stage 04

Run it on registry-grade systems

in progress

We partner with an established registry service provider to run the back office: who owns which name, when it renews, public lookup records, abuse handling and secure backups. The same platform class that runs recognised extensions.

commercially
Buy proven infrastructure instead of building it. Scales to hundreds of thousands of names without adding headcount, and gives registrars the standard systems they already integrate with.

  • Registry management platform
  • Registration database and lifecycle
  • Standard provisioning APIs (EPP)
  • Public lookup records (WHOIS/RDAP)
  • Availability checks and instant registration
  • Renewals, transfers, deletions, recovery
  • Abuse handling and compliance
  • Backups, escrow and continuity

stage 05

Get on the shelves people already buy from

next up

Businesses don't buy names from a registry — they buy from the shop they already use. We connect to registrars and resellers so a namespace name appears in the same checkout as any other domain.

commercially
Distribution instead of demand creation. Existing storefronts, existing payment rails, existing traffic — we supply the inventory and the renewal revenue compounds annually.

  • Registrar and reseller partnerships
  • API/EPP integration
  • Pricing, billing and renewal flows
  • Fully automated registration

stage 06

Launch, and keep widening the catalogue

next up

Open to the public sector by sector, with positioning aimed at the businesses each namespace is named for. Then bundle the name with the tools they were going to buy anyway — website builders, billing and point-of-sale platforms.

commercially
Recurring revenue per name, per year, plus channel partners who bring volume. Every new sector added is new inventory on the same infrastructure.

  • Public launch of the namespaces
  • Category-specific marketing
  • SaaS, POS and web-agency partnerships
  • Onboarding businesses and developers
  • Expansion into further namespaces

// why it compounds

The shape of the business

One build, many sectors

The DNS, security and registry work in stages 02–04 is done once. Adding the next namespace reuses all of it, so each new sector costs a fraction of the first.

Revenue that renews

A name isn't a one-off sale. It renews every year for as long as the business trades — and a business rarely changes the address printed on its board, its bills and its listings.

We aren't the shopfront

Registrars carry the customer acquisition, support and payments. We supply address space and the systems behind it, which keeps the operation lean as volume grows.

Priced to be kept

A flat, affordable yearly price is what makes a small business renew for a decade instead of abandoning the name after year one. Retention is the whole model.