Naming Convention Hell: When the Platform Becomes Its Own User

At some point we realised something interesting. Our platform doesn’t just build environments, it also builds itself.

We’re the first organisation using it. The root tenant. The one that enables access for partners and customers. That means we’re both the creator and the user. And that’s where naming suddenly became complicated.

We needed to define the very first organisation. The top of the hierarchy. The one that everything else connects to. Sounds simple, but this identity had to represent both us and the platform itself.

So we did a vote.
There were a few serious options, a few creative ones, and a few jokes.
The result was clear.

Root.

It’s direct, neutral, and it says exactly what it is.
No buzzwords, no branding, just the name of the origin itself.

What we learned

Names define more than you think. They shape how systems understand themselves. Recursive platforms need clear structure. Every layer should know where it comes from. And sometimes the simplest name really is the best one.