CLIODOT PRICING
Pricing that grows with the infrastructure you operate.
Start with the tools required to build integrations.
Expand as you publish capabilities, add environments, increase execution volume and operate Cliodot across more products and teams.
Cliodot pricing combines platform access with the infrastructure your applications consume.You pay for the capabilities, execution volume and operating model your organization requires, not for disconnected tools assembled around the same integration problem.
PLANPlatform availability
USAGEMeasured execution
OPERATIONSEnvironment scale
Confirmed with CliodotHOW PRICING WORKS
One platform. Clear dimensions.
Cliodot pricing is structured around four areas.
Platform access
The connectors, workflows, applications and deployment tools available to your organization.
Runtime usage
The workflow executions, connector actions, API requests, scheduled runs and capability invocations processed through Cliodot.
Operational scale
Projects, environments, collaborators, logs, retention, limits and governance requirements.
Deployment model
Managed Cliodot infrastructure, dedicated environments, hybrid operation or enterprise deployment.
PLANS
Choose the operating model that fits your product.
Exact prices, execution allowances and feature limits are confirmed with Cliodot. No unresolved commercial placeholders are published here.
Developer
For individual builders exploring Cliodot.
Build connectors, create workflows and understand how Cliodot fits into your product architecture.
Includes 9 items
- Development workspace
- Connector builder
- Workflow builder
- Community and public connectors
- Limited monthly executions
- Development logs
- Basic API access
- Arrikk AI assistance
- Community support
Builder
For teams shipping connected product features.
Move from experimentation into production with reusable connectors, workflows and application capabilities.
Includes 14 items
- Everything in Developer
- Production environments
- Private connectors
- Increased runtime usage
- Workflow publishing
- Scheduler
- Webhook Apps
- OAuth Apps
- Auth Apps
- Surface capabilities
- SDK and REST exposure
- Team collaboration
- Extended execution logs
- Email support
Scale
For products operating integration infrastructure across customers and applications.
Manage higher execution volume, multiple projects and advanced capability delivery from one control plane.
Includes 13 items
- Everything in Builder
- Multiple production projects
- Higher execution allowances
- Advanced Surface exposure
- MCP, GraphQL and WebSocket capabilities
- Remote capabilities
- Custom domains
- Usage controls
- Quotas and rate limits
- Advanced logs and observability
- Longer retention
- Priority support
- Higher collaboration limits
Enterprise
For organizations requiring deployment, governance and commercial flexibility.
Operate Cliodot according to your infrastructure, security and organizational requirements.
May include 14 items
- Dedicated or private deployment
- Hybrid infrastructure
- Enterprise licensing
- Customer-controlled credential models
- Custom execution limits
- Private Connector Hub
- Organization-specific capabilities
- Custom domains
- Advanced permission controls
- Extended logs and retention
- Deployment assistance
- Architecture support
- Dedicated support arrangements
- Custom commercial terms
RUNTIME USAGE
Pay for infrastructure when it runs.
Cliodot may meter activity across several execution types. The selected plan defines which activities are included and how additional usage is calculated.
Workflow executionflow/customer-sync
Capability invocationbilling.customers.create
Webhook processinggithub/events
Remote executionpartner/reports.read
TRANSPARENT METERING
Understand how usage is measured.
An execution represents a unit of work processed by Cliodot.
A workflow triggered once may count as one workflow execution.
Connector actions performed inside that workflow may be measured separately when the applicable plan uses action-level metering.
A Surface request may count as one capability invocation regardless of whether it is called through an SDK, REST, MCP or another exposure.
The final billing definition should remain consistent across every interface.
Workflow triggeredOne workflow execution
DEVELOPMENT AND TESTING
Separate experimentation from customer-facing infrastructure.
Development environments allow teams to build and test connectors, workflows and applications before publishing them to production.
- Development execution allowances
- Production execution allowances
- Environment limits
- Log retention
- Team access
- Publishing permissions
EXPAND WHEN REQUIRED
Configure Cliodot around your operating model.
Depending on the selected plan, additional capacity may be available. Add-ons remain optional and transparent.
COMPARE PLANS
A clear view of platform availability.
The comparison uses only approved plan inclusions. Contact us marks features whose exact availability has not been commercially finalized.
Build6 features
Deploy9 features
Apps4 features
Operate8 features
Enterprise6 features
FREQUENTLY ASKED QUESTIONS
Commercial details without hidden assumptions.
Can I start without a paid plan?+
The Developer plan is intended to let builders explore Cliodot, create connectors and understand the platform before moving production infrastructure onto a paid plan.
What happens when I exceed my included usage?+
Depending on the plan, additional usage may be billed automatically, restricted until the next billing cycle or require a usage upgrade. The applicable behaviour should be shown clearly before production usage begins.
Is Surface priced separately?+
Surface is part of the Cliodot platform. Availability, exposure types and usage limits may differ by plan.
Are connector installations billed individually?+
Connector definitions and installations are different resources. The final commercial model should state whether limits apply to private connectors, installations, executions or a combination of them.
Can Cliodot run in our infrastructure?+
Dedicated, private and hybrid deployment options may be available through an enterprise agreement.
Do development executions count toward production usage?+
Development and production allowances should be reported separately where supported by the selected plan.
Can we negotiate custom usage limits?+
Organizations with high execution volume, private deployment requirements or unusual workloads can contact Cliodot for a custom agreement.
START WITH THE PLATFORM
Build first. Scale when your infrastructure does.
Create your first connector, workflow or Cliodot App and move into production when your product is ready.