Related
Product scope
Understand what Catoids is before comparing editions.
ProductCatoids
Pricing
How Catoids is packaged — editions, adoption stages, and when to contact the team. Not a checkout.
Packaging for Catoids tenants. Currency amounts are placeholders until commercial terms are published. This page does not process payments.
Pricing philosophy
Catoids is packaged as an enterprise application platform. Editions map to adoption stages — evaluation, pilot, production, and organisation-wide rollout — rather than self-serve subscription catalogues.
Organisations should evaluate packages against domain ownership needs: kernels, workflow orchestration, decision automation, knowledge integration, and how AI assistance is scoped. Product scope is described on the Product page; this page only describes packaging.
Commercial engagement is consultative. Placeholder amounts below are structural until commercial terms are published. Enterprise and Custom packages are scoped with the team before a standard edition applies.
Platform editions
Representative editions by adoption stage. Structure matters more than the placeholder price labels.
Community
Developers and architects evaluating the platform
Evaluate Catoids with a bounded domain and advisory workflow policy.
Placeholder
Commercial terms not published — use documentation to evaluate.
- Bounded evaluation tenant
- Core domain, kernel, and API surfaces
- Advisory workflow and decision paths
- Documentation-driven support
Common pilot path
Professional
Platform and solution teams standing up a first production domain
Run a production pilot for a single domain with enforced workflows.
Placeholder
Commercial terms not published — contact us for professional packaging.
- Production-oriented tenant capacity
- Workflow enforcement and decision explanations
- Knowledge versioning for the owning domain
- Named technical contact path
Enterprise
Enterprises running multiple kernels and domains
Multi-domain production with organisation-grade review and operations.
Placeholder
Commercial terms not published — contact us for enterprise packaging.
- Multi-domain / multi-kernel capacity
- Scoped AI allowlists and knowledge ownership
- Security and procurement review support
- Agreed operational contact model
Custom
Organisations that need custom packaging before a standard edition applies
Bespoke tenancy, deployment, and commercial structure.
Custom
Scoped with sales — no self-serve checkout.
- Custom environment and seat boundaries
- Deployment model scoped per engagement
- Integration and review timeline planning
- Commercial agreement — not published list price
Capability comparison
Capability groups across editions. Not an exhaustive feature matrix.
| Capability | Community | Professional | Enterprise | Custom |
|---|---|---|---|---|
| Business kernelsModular domain units applications can compose. | Single evaluation kernel | Production kernel capacity | Multi-kernel capacity | Scoped with sales |
| Workflow engineOrchestration definitions, instances, and failure paths. | Advisory | Enforced workflows | Multi-domain workflows | Custom policy |
| Decision automationPublished policies, results, and explanations. | Core decisions | Explanations included | Explanations included | Custom decision scope |
| Knowledge integrationVersioned knowledge artefacts bound to domains. | Basic knowledge reads | Domain-owned versioning | Multi-domain knowledge | Custom knowledge scope |
| Developer toolingSDK, diagnostics, and documentation access. | SDK + documentation | SDK + diagnostics | SDK + diagnostics | Scoped tooling needs |
| Deployment optionsWhere the tenant may run — discussed per edition. | Evaluation cloud | Cloud production | Cloud / private options | Cloud, private, on-prem, hybrid — scoped |
| SupportHow teams receive help — not contractual SLA tables. | Documentation paths | Named contact path | Agreed contact model | Agreed with sales |
Deployment models
Supported approaches discussed per engagement. Availability depends on edition and organisation policy — not every model is self-serve.
Deployment
Cloud
Hosted tenant for evaluation and many production engagements. Default path when private infrastructure is not required.
Deployment checklistDeployment
Private cloud
Dedicated cloud environment scoped with Enterprise or Custom packaging when isolation requirements demand it.
ContactDeployment
On-premises
Discussed under Custom packaging when organisational policy requires on-premises operation. Not a self-serve option.
ContactDeployment
Hybrid
Split placements for control-plane and workload components when scoped in an Enterprise or Custom engagement.
Architecture guideFrequently asked questions
Pricing questions. Contractual terms are not published here.
How do we evaluate Catoids?
Start with Documentation (Installation and Quick start), then follow the Implementation guide. Community packaging describes the evaluation shape. Contact us if you need a tenant arranged — this site does not run self-serve checkout.
Can we start with a pilot?
Yes. Professional packaging is the usual production-pilot shape for a single domain. Timing and commercial terms are agreed with the team for your organisation.
How does enterprise adoption work?
Enterprise and Custom packages support multi-domain rollout, security review, and non-standard deployment. Adoption is expected to be incremental — architecture and one domain first, then additional kernels.
When should we contact the team?
Contact us for tenant access, Professional or higher packaging, procurement or security review, or any Custom deployment discussion. Published amounts on this page are placeholders until commercial terms are finalized.
Are the listed prices final?
No. Amounts and edition names are structural placeholders. This website does not collect payment methods or run subscriptions.
Enterprise engagement
Contact the team when standard editions do not match procurement, security, multi-domain operations, or deployment requirements. Enterprise and Custom conversations clarify environment boundaries, review timelines, and commercial structure.
We do not publish generic SLAs or invent onboarding catalogues on this site. Services and commitments are agreed in writing for each engagement. Continue with Product, Documentation, and Resources while packaging is discussed.
Next steps
Continue into product and documentation, review resources and releases, or contact us about packaging.