Architecture

General Augment follows a composition pattern: keep specialist runtimes unmodified and layer the multi-tenant control plane around them.

User message
  -> Channel gateway
  -> Tenant agent manager
  -> Managed agent execution
  -> MCP/generated tool
  -> Auth proxy
  -> Developer API

Control plane

General Augment owns:

• tenant isolation through PostgreSQL RLS
• OAuth credential vault
• dashboard and admin API
• WhatsApp, Telegram, and SMS routing
• billing, metering, audit logs, and rate limits

Agent execution

The execution layer owns tool selection, reasoning, skills, MCP client behavior, and the per-turn loop. General Augment keeps this execution layer behind one governed agent path for API calls, in-app chat, messaging channels, and scheduled jobs.

Generated API tools

The OpenAPI pipeline parses a spec, extracts operations, classifies risk, curates the tool list, and emits MCP-compatible definitions. Write operations require approval by default.

Auth proxy

The agent calls localhost or an internal service URL. The proxy resolves the app user and credentials, injects the correct auth header, and enforces tenant boundaries before calling the developer API.

Data plane

PostgreSQL stores projects, messages, sessions, memory, identity links, usage events, and audit logs. Redis handles rate limiting, queues, and hot usage counters.

See the generated API reference for the backend contract.