Open source project name ideas & instant vetting
Open source projects compete for attention across package registries, code hosts, developer forums, and conference talks. Your name must be easy to search, type, pronounce, and remember, while leaving room for contributors to use it in commands, documentation, and conversation. It should signal the project’s job or worldview without sounding like a generic software product.
Names that work usually connect to a precise technical image, a useful metaphor, a place, or a project origin story. They survive abbreviations, command-line use, and translation into repository names. Names that fail are vague, crowded with category terms, difficult to spell, or tied so tightly to one implementation that future maintainers cannot broaden the project.
Naming rules for an open source project
- Choose a name that stays readable in a terminal command, package declaration, URL, and issue title.
- Use a concrete reference to the tool’s input, output, workflow, protocol, or origin.
- Check package registries and code-host searches for collisions before adopting a distinctive spelling.
- Prefer a name contributors can pronounce consistently during talks, chat, and bug reports.
25 open source project name ideas
Domains checked September 23, 2026. Open a name for a live domain check and trademark search.
Which one would you put on the door?
A communal nesting place for independently built parts that thrive together.
rookery.comrookery.iorookery.corookery.appA real frame that holds fabric taut, suggesting stable structure under active change.
tenter.comtenter.iotenter.cotenter.appIndependent musical lines become one composition, like contributors building in concert.
partsong.iopartsong.copartsong.apppartsong.comThe distinctive trace a tool leaves behind, honoring useful work and visible authorship.
toolmark.comtoolmark.iotoolmark.cotoolmark.appA wooden peg fastening large timbers, an uncommon image of durable connection.
trunnel.cotrunnel.comtrunnel.iotrunnel.appA shared base that lets many new varieties grow without losing resilience.
rootstock.comrootstock.iorootstock.corootstock.appThe dimensions that make a structure sound, giving technical work a built-world metaphor.
scantling.ioscantling.coscantling.appscantling.comThe direction that keeps fabric true, suggesting aligned work without rigid uniformity.
grainline.comgrainline.iograinline.cograinline.appThe internal beam strengthening a vessel, a quiet foundation for collective work.
keelson.comkeelson.iokeelson.cokeelson.appA woven wall made from simple branches, turning many small pieces into shelter.
wattle.comwattle.iowattle.cowattle.appA support stone that keeps a granary dry, protecting useful work from below.
staddle.iostaddle.costaddle.comstaddle.appOne curved segment completing a wheel rim, making interdependence physically visible.
felloe.iofelloe.cofelloe.appfelloe.comA Swedish tradition of learning through making, suited to a project shaped by practitioners.
sloyd.iosloyd.appsloyd.comsloyd.coA human measure that makes a technical project feel approachable and collectively made.
handspan.iohandspan.cohandspan.comhandspan.appA visible row of fasteners joining plates into something sturdier than either.
rivetline.iorivetline.apprivetline.comrivetline.coFrom the workshop practice of securing material before shaping it.
workhold.ioworkhold.coworkhold.appworkhold.comAn old word for shared welfare, giving collective stewardship real moral weight.
commonweal.iocommonweal.comcommonweal.cocommonweal.appA small peg or pipe that directs pressure and flow where needed.
spile.cospile.appspile.comspile.ioAn early form meant for refinement, embracing public iteration over polished pretense.
roughcast.ioroughcast.coroughcast.approughcast.comA simple workshop stop that holds work firmly while hands stay free.
benchdog.iobenchdog.combenchdog.cobenchdog.appA shaping tool that removes material gradually, suggesting patient refinement by many hands.
rasps.iorasps.corasps.comrasps.appA woodland renewed by selective cutting, a natural model for sustainable regrowth.
coppice.iocoppice.cocoppice.comcoppice.appTo gather a sail for later use, a compact image of orderly reuse.
furl.cofurl.comfurl.iofurl.appInterlocking wall panels that protect a room while giving it character.
wainscot.iowainscot.cowainscot.appwainscot.comA general-purpose woodworking plane that turns rough stock into workable form.
jackplane.iojackplane.cojackplane.appjackplane.com
Free to start, no account needed.
Questions
How to choose a name for an open source project company?
Start by listing the project’s central action, the thing it handles, and the story behind its first use. Generate names from physical objects, local terms, protocols, workbench language, or memorable incidents. Test each in a shell command, import statement, URL, README heading, and spoken sentence. Remove names with collisions, spelling traps, narrow implementation references, or unclear ownership.
Are these open source project names trademark-checked?
Each name was screened against well-known brands in the tech space and its domains were checked on September 23, 2026. None has had a full trademark search yet. Open a name to search WIPO, EUIPO and USPTO, or run the Clepen check, which searches for same-name companies and registered marks in your category.
What domain extension is best for an open source project?
Use .org when the project is community governed, documentation led, or contributor focused. Choose .dev when the site primarily serves developers and .com when you expect a broader commercial identity. A country ending such as .uk or .de beats .com when your users, governance, or legal presence clearly centers on that country.