THE CLIODOT PLATFORM
The operating system for integration infrastructure.
Build connectors and workflows.
Publish APIs and programmable capabilities.
Operate execution, access, environments and usage from one control plane.
Cliodot gives software teams the infrastructure required to connect systems without scattering integration logic across applications.
Explore the purpose-built Apps layerBUILDConnectors · Workflows
DEPLOYSurface · Gateway
OPERATERuns · Usage · Policy
BUILD. DEPLOY. OPERATE.
One lifecycle for connected software.
Cliodot organizes integration infrastructure around three responsibilities.
Build
Create the systems and logic your applications depend on.
Deploy
Make that logic available through APIs, SDKs, schedules, domains and other interfaces.
Operate
Control how the infrastructure runs across users, environments, organizations and deployments.
Each layer works independently.
Together, they form the complete platform.
BUILD
Create reusable integration infrastructure. Connectors
Define how external applications, databases and internal services are authenticated and operated.
Workflows
Compose connector actions, logic, conditions, transformations and custom execution into complete processes.
Arrikk AI
Use AI to scaffold connectors, understand schemas, create workflows and accelerate platform operations while preserving builder control.
Build visually where it improves speed.
Inspect and configure precisely where production requires it.
ORCHESTRATE BUSINESS LOGIC
Turn connected actions into production processes.
Cliodot workflows combine systems and logic into reusable execution paths.
A workflow can include:
Webhook triggers Connector actions Conditions Loops Transformations Validators Middleware Custom code Sub-workflows Response formatting Error handling
Workflows can power APIs, scheduled jobs, webhooks, Surface capabilities and internal operations.
DEPLOY
Make capabilities available where they are needed. Surface
Package connector actions, workflows and services into a programmable interface exposed through SDKs, REST, MCP, GraphQL and WebSockets.
Gateways
Publish managed API routes backed by workflows or selected connector operations.
Scheduler
Run workflows and operational tasks on defined schedules without maintaining separate cron infrastructure.
Custom Domains
Place published interfaces behind the domains your products and customers already trust.
Deployment is not the final step.
It is the beginning of the operational lifecycle.
TWO PUBLISHING MODELS
Choose the right boundary. Gateway
Use Gateway when the primary product is an API route.
Define the path, method, authentication and execution target.
Surface
Use Surface when the primary product is a collection of capabilities.
Attach actions and workflows, design a public contract and expose the same capabilities through multiple protocols.
Gateway publishes routes.
Surface publishes what your system can do.
OPERATE
Infrastructure requires more than execution. Usage Billing
Measure executions and apply usage policies across products, organizations and environments.
Connector Hub
Discover, install and distribute reusable connector definitions.
Enterprise License
Control the capabilities available to each deployment, organization or licensed environment.
Runs and Logs
Inspect executions, failures, inputs, outputs, timings and system behaviour.
Environments
Separate development, testing and production configuration without duplicating the platform.
Cliodot brings operational control into the same system where integrations are built.
PURPOSE-BUILT APPLICATIONS
More than a workflow builder.
Cliodot includes dedicated applications for different integration responsibilities.
OAuth Apps
Create authorization experiences using supported provider connectors and controlled scopes.
Authentication
Add verification and authentication capabilities such as OTP, TOTP, magic links, passkeys and challenge flows.
Webhook Apps
Receive, inspect, route and process incoming webhook traffic in real time.
Surface
Create a unified programmable capability layer for applications, developers and AI systems.
Remote
Request, approve and securely use capabilities exposed by another organization.
Each application uses the same underlying connector and execution infrastructure.
DISTRIBUTED INTEGRATION INFRASTRUCTURE
Use capabilities beyond one Cliodot environment.
Organizations can expose selected connector actions as remote capabilities.
Another organization can request access and explain why the capability is needed.
The publisher can then:
Review the request Modify the allowed actions Set an expiration Define quotas Configure rate limits Restrict environments Accept or decline access
Once approved, the remote capability can be used inside workflows, gateways or Surface while preserving the publisher’s attached permissions.
FLOWSYNC
A runtime designed for repeated execution.
FlowSync resolves and executes published integration logic across Cliodot.
The runtime is designed around:
Published workflow compilation Connector runtime bundles Deterministic cache keys Hot execution paths Environment-aware configuration Version-aware resolution Controlled invalidation MongoDB fallback Isolated custom code execution Usage and trace instrumentation
The objective is simple:
Keep production logic ready to run instead of rebuilding it on every request.
DEPLOYMENT CONTROL
Operate Cliodot around your organization.
Enterprise teams can use Cliodot across managed, private and hybrid environments.
Support may include:
Dedicated deployments Organization-specific licensing Private connector distribution Customer-owned credentials Custom domains Environment controls Usage policies Internal services Restricted remote capabilities Deployment-level feature access
Cliodot adapts to the operating model rather than forcing every organization into the same architecture.
ONE PLATFORM. MULTIPLE ROLES.
Built for the people who create and maintain connected systems.
Developers get typed interfaces, inspectable definitions and programmable infrastructure.
Product teams get reusable capabilities that can be delivered faster.
Platform teams get a consistent control plane.
Operators get execution visibility and environment control.
Organizations get an infrastructure layer that can grow with their products.
BUILD THE CONNECTED LAYER
Your applications should consume capabilities, not integration complexity.
Create the connectors, workflows and programmable interfaces that power your software.