Galaxia Nexus

Chart the Unknown Possibilities of Existence.

Galaxia Nexus is the cross-app routing hub and multichain execution spine for developers, operators, and integrators. Chart the Unknown Possibilities of Existence.

Sign-in returns here with a one-time gid_code. Nexus exchanges it via a same-origin proxy and stores an HttpOnly session cookie (not localStorage). MetaMask is used on Galaxia ID when you choose wallet sign-in — Nexus does not replace or remove MetaMask.

Vercel hosts the status / directory / PQ-catalog shell. Full Postgres / Redis / NATS spine is absent here —/api/ready returning 503 is expected until private infra is configured.

Application type

Developer / Infrastructure API — not a consumer SMB product UI.

Post-quantum

Hybrid ML-KEM / ML-DSA / SLH-DSA libraries are PQ-capable (self-test probe). This is not a quantum-proof guarantee or third-party certification. Probe /api/post-quantum/health.

Persistence

Full Postgres/Redis/NATS spine runs via Docker or private infra. Vercel hosts status, readiness, PQ probes, and ecosystem directory — configure env vars for stateful routes.

Ecosystem

7 core apps linked. See /api/nexus/ecosystem.

Why Nexus exists

Galaxia ships many sister apps. Nexus is the org-coordination and developer routing layer: shared readiness probes, ecosystem directory, intent/RPC-oriented integration points, and a single place to see how identity, compliance, and app surfaces connect — without pretending to be the consumer front door (that is Portal) or the SSO issuer (that is Galaxia ID).

Use Nexus when you are wiring platforms together; use Portal when you are discovering and launching products; use Galaxia ID when you need a session.

Primary customer

Platform engineers, Galaxia app integrators, and operators wiring identity, intents, vaults, compliance, and agent credentials into the ecosystem.