Skip to main content

Platform overview

The platform's architecture, summarized in five minutes.

What you'll learn​

  • The runtime architecture (gateway, service module, events)
  • The deployment architecture (our cloud platform, Postgres, Redis)
  • What you (a developer) interact with directly

Runtime architecture​

Clients ─── HTTPS ─── API Gateway ─── GraphQL Federation ─── Subgraphs (40+)
│ │
│ ├── Postgres (per service)
│ └── Redis Streams (eventing)
│
Schema registry
  • API Gateway — GraphQL + GraphQL federation. Authenticates, enforces RBAC, routes to service module.
  • Subgraphs — Bun + Elysiajs + GraphQL + Prisma. Each owns one module.
  • Eventing — the event bus. At-least-once, consumer groups for parallelism.
  • Schema registry — the schema registry. Gateway pulls live API schema from CDN.

→ Deep dives: Federation & multi-tenancy, Actor model, Eventing

Deployment architecture​

  • Compute: our cloud platform in centralindia (alpha + prod environments)
  • Database: Postgres with a graph extension
  • Cache + events: Redis (TLS port 10000)
  • Secrets: secret storage, one per environment, private-endpoint only
  • Edge: Cloudflare DNS + CF Access for alpha; CloudFront for static sites

You don't operate this directly — you write code, push to main, and CI takes it from there.

What you'll write​

You're buildingYou'll write
A web/mobile app calling the APIGraphQL queries/mutations via Apollo Client or our Node SDK / Python SDK
A backend service that talks to the platformService-to-service GraphQL calls via internal gateway + Node SDK
A plugin that adds new capabilitiesPlugin development (RBAC, UI, AI, or Vibe plugins)
Async workScheduler or event consumers
An outbound integrationWebhooks

Next steps​