Durable
Durable is an enterprise AI platform that turns a described business problem into a deployed automation, writing real production code rather than agent chains. It connects 44 SaaS systems and repairs itself when APIs change. Access is by demo only.
What is Durable?
Durable is an enterprise automation platform built by Durable, Inc., a Louisville, Colorado company working on neurosymbolic AI. Its premise is stated bluntly on the product page: most AI platforms wire agents together, Durable writes software.
That distinction drives the whole design. The company argues that code is deterministic, does the same thing every run, costs little to execute and holds no surprises, while agents are powerful but expensive, slow and unpredictable. Agents are therefore demoted from architecture to tool call: they sit inside otherwise ordinary code and are invoked only where genuine intelligence is required, such as classifying a document or interpreting an edge case.
The cycle has four stages. First, a conversation: you describe what is wrong in plain English and Durable asks clarifying questions. Second, what the company calls the Solution Architect connects to your APIs, databases and SaaS tools, discovers what is actually there, including schemas, custom objects and API quirks, and returns structured requirements to review rather than a workflow you hope works. Third, those requirements become the source of truth. They are numbered, versioned and written in plain English, so anyone on the team can read one, click it and describe a change; the code regenerates to match. Fourth, deployment is a single click, followed by a real-time activity feed and a workflow monitor. When a third-party API changes or a run fails, Durable repairs it automatically and submits the amended specification for approval.
The published integration library covers 44 named systems across eight categories, each with its own page: Salesforce, HubSpot, Zendesk, ServiceNow, Jira, GitHub, GitLab, the Google Workspace suite, QuickBooks, Xero, Stripe, Slack, Twilio, Datadog and more. The site claims it can connect to any system with an API, however obscure.
For enterprise buyers, Durable advertises SOC2 Type II and Google CASA Tier 2, SSO/SAML, role-based access control, audit logging, data residency options, dedicated infrastructure and a 99.9% uptime SLA. Integration data runs on isolated containers, and only monitoring data reaches Durable's servers, encrypted at rest. The product is a web application, and the only way in is to book a demo.
What it does
- Investigate the systems you already run, including schemas, custom objects and API quirks, before writing any code
- Turn a problem described in one sentence into structured, reviewable requirements
- Write deterministic production code, calling AI agents only where judgment is genuinely needed
- Deploy an automation to production in one click, with no developer in the loop
- Connect 44 documented SaaS systems, and in principle any system exposing an API
- Detect and repair failures automatically, then submit the amended specification for approval
- Monitor every run in real time and keep a full version history of the automation
When to use Durable / When not to
A quick filter to help you decide if Durable is the right fit.
When to use Durable
- Enterprise operations teams running repetitive cross-SaaS processes such as CRM-to-warehouse syncs, invoice processing, lead routing or onboarding
- IT and platform teams buried under internal automation requests they have no headcount to build
- Data teams maintaining brittle pipelines between systems like Salesforce and a warehouse
- Non-developer business analysts who need to change automation logic themselves, in plain English, without filing a ticket
- Companies with enterprise security requirements: SSO/SAML, role-based access control, audit logging and data residency options
When not to use Durable
- Individuals and very small businesses: the positioning is strictly enterprise, with no self-serve signup and no published price
- Anyone who wants to try the product today without first talking to a salesperson
- Teams that need to drive the platform from their own code, since no public API documentation is published
- Buyers who require a written GDPR framework, a DPA or a subprocessor list before they can sign
- Anyone looking for an AI website builder, which is durable.co, an entirely different company
How to use Durable
A typical end-to-end flow, from setup to results.
- Book a demo, which is the only entry point: there is no self-serve signup
- Describe the problem you want solved, in plain English, in Durable Chat
- Answer the clarifying questions the tool asks back
- Let Durable connect to your systems and discover schemas, custom objects and API behaviour
- Review the generated requirements, numbered R1.1, R1.2, R2.1 and grouped by block
- Request a change by clicking any requirement and describing the modification in plain English
- Approve the specification and deploy to production in one click
- Follow execution in the real-time activity feed and the workflow monitor
- Approve the specification updates Durable proposes when a third-party API changes
- Sign in to app.durable.ai for day-to-day use, and request any missing integration on the request page
Pros & Cons
Pros
- Produces version-controlled, testable production code instead of an opaque agent chain, a real argument on both cost and determinism at runtime
- The specification stays readable and editable by non-developers, which removes the ticket-and-sprint loop
- An upfront investigation phase: the tool inspects the systems you already run before proposing anything
- Automatic maintenance when a third-party API changes, with human approval required for each update
- Forty-four integrations documented one by one, each with its own page, so the scope is verifiable rather than merely asserted
- A detailed enterprise security story: isolated containers, end-to-end encrypted credentials, SSO/SAML, RBAC and audit logging
- Unusual transparency about the team, with five people named alongside their backgrounds, two academic advisors and a physical office
Cons
- No published price, no trial and no self-serve signup: everything goes through a sales demo
- No terms of service at all, leaving the privacy policy as the only contractual document on the site
- The Trust Center linked from every page footer does not resolve, so the SOC2 Type II and Google CASA Tier 2 badges cannot be verified anywhere
- No mention of the GDPR, no DPA, no subprocessor list and no Article 27 representative
- No public API documentation, no mobile application and no openly accessible demo
- No postal address and no contact form: the only contact points are two email addresses masked behind a Cloudflare token
- No named customer, no case study and no screenshot of a real deployment, since every product visual on the site is a mockup
Pricing & Plans
No pricing is published on any page of the site, and no pricing page exists. The only pricing reference is an FAQ heading asking how pricing works for enterprise customers, and its answer is not present in the page source. There is no announced free plan and no announced free trial. Obtaining a figure requires booking a demo.
Data, GDPR & hosting
A consolidated view of how Durable handles your data.
GDPR overview
There is no mention of the GDPR anywhere on this site. Across the seven pages collected, in both rendered text and raw HTML, the words GDPR, General Data Protection Regulation and CCPA do not appear once. No Article 27 representative is designated, no data protection officer is named, no legal basis for processing is cited, no Data Processing Agreement is offered and no subprocessor list is published. Data subject rights appear only in generic, conditional terms, and the policy directs readers to contact details at the end of the document that are not there. Durable states it is based in the United States and that data may be processed there or in other countries where its servers are located, without naming a transfer mechanism. Data residency is listed as an enterprise option with no region named.
Who owns the data?
No terms of service are published, so ownership can only be read from the privacy policy dated 27 May 2025. Customer specifications are collected into a document Durable calls a Blueprint. Generated apps run in isolated environments, and data flowing through them is not permanently stored. Integration credentials are end-to-end encrypted, never stored unencrypted, and only the customer can access or change them. Durable may share information with cloud hosting and analytics providers under contract, and may transfer it in a merger or sale of assets. Nothing published states who owns the generated code itself.
Reuse rights
Account information can be viewed and updated from account settings. The policy acknowledges access, correction and deletion rights depending on the user's location, but names no procedure and no address for exercising them: section 8.4 points to contact details at the end of the document that the document does not contain. For Google data specifically, the customer may revoke OAuth access, disconnect the integration, request deletion, and export data where technically feasible. Because no terms of service exist, nothing defines what the customer may do with the automations and the code Durable produces on their behalf, or whether that output can be reused freely elsewhere.
Data retention & training
Hosting summary
Durable states it is based in the United States and that information from users outside the country may be transferred to, stored and processed in the United States or in other countries where its servers are located. That reservation is never resolved: no hosting provider is named, no cloud region is named, and the policy refers only to cloud hosting providers in the plural without listing them. Data residency appears among the enterprise security features with no region attached to it. What the company does describe is the execution model rather than the geography. Integration data runs on isolated containers, and the only data reaching Durable's own servers is monitoring data, encrypted at rest. Communication between an application and Durable's systems is limited to app controls and health checks, with everything else end-to-end encrypted. The domain itself sits behind an anycast address, which says nothing about where the application is actually hosted. A buyer with a jurisdictional requirement will have to obtain the answer during the sales conversation.
Things to keep in mind
Risks and trade-offs to weigh before adopting Durable.
- Name collision, first of all: durable.ai is Durable, Inc., an enterprise automation company in Colorado, and is unrelated to durable.co and durable.com, the AI website builder. Prices, affiliate offers and reviews found online under the name Durable almost always describe the other company
- The Trust Center linked from every page footer and from the homepage security block does not resolve, as the subdomain has no DNS record, so the SOC2 Type II and Google CASA Tier 2 claims cannot be checked anywhere on the open web
- No terms of service exist, which means nothing contractually settles who owns the generated code, what happens to your automations if you leave, or what the advertised 99.9% uptime commitment actually guarantees
- The GDPR is never mentioned, and there is no DPA, no subprocessor list and no Article 27 representative, which is a real obstacle for a European buyer and a striking gap given how precise the same policy is about Google's requirements
- The privacy policy tells you to use contact details at the end of the document to exercise your rights, but the document has no such section, so a deletion request means falling back on a footer email address
- Durable rules out training on Google user data only, and publishes nothing about the Blueprints you write or the data moving through the other integrations, so treat this as an open question until you have it in writing
- Parts of the live site are unfinished, with the homepage use-cases block rendering an empty-category message and the six FAQ answers absent from the page source. Combined with the absence of any named customer or case study, nothing public demonstrates the product running in a real deployment
Setup & Integrations
Technical difficulty
Low for the user, on paper: you describe the need in plain English, review the requirements and click deploy. The real prerequisite is authority, since you must be able to authenticate the systems being connected by granting OAuth access or API keys. Enterprise options such as SSO/SAML and role-based access control need configuring upfront on your side. The main friction is commercial rather than technical, as there is no self-installation, only a demo. And with no public documentation, no getting-started guide and no accessible help centre, the true learning curve cannot be assessed before contact.
Deployment
Integrations
Supported languages
Behind Durable
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
How much does Durable cost?
Can I try it without talking to a salesperson?
Do I need to know how to code?
Which systems can it connect to?
What happens when a third-party API changes?
Is there a Durable API I can call from my own systems?
Is the tool GDPR compliant?
Is my data used to train AI models?
Where is data hosted and how long is it kept?
Who is behind Durable and how do I reach them?
Should you pick Durable?
Durable makes an argument the rest of the category mostly avoids: that the answer to enterprise automation is deterministic code with AI called sparingly inside it, not an agent orchestrating everything. Whether or not that thesis convinces you, it is coherent, it is argued in detail, and it shapes a product that looks different from its neighbours. Requirements you can read, code you can version, failures the platform repairs and then asks you to approve.
The company behind it is legible in a way many AI startups are not. Durable, Inc. names five staff with their doctorates and prior work, two academic advisors, a Colorado office and an open role. The integration library describes 44 systems one at a time, each with a page. The privacy policy runs to twelve sections and carries a date.
What is missing is everything a buyer needs to close. There is no price, no trial and no self-serve entry, only a demo booking. There are no terms of service, so nothing contractually defines who owns the generated code or what service level is being sold. The Trust Center linked in every footer does not resolve, which leaves the SOC2 Type II and Google CASA Tier 2 badges unverifiable on the open web. The GDPR is never mentioned. No customer is named and no case study is published, and every product visual is a mockup.
The honest reading: a technically serious young company that has not yet built the commercial surface around its product. If cross-system automation is a real cost centre for you, the demo is probably worth the hour, but go in with a list. Pricing, contract terms, the compliance evidence behind those badges, a reference customer, and a written answer on whether your specifications and integration data are used to train anything.
- Choosing a selection results in a full page refresh.
- Opens in a new window.