.cube TLD
The computational space
has no namespace.
.com said: commerce lives here.
.edu said: learning lives here.
.net said: networks live here.
.cube says: computation lives here.
The Word Has History. The Namespace Doesn't.
The word "cube" has been used in computation for decades — by game designers, mathematicians, and infrastructure engineers. The TLD is unclaimed.
Q*bert (1982) rendered a state machine as an isometric pyramid of cubes — each cube has state, the player transforms state by visiting. Boulder Dash (1984) built a cellular automaton from a grid of cells, each following rules. Intelligent Qube (1997) made the cube a survival resource under pressure.
These designers weren't following a shared theory. They reached for the cube as a unit of bounded, stateful, interactive computation — and it kept working.
Sokoban (1982): push cubes to target positions. Proved NP-hard in 1997, then PSPACE-complete in 2000. The cube-as-positional-unit turns out to sit at the boundary of what is tractable to compute.
The cube captures the minimal structure needed for computational completeness: bounded state, spatial relationships, transformation rules.
When DevOps engineers needed a word for "bounded, isolatable unit of computation with state, interfaces, and neighbor relationships," they kept arriving at the same place. Docker containers (2013): isolated, portable, composable. OLAP cubes: multidimensional data structures. CubeRunner: a container orchestration platform that explicitly names its units "cubes."
The word keeps showing up where engineers build bounded, portable computation. We don't think that's a coincidence, but we're not claiming a grand theory either.
Game designers, mathematicians, and infrastructure engineers have all used the word "cube" to describe bounded, stateful computation. Nobody claimed the TLD. We don't know why. We think it should exist.
Text Finds Its Shape
Just as computation flows around constraints, text flows around structure.
The Namespace Gap
Every era of computing that named its resources deployed them at scale. The computational space has no name.
Agents are deployed now, without names. OpenAI agents have OpenAI IDs. Anthropic agents have Anthropic IDs. None are portable. None resolve across platforms. The namespace gap is not theoretical. It exists today.
"Agents are proliferating. They don't have names yet. That's the gap."
"The collapse is coming. .cube is the name before the collapse."
What .cube Addresses Look Like
Standard DNS. No new syntax. No special tools.
arcade.nebula.cube A game server — bounded, stateful, addressable api.startup.cube An API endpoint — composable, portable model.lab.cube An ML inference endpoint — global name, any provider sensor.factory.cube An IoT device — edge, addressable, discoverable bus.fleet.cube A coordination agent — named, namespaced, portable
Organizations register a second-level domain (e.g., cohesive.cube) and
manage their own cubes — just like cohesive.net today.
Technical Architecture
Standard DNS. Standard protocols. No custom infrastructure.
Standard resolution. A/AAAA/CNAME records. DNSSEC-signed from day one.
The computational space requires authenticated resolution —
you need to trust that model.lab.cube is the model you think it is.
Open registry. Any ICANN-accredited registrar can sell .cube domains. Standard Extensible Provisioning Protocol for registrar integration.
Service discovery via SRV + TXT records. A cube's type, version, platform, and health endpoint are queryable via standard DNS. What service meshes do inside a cluster, .cube does across the internet.
Registration data lookup. ICANN-compliant. Data escrow with daily deposits.
A CoreDNS plugin generating conforming .cube zone files already runs internally. The technical risk is near zero. The innovation is in the namespace, not the infrastructure.
Why .cube — String Quality
A TLD must serve two functions: taxonomy and mnemonic.
".cube wasn't taken. That surprised us."
Registry Economics
.cube is designed to be a lean, self-sustaining registry. Here's the math.
Break-even threshold
5,000–7,500 domains
At $15–20 wholesale, lean operations
Steady-state operating margin
~50%
At 10,000 domains, $18 wholesale
Peer group
.dev, .cloud
Tech-positioned TLDs, not generic TLDs
Pricing Philosophy
We don't compete on price. Low-price registrations produce low renewal rates. .cube targets developers and infrastructure engineers who register domains they actually use — and renew them.
Renewal rate benchmark: .dev at 83%. Low-price TLDs: 3–18%. Wholesale range: $15–$20/year. Retail range: $20–$30/year.
Public Benefit Commitment
A percentage of .cube registration revenue goes directly to open-source infrastructure — tools, standards, and projects that benefit the computational community. This is voluntary, permanent, and public.
- Allocation: 5–10% of net registration revenue
- At 10,000 domains: $9,000–$18,000/year
- Historical precedent: NSF Intellectual Infrastructure Fund (1995)
Cost Transparency
Annual operating costs: $65K–$121K. Break-even: 5,000–7,500 domains. Full breakdown, interactive calculator, and sensitivity analysis on the economics page.
The namespace was always there. We're just building it now.