customerSAX Docs
Getting Started

Service Map

Every service in the platform, its package name, port and framework.

Services and ports

AppPackagePortFrameworkRole
studio@csa/studio3000Next.js App RouterRep console + server proxy layer
docs-site@csa/docs-site3001Next.js (Fumadocs)This documentation portal
ai-assist@csa/ai-assist8080ExpressLLM chat orchestration, tools, memory
bff@csa/bff4000Apollo GatewayFederated GraphQL supergraph
auth@csa/auth4360node:httpLogin, sessions, project selection (REST)
admin@csa/admin4370Apollo subgraphSuperadmin: clients, projects, roles, AI settings, audit
ticketing@csa/ticketing4350Apollo subgraphMongoDB-backed tickets
commerce / commercetools@csa/commerce-commercetools4310Apollo subgraphThe implemented commerce adapter
commerce / contract@csa/commerce-contract— (library)tsc → dist/Platform-neutral GraphQL contract

The commerce adapters for shopify, bigcommerce and sfcc exist as schema-only placeholders (ports 4320 / 4330 / 4340). Only commercetools is wired up and implemented today.

Data stores

  • MongoDB — admin data, tickets, chat sessions and episodic memory.
  • Redis — working (short-term) memory for the assistant; degrades to a no-op when REDIS_URL is absent.
  • commercetools — the live commerce backend (SaaS).

Request entry points

  • Browsers load the studio at :3000.
  • The studio's server proxy layer (app/api/*) talks to the BFF at :4000.
  • The chat stream posts directly from the browser to ai-assist at :8080 (see Resolution Flow for why that asymmetry matters).

On this page