AgentGem — Client / Server Split

One codebase → two entrypoints → a pure client (no DB) that points at a server it chooses: public, or a private enterprise deployment.

① BUILD — one codebase, two entrypoints (esbuild tree-shakes by entry) ② RUNTIME — the client points at a server it chooses server only esbuild esbuild deploys as deploys as (×N) src/appCommon.ts shared: console + Share/Review/ Benchmark proxies · originGuard · MCP src/client.ts desktop entry (NEW) src/index.ts server entry src/serverAggregator.ts mountAggregator: Aggregator + auth + og + orgs · sole importer of pg / PGlite core/index.mjs — desktop bundle NO aggregator · NO auth NO pg · NO PGlite ✓ (500 gone) server image (Fly Dockerfile) index.ts + full aggregator requires DATABASE_URL default base enterprise base (AGENTGEM_AGGREGATOR_URL) AgentGem Desktop pure API client · no database • Console UI (React) • Benchmark tab → /api/benchmark → benchmarkClient · anon GET • share / review / ingest clients AGENTGEM_AGGREGATOR_URL selects which server this client uses never receives a DATABASE_URL server mode — operator sets DATABASE_URL api.agentgem.ai public · Fly (iad) · index.ts image Neon Postgres public network data k-anon · quarantine producers accruing (opt-in) (needs producer ingest — separate) api.⟨enterprise⟩.internal private deployment · same image Enterprise Postgres their own DATABASE_URL tenant-isolated never touches the public net Legend client (no DB) server / aggregator database (operator-owned) server-mode deployment

Client — src/client.ts

  • Pure API client: console + Share/Review/Benchmark proxies; the Benchmark tab calls benchmarkClient (anon GET) to the chosen server.
  • The aggregator path is unreachable from this entry, so esbuild ships the desktop bundle with no aggregator, auth, pg, or PGlite — the 500 is gone by construction.
  • Points at a server via AGENTGEM_AGGREGATOR_URL; never gets a DATABASE_URL.

Server — index.ts + serverAggregator.ts

  • mountAggregator() mounts the full /api/aggregator surface, auth, OG, orgs on DATABASE_URL Postgres.
  • Sole importer of the heavy server deps — keeps them out of the client entry.
  • Same image runs on Fly (public) and on any private enterprise host.

Two deployments, one image

  • Public api.agentgem.ai → Neon, the k-anon network view (fills as producers opt in and ingest).
  • Private enterprise → their own DATABASE_URL; data stays in their tenant, never mixes with the public network.
  • Enterprise desktops just set AGENTGEM_AGGREGATOR_URL to their API.

One codebase → two entrypoints · client carries no database · server owns the DB (public or private-enterprise) · spec: docs/superpowers/specs/2026-07-12-desktop-client-mode-no-pglite-design.md