Name Brainstorming for Amigos

🎯 Naming Criteria

Must Have

• [ ] Available .com domain
• [ ] No trademark conflicts
• [ ] Easy to pronounce globally
• [ ] Memorable and short (< 10 letters ideal)
• [ ] Works as CLI command (e.g., amigo deploy)

Nice to Have

• [ ] Conveys “open”, “composable”, or “connected”
• [ ] Not blockchain-specific (we’re bigger than that)
• [ ] Positive associations
• [ ] Works in multiple languages
• [ ] Expandable (AmigoHub, AmigoVM, etc.)

🧠 Current Working Name: AMIGOS

Pros

• Friendly: Spanish for “friends” - collaborative feel
• Memorable: Easy to say and spell
• Expandable: AmigoHub, AmigoVM, AmigoNet
• Global: Understood in many languages
• Positive: No negative connotations

Cons

• Generic: Might be hard to trademark
• Domain: amigos.com likely taken/expensive
• Tech Association: Doesn’t scream “developer platform”

📜 Historical Context

Previous Name: PEAGO

• Early project name (see p/amigos/early-technical-insights|early notes)
• Possibly: “Pea” (small, modular) + “Go” (language)
• Or: Persistent + Easy + Go
• Tagline ideas from that era:
  • “Open source for apps, not just code”
  • “Write once, run everywhere with automatic persistence”

💡 Alternative Names

Composition/Building Theme

• Compose / ComposeDev / ComposeOS
• Mosaic - Building from pieces
• Lego (trademark issues)
• Brick / BrickOS / BrickHub
• Stack / StackOS / OpenStack (taken)
• Build / BuildOS / BuildHub
• Remix - Remixing existing services

Import/Connection Theme

• Import / ImportOS / ImportHub
• Importland - Land of imports
• Pipezone - Data/logic pipelines
• Brickhouse - Building with blocks
• Link / LinkOS / LinkedApps
• Wire / WireOS / WireHub
• Connect / ConnectOS
• Mesh / MeshOS / MeshHub
• Weave / WeaveOS
• Bridge / BridgeOS

Open/Transparent Theme

• Clear / ClearOS / ClearHub
• Crystal - Transparent and valuable
• Prism - Splitting light/transparency
• Glass / GlassOS
• Open / OpenOS (too generic)
• Lucid / LucidOS
• Clarity / ClarityOS

Evolution/Next-Gen Theme

• Neo / NeoOS / NeoHub
• Nova - New star
• Genesis - New beginning
• Prime / PrimeOS
• Apex / ApexOS
• Zenith - Peak/pinnacle
• Evolve / EvolveOS

Speed/Simple Theme

• Swift / SwiftOS (Apple conflict)
• Rapid / RapidOS
• Quick / QuickOS
• Simple / SimpleOS
• Easy / EasyOS
• Snap / SnapOS

Community/Collective Theme

• Colony / ColonyOS
• Hive / HiveOS (taken)
• Commune / CommuneOS
• Collective / CollectOS
• Guild / GuildOS
• Tribe / TribeOS

Technical/Developer Theme

• Module / ModuleOS
• Package / PackageOS
• Func / FuncOS (functional)
• Lambda / LambdaOS
• Proto / ProtoOS
• Schema / SchemaOS
• Struct / StructOS

Unique/Made-up Names

• Amigo (current favorite)
• Peago - Historical name (Pea + Go or Persistent + Easy + Go)
• Dago - DAG + Go
• Aligo / Allego - Variations
• Foogo - Foo + Go
• Zephyr - Gentle breeze
• Quasar - Bright cosmic object
• Nebula - Cloud of possibility
• Flux / FluxOS
• Helix / HelixOS
• Vertex / VertexOS

🏆 Top Contenders Analysis

1. AMIGOS (Current)

• Domain: amigos.dev available
• Vibe: Friendly, collaborative
• Risk: Too casual for enterprise?

2. COMPOSE

• Domain: compose.dev possibly available
• Vibe: Technical, clear purpose
• Risk: Docker Compose association

3. MOSAIC

• Domain: mosaic.dev check availability
• Vibe: Artistic, building blocks
• Risk: Less technical sounding

4. PRISM

• Domain: prism.dev check availability
• Vibe: Transparency, splitting light
• Risk: Surveillance associations?

5. WEAVE

• Domain: weave.dev likely taken
• Vibe: Connecting threads
• Risk: WeaveWorks exists

🎨 Brand Extensions

For AMIGOS

• AmigoHub: GitHub for live services
• AmigoVM: The virtual machine
• AmigoNet: The network
• AmigoStudio: Visual IDE
• AmigoCLI: Command line tool
• AmigoCloud: Hosted platform

Domain Strategy

• Primary: amigos.dev
• Docs: docs.amigos.dev
• Hub: hub.amigos.dev
• Registry: registry.amigos.dev
• Status: status.amigos.dev

🔍 Domain Availability Check

To Check

• [ ] amigos.com / .dev / .io
• [ ] compose.dev / .io
• [ ] mosaic.dev / .io
• [ ] prism.dev / .io
• [ ] weave.dev / .io
• [ ] import.dev / .io
• [ ] remix.dev / .io

Social Media Handles

• [ ] Twitter/X: @amigosdev
• [ ] GitHub: github.com/amigos
• [ ] Discord: discord.gg/amigos

💭 Name Testing Questions

1. The Elevator Test: “I’m building on [NAME]” - does it sound professional?
2. The Parent Test: Can you explain it to non-technical people?
3. The Global Test: How’s it pronounced in Asia, Europe, LatAm?
4. The CLI Test: Is amigo deploy better than compose deploy?
5. The Trademark Test: Any conflicts with existing brands?

🎯 Recommendation

Stick with AMIGOS unless a perfect alternative emerges.

Why:

• Already has mindshare in the team
• Positive, memorable associations
• Technical enough with context
• Expandable ecosystem naming
• No major red flags found

Backup Options Ranked:

1. Compose (if available)
2. Mosaic
3. Prism
4. Remix

📋 Action Items

• [ ] Run formal domain availability check
• [ ] Trademark search in major jurisdictions
• [ ] Test with 10 developers for feedback
• [ ] Test with 10 non-technical people
• [ ] Check cultural meanings globally
• [ ] Reserve domains and social handles
• [ ] Design basic logo concepts

See also

• p/amigos/pitch-deck