LanOnasis Platform Architecture & Domains

The LanOnasis platform is intentionally split into independently deployable services with strict boundaries. REST and MCP are distinct entry points by design.

High-level map

flowchart LR
  subgraph Web
    User
  end
  User -->|HTTPS| API[api.lanonasis.com]
  User -->|HTTPS| AUTH[auth.lanonasis.com]
  User -->|HTTPS| MCP[mcp.lanonasis.com]
  User -->|HTTPS| DOCS[docs.lanonasis.com]
  User -->|HTTPS| DASH[dashboard.lanonasis.com]

  API -->|Proxy| Services[REST Gateway + Memory API]
  AUTH --> AuthSvc[Central Auth Gateway]
  MCP --> MCPServer[Production MCP Server]
  DASH --> DashApp[Dashboard App]
  DOCS --> DocsApp[Docs App]

  Services -->|SDK/DB| Supabase[(Supabase)]
  AuthSvc --> Supabase
  MCPServer --> Supabase

Domains → Services → Repo paths

Domain	Primary purpose	Backing app/service (monorepo path)	Notes
api.lanonasis.com	REST gateway, Memory API	onasis-core (gateway), Memory endpoints consumed by apps/lanonasis-maas	Public REST entry; proxied via Netlify. See integration examples.
auth.lanonasis.com	Central Auth Gateway	onasis-core (auth gateway)	Canonical OAuth (Device Flow + PKCE). Clients should prefer OAuth over raw keys.
mcp.lanonasis.com	Production MCP server (SSE/HTTP/WebSocket)	apps/mcp-core or apps/mcp-lanonasis (deployment target)	Official MCP endpoint and tool registry.
docs.lanonasis.com	Documentation website	apps/docs-lanonasis	This site.
dashboard.lanonasis.com	Admin/Operator dashboard	apps/dashboard	Authenticated operator interface.
Memory Suite (MaaS)	Memory Service + SDK/CLI	apps/lanonasis-maas, SDK in external package, CLI tooling	Exposed via REST and MCP tools.

For operators: external gateway/proxy infra details are referenced in internal docs and deployment manifests. This page is focused on the public-facing map and cross-links.

Why REST and MCP are separate

• REST (api.lanonasis.com) provides stable HTTP endpoints for products and third-party integrators.
• MCP (mcp.lanonasis.com) exposes a tool-driven protocol suited for agents and IDEs, with long-lived connections and server-sent events.

Where to go next

• Central Auth (OAuth, flows, client guidance): see Auth → Central Auth Gateway
• MCP (endpoints, tools, IDE configs): see MCP → Production Server and MCP → IDE Integration
• Memory Suite (REST, SDK, CLI): see Memory → Overview
• Vendor API Keys (storage, rotation, auditing): see Keys → Vendor Key Management
• Changes & migrations across releases: see Changelog & Migration