Cyclr

Cyclr is an embedded integration platform, an iPaaS built mainly for software companies that want to offer integrations inside their own product. The company's headline reads "One platform for embedded integration, AI interoperability and data governance," and it describes itself as "the infrastructure layer that lets SaaS companies connect systems, surface their product in AI safely and scale customer integrations." The reader it is written for is a product or engineering team at a B2B SaaS company, a service company delivering integrations for clients, or an enterprise standardizing how integrations are delivered. The company behind it is Cyclr Systems Ltd, and the contact block on the home page gives an address in Croydon, UK, with phone lines for the UK and the US. The promise is to deliver "customer-facing integrations, secure AI connectivity and enterprise-grade control without building and maintaining the infrastructure yourself."

What you build and how

The home page groups Cyclr into 5 areas: Headless ("API, MCP, data access, governance and headless delivery"), Embedded iPaaS, MCP & AI, Governance and Services. The core capabilities menu shows what you actually build with.

Workflows and templates. "Low-Code Orchestration" is described as "Build workflows, templates and automations visually." A customer quote on the page says the team can "simply use its visual builder to drag and drop, link, and map methods, eliminating the need for bespoke integration frameworks." The template idea is central: "Build a workflow once, deploy many times across multi-tenanted accounts." That is the difference from a general automation tool, because the unit you design is a reusable integration that many of your customers each switch on for their own accounts.

Connectors. Cyclr lists "600+ Connectors" for "SaaS apps, databases, APIs and infrastructure." Each application connector "handle[s] authorisation, paging, API rate-limits & ETL Data transformation." The popular list names Salesforce, Microsoft Dynamics, NetSuite, Sage 200, HubSpot, Shopify, Amazon S3 and Claude, and the library is browsable by category, with accounting, CRM and email marketing named. Where a system has no connector, a Connector Creation Toolkit lets you "create connectors for proprietary, niche or long-tail systems," and "API Connectors" turn APIs into reusable visual components.

Delivery to your users. An "Embedded Marketplace" lets "users select, authenticate and install integrations inside your app." "Integration Delivery" offers "a wide rage of options to trigger & deploy integration workflows," a "CLI Integration Delivery" option lets your users automate integrations by command line, and "API Access" lets you "automate platform and account-level operations." "Data on Demand" calls third-party data "through a unified, governed layer." There is also a Branded Embedded iPaaS, described as "white-labelled integration delivery for multi-brand or partner-led models," and a service-based variant that deploys and manages integrations for many customer accounts.

Multi-tenancy and management. Multi-Tenancy is described as managing "customers, accounts and integrations in ring-fenced environments." Integration Management provides "a wide range of tools to monitor and govern the performance of your integrations." The headless pitch adds that the multi-tenant account model controls "authentication, permissions, usage, transactions and customer-specific access," so each customer only reaches what you have scoped for it.

AI and agents. This is where the platform has moved most recently. AI Interoperability connects "your services to LLMs and AIs," MCP PaaS will "turn your API and integration capabilities into governed MCP servers," and "MCP-triggered Workflows" are "token & data efficient workflows that can be called by AI." AI Orchestration is meant to "orchestrate AI, application and customer data with governed workflows." The pitch is that multi-tenancy acts as a "gatekeeper for using AI at scale," and an AI Agent Workflows use case promises control over "how agents access apps, APIs and customer data."

Where it runs. "Private Deployments" put Cyclr "in infrastructure aligned to your enterprise requirements," and "On-Prem Integrations" connect "proprietary, local or legacy systems into modern workflows." The page also mentions that "Private Cloud migration" is available as you scale. The console has sign-in links for four regions, US, US2, UK and EU. The compliance section adds an invitation to "speak to us about our ability to deploy into your own hosted environment."

The page also names who it is built for: B2B SaaS companies, service companies, AI companies, enterprise organizations, eCommerce brands and system integrators, with team pages for product managers, CTOs and engineering leaders, SaaS developers, API teams and integration teams. A use case called Native In-App Integrations promises to "deliver integrations without sending users to a third-party automation platform," which is the clearest statement of the product's purpose. The headless section takes the same idea further: customers should reach your platform's integrations, workflows and data "through the interfaces they already use," from the product UI, APIs and customer portals to AI chatbots and agentic tools, and approved workflows become "governed tools that can be used by AI agents, chatbots and automation layers."

Cyclr does not build front-end apps or websites. What your customers experience is the integration inside your product, and Cyclr stays behind it.

Pricing, claims and customers

Pricing: the home page lists no prices, plan names or usage limits; it says the plans and infrastructure are "built for scale," with private cloud migration available. It offers "Book Demo" and "Get a Free Trial" buttons, and the closing banner reads "Start building for free," though the length and scope of the trial are not given.

Compliance: "Cyclr is SOC2 Type II accredited and GDPR compliant." The page says the company regularly undertakes external and internal assessments, and a Security & Compliance Review page is linked. It mentions "end-to-end encryption and compliance certifications" without naming others.

Connector count: 600+, repeated as "Over 600 SaaS Connectors & universal connectivity tools."

Customers: quotes come from Neural Voice (a lead software engineer), Simplesat (head of customer success), Force24 (a director of operations), Younium (a co-founder and head of product), Monica Vinader (head of product and data) and Leadoo (a founder and head of product). Younium's comment shows the logic of the product: "A lot of the systems we need to integrate with are niche and so specific, local ERP systems for instance. It would mean I'd need 10 people to maintain these." Simplesat's Elliot Fox says "Cyclr gives us the ability to never say no," and Force24 says it can "integrate with a considerably higher number of different systems with a much lower overhead." Monica Vinader's first use case was an abandonment flow. These are testimonials chosen by the vendor.

Support: the product has user and API documentation, connector guides covering authentication and setup, and a blog whose recent posts deal with embedded MCP integrations and agentic workflows. A Services area offers "integration and solution experts" to accelerate implementation. Neural Voice's quote praises "the level of support and speed of responses," and Force24 says the support "is really what sold Cyclr to us."

Who it suits and who it does not

Cyclr suits a B2B SaaS team whose customers keep asking for integrations to different systems, and which would rather not staff an integration backlog. It also fits a consultancy or system integrator that wants to deliver the same integration repeatedly for many clients from one place, and an AI company that needs governed access to customer apps and data. The multi-tenant, template-based design is built for exactly that repetition.

It is a weaker fit for an operations team that wants to automate its own internal apps, or a founder who wants a quick flow between two tools. The page frames everything around delivering integrations to other people's accounts. A second caveat is cost visibility: with no prices on the home page, you need a demo or the trial before you can budget.