Platform Overview
A practical map of Wacht surfaces and where each docs section fits in a real implementation.
Wacht is split across clear product surfaces:
console: operator workflows and configurationfrontend-api: runtime auth/session/user operationsplatform-api: control-plane and orchestration APIs- SDKs: app-facing integrations over those APIs
Surface diagram
+-------------------+
| console |
| operators/config |
+---------+---------+
|
v
+-------------------+ +-------------------+
| frontend-api | | platform-api |
| runtime auth/data | | control/orchestr. |
+---------+---------+ +---------+---------+
^ ^
| |
+-----+-----------------------+-----+
| SDKs |
| nextjs / react-router / tanstack |
| backend js / rust |
+-----------------------------------+Use this map to choose your starting point
- Product concepts and mental model: Product docs
- Framework-specific app integration: SDK docs
- End-to-end implementation tracks: Guides
- Exact request/response contracts: API Reference
Common implementation shapes
- Frontend app with hosted auth and session state: Use Next.js, React Router, or TanStack Router.
- Backend service enforcing authenticated access: Use Backend JS SDK or Rust SDK.
- B2B org/workspace workflows: Start with Organizations and Workspaces and B2B lifecycle guide.