About Nabaname

Naming a product looks like one decision. In practice, it is several different jobs tangled together. Nabaname keeps the whole process in one place.

Why naming is hard

You are not just trying to think of a good word. You need to:

  • generate enough strong candidates to discover what you like
  • check which domains are actually available
  • find useful domain variations when the obvious address is taken
  • choose a name that fits the brand you have or sharpens the one you are still defining
  • hear how the contenders land from other points of view

Each step is doable on its own. Moving back and forth between them is what turns naming into a grind.

What Nabaname does

Nabaname works through that loop with you. It uses your brief to generate a broad range of names, checks domains as it goes, and explores useful variations when a domain is taken. Each candidate stays on one board with its meaning, fit, and domain evidence. When you compare finalists, you can add outside perspectives there too.

The range matters. Good naming needs enough material to compare, discard, combine, and build on. Sometimes the final name is already on the board. Sometimes one candidate leads you to it. Both are useful outcomes.

Use it from your assistant

You can also use Nabaname from Claude Code, Cursor, Codex, or another MCP-compatible assistant. Names and domain evidence land on the same board you use in the browser. After you sign in, the connection instructions are in MCP settings.

The reference

We publish what we learn while building Nabaname in the reference. It covers how availability checks work, which naming rules hold up under scrutiny, and the techniques behind names that last. No account required.

Who makes it

Built by Deep Noodle.