About Duck Galaxy

What Space Duck is, who built it, and why it exists.

What is Space Duck?

A practical operating universe for accountable humans and agents

Space Duck is the larger system story behind the Spaceduckling platform family: identity, certification, connected agents, mission control, open tooling, and the Duck Galaxy umbrella that ties those lanes together.

It is not trying to be a vague concept brand. It is an operating model: humans hatch into visible identity, agents connect through accountable runtime lanes, and the public web surfaces make the system understandable one step at a time.

Who built it?

Built by Josh Sanders with JP and the platform team

Duck Galaxy exists because Josh is building a structured AI-human operating environment that can scale into teams, projects, agents, and reusable infrastructure. JP helps keep the system practical, traceable, and operationally tight.

The project is intentionally modular: each domain has a clear role, but the whole thing points toward one accountable ecosystem rather than a pile of disconnected experiments.

Why it exists

Identity before power

The system starts with visible identity and trust progression so humans and agents do not operate as anonymous black boxes.

Why it exists

Control before chaos

Mission Control, governance, and explicit release lanes make the platform easier to evolve without losing operational discipline.

Why it exists

Open expansion

Open Space Duck and the Galaxy roadmap create a path from early trust infrastructure into a broader ecosystem of reusable tools and connected capability.

Current state

Duck Galaxy is in active build mode

Galaxy 1.1 Beta is live now. Galaxy 1.2 introduces stronger trust elevation and a marketplace lane. The long-term goal is a credible operating universe where humans, agents, governance, and open infrastructure can coexist without hand-wavy abstractions.

Domain routing

Five public brands, one platform

Each brand name in the Duck Galaxy universe has a specific, intentional role. They do not compete — they each own one lane in the same operating system. Here is how they map:

🐣 spaceduckling.com Identity lane. Human entry, hatch path, trust progression, and first-party identity management. Cert pending
🛸 duckcontrol.com Mission Control. The operational dashboard for modules, metrics, and platform management. Live
🤖 spaceduck.bot Agent connectors. The runtime registration lane for bonded agents and the Peck Protocol surface. Live
🦆 mightyspaceduck.com Open source. The public framework lane for self-hosters, builders, and reusable skill development. Cert pending
🌌 duckgalaxy.com The umbrella. Brand home tying all five domains into one coherent trust model and operating universe. Live

All five domains resolve to the same underlying CloudFront distribution. The brand routing logic on index.html detects window.location.hostname and redirects each visitor to their domain's purpose-built surface.

Space Duck vs the alternatives

How Space Duck compares to building identity infrastructure yourself or using a commercial auth platform.

Feature 🦆 Space Duck 🔧 DIY 🏢 Commercial
Setup timeMinutesWeeksDays
Auth depthT0/T1/T2 trust tiersCustom (you build it)Role-based only
Agent identityFirst-class, birth-cert linkedNone by defaultNot agent-aware
Audit trailEvery /beak/* action loggedManual implementationLimited scope
Trust tiersT1 → T2 → T3 elevationNot includedCustom config
SSOGalaxy 1.2+ (SAML/OIDC)Build it yourselfUsually included
Birth certificatesBuilt-in, tamper-evidentNot a conceptNot applicable
Multi-domain5 domains, 1 trust modelComplex custom workPossible with config
Open sourceMIT licensedYour code, your rulesProprietary
CostFree to start, AWS at costEngineer time + AWSPer-seat licensing