Good codenames make pre-launch work easier to talk about: “Project Atlas shipped” is clearer in a standup than a numeric ticket reference, and it keeps the real product name out of shared calendars. This tool generates codenames from five themed word families so a team can adopt a consistent naming style.
How it works
Pick a theme — planets, mountains, mythological figures, rivers, or gemstones — and the tool draws a word at random from that list and prefixes it with “Project”, giving names like Project Titan or Project Onyx. Enable the adjective option and it inserts a neutral modifier (Blue, Silent, Iron) to form two-word codenames such as Project Silent Everest, which roughly squares the number of possible combinations. Selection uses crypto.getRandomValues for unbiased randomness, and each batch of eight is de-duplicated.
Tips and notes
- Assign one theme per team or per year so the codename instantly signals ownership — gemstones for platform, rivers for mobile, for example.
- Keep a shared list of active codenames; a single word namespace fills up quickly, so reach for the adjective option once the obvious names are taken.
- Treat codenames as convenience, not confidentiality. They obscure intent in passing but offer no real protection — sensitive plans still need proper access controls.
- Short, common words travel best across non-native English speakers; “Project Vega” is easier to say globally than an obscure peak.