Resources
Integration guide
How Catoids applications integrate identity, events, and external systems without duplicating domain ownership.
- Category
- Guides
- Type
- Guide
- Version
- v0.3
- Published
- Tags
- integration
Integration surfaces
- HTTP API and SDK for kernel and workflow clients
- Identity via tenant bearer tokens
- Optional event consumers for workflow and decision lifecycle events
External systems
Treat external CRMs, ERPs, or data platforms as adapters. Catoids remains the owner of domain models and decision contracts; mirrors should not become a second source of truth for kernel state.
Identity
Map enterprise identities into tenant-scoped tokens. Do not embed long-lived secrets in application repositories.
Event consumers
Subscribe only to events your kernel is mandated to handle. Ignore unrelated domain streams to keep coupling explicit.
Related
Document only — no binary attachment in this phase.
Version
- Version
- v0.3
Related resources
- WhitepapersArchitectureFeatured
Architecture guide
Structural view of Catoids components, data flow, and non-goals for implementers.
View resource - GuidesGuideFeatured
Implementation guide
Suggested sequence for standing up a Catoids evaluation or pilot application.
View resource - TemplatesReference
Developer quick reference
Compact environment, endpoint, and documentation entry points for Catoids developers.
View resource