Problem
Complex business workflows
Enterprise steps, handoffs, and failure paths are informal or encoded outside the domain that owns them.
Workflows guideCatoids
Product
Authoritative product description for Catoids — purpose, users, capabilities, architecture, and how to get started.
Platform overview
Catoids is an AI-native enterprise application platform for building domain-driven business applications. It centres on modular business kernels, workflow orchestration, decision automation, knowledge-driven architecture, and AI-assisted execution.
It exists because traditional enterprise software often collapses unrelated domains into rigid suites, or leaves teams stitching fragmented systems without clear ownership. Catoids keeps domain mandates explicit and composable.
Shared platform services supply identity, APIs, and operational plumbing. They do not absorb the domain work that kernels and applications own.
Problems Catoids solves
Representative enterprise problems addressed by the platform. Detail remains in documentation.
Problem
Fragmented enterprise systems
CRMs, ERPs, and data platforms reverse-author state when they should act as adapters to domain-owned contracts.
Integration guideProblem
Knowledge silos
Reference rules and artefacts scatter across tools instead of versioned knowledge bound to a domain.
Core conceptsProblem
Manual decision processes
Judgments run outside published policies, with little structure when teams need to revisit outcomes.
API overviewProblem
Rigid application architectures
Monolithic suites and shared mutable stores blur ownership so domains cannot evolve independently.
Architecture guideWho should use Catoids
Intended roles from the product model. Personas beyond this set are not claimed.
Audience
Enterprise architects
Roles that define domain boundaries, kernel mandates, and how applications compose under a tenant.
Architecture guideAudience
Software engineers
Implementers of kernels, workflow adapters, and API clients against published domain contracts.
InstallationAudience
Platform teams
Teams that stand up tenants, pin SDK versions, and operate access, configuration, and cutover.
Implementation guideAudience
Solution architects
Practitioners who map enterprise workflows onto domains, kernels, and integration surfaces.
Domain modellingAudience
Technology leaders
Owners who need a clear platform boundary — what Catoids owns versus what remains outside.
Product overviewCore platform capabilities
Major capability areas — not a feature matrix. Guides and API docs own the depth.
Capability
Business kernels
Modular units that own a slice of domain behaviour — models, adapters, and decision surfaces.
Kernel overviewCapability
Workflow orchestration
Ordered enterprise steps with explicit handoffs and failure paths under domain ownership.
Workflows guideCapability
Decision automation
Published policies evaluate inputs and return outcomes operators can inspect.
API overviewCapability
Knowledge-driven systems
Versioned knowledge artefacts stay tied to domain publication for runtime use.
Core conceptsCapability
AI-assisted execution
Prompts, tools, and retrieval scopes run inside allowlists owned by the domain or kernel.
AI guidePlatform architecture
High-level architecture themes. Technical procedures live in Documentation and Resources.
Architecture
Domain-driven design
Domains publish vocabulary and ownership before workflows or kernels encode unstable shapes.
Domain modellingArchitecture
Modular architecture
Platform services, domains, kernels, workflows, knowledge, and decisions stay separable.
Architecture guideArchitecture
Composable business capabilities
Applications assemble kernels through published APIs — not shared mutable databases.
Kernels guideArchitecture
AI integration
AI assistance is scoped to domain-owned tools and corpora rather than unconstrained agents.
AI guideBusiness kernels
Why reusable kernels exist — not an inventory of every module.
Kernels
Clear mandates
Each kernel states a problem boundary so applications do not become accidental suite modules.
Kernels guideKernels
Owned composition
Kernels depend on platform services for transport and identity; cross-kernel calls stay explicit.
Kernel overviewKernels
Stable vocabulary
Domain terms and decision types belong with the kernel that owns them across releases.
Core conceptsDeveloper experience
How engineering teams approach adoption. Implementation sequences live in Resources.
Developers
Architecture-first
Start from domain boundaries and composition rules before wiring adapters.
Architecture guideDevelopers
Documentation-driven
Getting Started, Guides, API, and FAQ are content collections — not marketing pages.
Browse docsDevelopers
Incremental adoption
Move from install and modelling through workflows and deployment checks in sequence.
Implementation guideDevelopers
Composable implementations
Ship kernels and adapters that publish clear APIs instead of shared stores.
Kernels guideDocumentation
Representative entries from the documentation collections.
Getting Started
Quick start
Create a minimal domain context and confirm read/write path against the Catoids API.
ReadGetting Started
Core concepts
Vocabulary for domains, kernels, workflows, knowledge, and AI-assisted execution in Catoids.
ReadGuides
Modelling a domain
Define domain boundaries, owned models, and vocabulary before wiring workflows or kernels.
ReadAPI
Overview
Authentication, resource model, errors, and versioning for the Catoids HTTP API.
ReadResources
Selected entries from the resources catalog.
- GuidesGuideFeatured
Implementation guide
Suggested sequence for standing up a Catoids evaluation or pilot application.
View resource - WhitepapersArchitectureFeatured
Architecture guide
Structural view of Catoids components, data flow, and non-goals for implementers.
View resource - WhitepapersOverviewFeatured
Platform overview
Concise description of Catoids scope, users, and boundaries for technical and product readers.
View resource
Release notes
Recent published releases from the Release Notes collection.
Release Notes
v0.3.0
Developer tooling and architecture refinements — AI execution scopes, knowledge versioning, and expanded documentation.
ReadRelease Notes
v0.2.0
Kernel improvements and workflow engine — publish kernels, run orchestration instances, and capture decision explanations.
ReadRelease Notes
v0.1.0
Platform foundation — tenant API, domains, authentication, and initial SDK surface.
ReadFrequently asked questions
Entries from the Documentation FAQ collection.
Next steps
Continue into documentation and resources, review releases, compare pricing, or contact us about a tenant evaluation.