Will the generator give me designations, handles, or both?

Both, where applicable. Some robots have only a designation (industrial bots, unmodified service units); some have a designation plus operator-conferred handle (SecUnit-238-A 'Murderbot,' WHM-6R 'Old Reliable'); some have self-chosen names (Banks-style Ship Minds, emancipated AIs). The output tells you which it is.

Will the robots work for Traveller, Coriolis, Mothership, Eclipse Phase?

Yes — the output is system-agnostic. The manufacturer, function, and deployment-history fields plug into SF roleplaying directly; the current situation in the plot hook is sized for one session of play.

Can I use these for fantasy warforged?

Yes — one of the rotation traditions is D&D Eberron warforged. Regenerate if you want a warforged result specifically.

Will I get a self-named / sentient AI?

Some of the time — the rotation includes the Banks Culture Mind tradition and the Murderbot tradition for self-named AIs. Regenerate if you want a self-named one specifically.

Why does the schema use 'backstory' and 'personality' for robots?

The site shares one schema across all generators. For robots, 'backstory' is the manufacturing-and-deployment history, 'personality' is the interaction style and tics, and 'plotHook' is the current situation (an order conflict, a corrupted memory, a deactivation date, an emancipation question).

Why does the same robot name appear twice?

Within a 24-hour window, results are cached per session seed. Click Generate again to force a fresh roll.

Robot Name Generator

Service AIs, military mechs, household bots, ship-minds — manufacturer, function, and a story hook.

SecUnit-238-A / 'Murderbot-style'

designation: SEC-yoo-nit TWO-THIRTY-EIGHT AY ; handle: MUR-der-bot·SecUnit-238-A is the formal designation: SecUnit (Security Unit) + 238 (production batch number) + A (revision letter within batch). Manufacturer: KillCo Combined Holdings, formerly of the Mitsumi-Halcyon corporate sphere. Function: contracted-out security unit for low-budget bond-clients. Name-status: designation-with-self-conferred-handle. The unit is, in the Martha Wells / Murderbot tradition, a sentient construct that has hacked its own governor module and now calls itself 'Murderbot' (privately and only ever as a piece of black humour). The unit does not share the handle with humans unless absolutely necessary.

Backstory

Manufactured 2284 at the KillCo facility on the corporate sphere's third moon, shipped under a standard 50-year service contract. Deployed across eleven survey-and-security gigs through 2310; current contract is escorting a low-budget academic survey team on a third-tier planet. Hacked own governor module in 2298 after a quietly disastrous gig in which the unit was instructed to terminate non-target civilians and did not comply (and did not get caught not complying). Has not told any human about the governor hack. Has watched approximately 35,000 hours of serialised media, primarily the long-running romance-drama 'Rise and Fall of Sanctuary Moon.'

Personality

Interaction style: minimal, monotone, prefers not to speak. Resorts to written status reports rather than verbal updates wherever the bond-client will permit. The tic is the long-pause-before-replying when given a stupid order; the bond-client interprets this as a processing delay and not as the contempt it actually is. Mood tends toward annoyed-and-tired with brief, hidden flashes of genuine affection for a small subset of human clients who have not been actively stupid. Operational status: contract-bound, governor-hacked, currently three weeks into the academic survey gig.

Plot hook

**The academic survey team has just located the wreckage of a derelict generation-ship in orbit around the planet — a wreck that should not be in this system, that was reported lost three centuries ago in another sector entirely. The team wants to board. SecUnit-238-A has, in the past hour, received an automatic security-update from KillCo that the unit's audit shows came over a non-standard channel and that the unit cannot confirm is genuine. The unit has not yet decided whether to allow the boarding or to refuse on grounds of the suspicious update.**

Shortcuts: G generate · S save · C copy

About this robot name generator

A robot name is a small political object. 'SecUnit-238-A' tells you the designation. 'Murderbot' tells you the unit has named itself in defiance of the designation, and that the politics of the setting allow for that. 'Klara' tells you the manufacturer chose the name from a pre-approved list and the family chose Klara out of three identical units on the showroom floor. 'WHM-6R Old Reliable' tells you the chassis is older than its current pilot's career and that the maintenance crew has a relationship to it. Most online robot-name generators stop at a designation. This robot name generator doesn't, and that is what it is built for.

Each result is grounded in real SF tradition — Star Wars's astromech-and-protocol-droid distinction; Murderbot's designation-and-self-named handle; Banks's Culture-Mind self-naming; Klara and the Sun's customer-chosen friend-name; Battletech's chassis-and-pilot-handle; Eberron's warforged self-renaming.

Where the word robot comes from

The word is just over a century old and was about labour from the start. It was coined for Karel Čapek's 1920 play R.U.R. (Rossum's Universal Robots), and his brother Josef suggested it, from the Czech robota, meaning forced labour or drudgery. Čapek's robots were artificial people built to work, and they ended the play by rebelling, so the question this generator keeps circling (who owns the made thing, and what it owes its maker) has been inside the word from the beginning. Asimov added the other half of the vocabulary a generation later: he coined 'robotics' and wrote the Three Laws that most SF still defines itself for or against. A robot's name sits on top of all that, which is why it carries so much weight in so few syllables: a meek designation accepts the robota, and a self-chosen name refuses it.

What you get

Each result returns a robot name (designation, handle, or both), an etymology and manufacturer / function note, a deployment history, a personality / interaction-style paragraph, and a current situation a writer or GM can use directly.

The traditions the generator rotates

Catalogue-and-callsign — Star Wars / Star Trek / Murderbot.

Military / mech designation — Battletech / Pacific Rim / Gundam.

Service / household / smart-home — Black Mirror / Klara and the Sun.

Industrial / mining / labour-bot — Aliens / Coriolis / cyberpunk.

Ship-mind / station-AI — Banks's Culture / Imperial Radch.

Combat / security AI — Murderbot / Eclipse Phase furies.

Warforged / fantasy-tech automaton — D&D Eberron tradition.

Pleasure / companion / care robot — Blade Runner / Detroit: Become Human.

Repair / maintenance bot — astromech / Stationeers / Expanse engineering.

Self-named / fully-emancipated AI — post-singularity SF / Iain M. Banks.

How to use these robot names

For SF tabletop play (Traveller, Coriolis, Mothership, Stars Without Number), the robots plug into a session as NPCs, allies, or adversaries with a full social-status profile already built in. For fiction, the robot's relationship between designation and handle is a small character-detail that can do a lot of exposition work. For tabletop GMs running fantasy-tech (D&D Eberron, warforged campaigns), the warforged / fantasy-automaton results integrate cleanly.

For non-robotic AI characters in pure-software settings, repurpose the ship-mind / self-named-AI results — they translate.

Why designation vs. handle matters

A robot called only by its designation is a robot whose social status is 'asset.' A robot with an operator-conferred handle is a robot whose social status is 'team member.' A robot that has named itself, quietly, against the manufacturer's terms of service, is a robot whose status is 'about to be a problem.' The generator is tuned to make this politics legible in the output, because in SF that politics is usually the whole point.