Durable

Founded by James Clift (CEO); headquartered between Vancouver, Canada and San Francisco, California per third-party company profiles (Durable's own About page does not state HQ city). Legal entity name per Terms of Service.

Durable's own About page frames the company's founding story without a single explicit year, but third-party sources (BetaKit funding coverage, founder bio) place founding in September 2021, with the public product ramping through 2022. No Wikipedia article exists for Durable. Used 2021 as the incorporation/founding year rather than the later public-launch-momentum year some reviews cite as 2022.

AI-generated website plus bundled managed hosting; positioned by the vendor as a full 'AI business builder' (site + CRM + invoicing + bookings + marketing), not a traditional CMS.

Proprietary closed-source SaaS; no source-available or open-source licensing found anywhere in vendor materials.

No Wikipedia page exists for Durable; sourced from the official Terms of Service instead.

Inferred from Durable's own homepage industry examples and positioning ('the complete AI business builder'); explicitly not positioned for ecommerce or content-heavy publishing.

Legacy durable.co domain 301-redirects to durable.com.

Free plan lets you build and preview a site, but publishing to a live custom domain requires a paid plan; free sites run on a Durable subdomain with Durable branding.

Launch plan, billed annually (monthly equivalent); $25/month if billed monthly. Launch is the cheapest tier that includes a free custom domain and lets you actually publish. Official pricing FAQ: 'A Launch subscription starts at $22 per month.'

Grow plan, billed annually (monthly equivalent); marketed as unlocking unlimited team members, unlimited AI chat, daily blog posting, and 10x AI usage over Launch. Official pricing FAQ: 'A Grow subscription starts at $41 per month.'

Durable has no dedicated ecommerce plan or product-catalog/cart tier. Selling is done via individual product pages plus external Stripe Payment Links (see ecommerce.native); no separate ecommerce-specific price point exists to report.

Durable branding appears on the Free plan; removed starting at the Launch tier, which is also the first tier with a real custom domain.

Official pricing FAQ states the Launch plan is '$22/month (billed annually) or $25/month (billed monthly)'; monthly billing costs more than the annual-equivalent rate, consistent with a standard annual discount structure (about 15% per the toggle savings labels).

No money-back guarantee is documented in official sources. Durable's Terms of Service explicitly state fees are 'non-cancelable and non-refundable' and quantities cannot be decreased mid-term; some third-party review sites claim a '30-day money-back guarantee' but this directly contradicts the official ToS language and could not be corroborated on durable.com, so it is treated as unverified/likely inaccurate rather than reported as fact.

AI generates a full page/section layout from a business description; editing happens through a drag-and-drop interface for swapping images, adjusting headings/fonts, and reordering or regenerating sections, rather than a freeform pixel canvas or a rigid fixed-template system.

Vendor copy: 'use the intuitive drag-and-drop editor to control layouts, swap images, adjust headings, and customize fonts.'

Text can be edited inline directly on the page; an AI rewriting toolbar can also make selected copy longer, shorter, more casual, or more professional.

Durable only documents a single-step Undo (a toast notification with an 'Undo' button appears after an edit like a section deletion). No dedicated version-history panel or multi-step rollback feature is documented in the help center, unlike competitors with snapshot-based history.

Standard behavior for the web-based editor; changes are saved as you edit without a manual save step (implicit in the undo/toast-notification workflow and general product design).

Durable has no dedicated iOS or Android app; the site is built and edited entirely through the web-based editor, including on a mobile browser, but there is no native app for editing.

No official claim of a safe template-switch feature. Because each site is freshly AI-generated from a business description rather than picked from a swappable template gallery, changing the overall design/layout is not documented as a non-destructive operation.

Editorial judgment: the entire value proposition is speed and simplicity (answer 3 questions, get a full site in about 30 seconds), with a straightforward drag-and-drop editor layered on top; this is the lowest-friction entry point of any AI builder profiled, at the cost of design depth.

Durable does not publish a browsable template gallery or an official template count; the AI selects and customizes a layout per business rather than offering a numbered template library, so there is no comparable official figure to cite.

Vendor copy confirms font selection/customization from within the editor ('adjust headings, and customize fonts') but does not specify whether arbitrary custom font file upload is supported versus choosing from a preset palette of fonts; could not independently verify true file-upload custom fonts from official sources.

Vendor states all Durable sites are 'automatically responsive and optimized for mobile devices, tablets, and desktops' with no documented manual breakpoint editor.

Custom code (including CSS) can be added via a head/footer embed on the Add Custom Code feature; applies site-wide (not per-page). Plan-gating of this specific feature could not be independently confirmed from official sources.

Same custom code embed feature supports JavaScript (e.g., tracking/ad pixels, third-party widgets), applied to the site header/footer across all pages rather than per-page.

No native animation, interaction, or scroll-effect toolset is documented anywhere in official Durable marketing or help content; the product's design surface is limited to layout, image, color, and font adjustments.

Durable applies a consistent AI-selected color palette and font pairing across a generated site, but no official documentation describes a dedicated global design-tokens/style-guide panel distinct from per-section editing; unverified either way from official sources.

Editorial judgment: Durable optimizes hard for speed over control. Layouts are AI-generated and adjusted within a constrained section/drag-and-drop system with no freeform canvas, no native animation tools, and unconfirmed custom-font upload; site-wide (not per-page) custom code is the main escape hatch. This is the most constrained editing model among AI-generation-first builders in this comparison set.

Vendor: 'Durable includes free hosting with all plans.'

No self-hosting path exists; sites run exclusively on Durable's own infrastructure (Cloudflare-fronted). No reverse-proxy or bring-your-own-infrastructure option is documented, unlike some competitors that offer a proxy workaround.

Official pricing-page FAQ: 'All Durable domains are hosted on a content delivery network called Cloudflare. We chose Cloudflare because they offer fast and secure SSL generation, firewalls, and excellent protection from all web attacks including DDoS.'

Included as part of the Cloudflare-backed hosting described in the pricing FAQ ('fast and secure SSL generation').

No published uptime SLA or guaranteed percentage found in official Durable materials (no trust center or dedicated infrastructure/status page located).

No bandwidth or storage caps are published on the pricing page; plan limits are expressed instead as AI-usage quotas (images/month, AI chat messages/month, blog posts/month), not bandwidth/storage. Could not confirm whether a hidden bandwidth ceiling exists.

Multiple independent reviews and Durable's own domain-transfer FAQ (which offers only to hand over the custom domain name, not the site) corroborate that there is no HTML/code export; you cannot copy or export a Durable site's underlying code to self-host it elsewhere.

Durable is not tracked as a distinct technology in the HTTP Archive CWV Technology Report as of the latest available month; the API call https://cdn.httparchive.org/v1/cwv?technology=Durable&geo=ALL&rank=ALL returns an empty result set (no origins attributed to 'Durable'), consistent with it being a comparatively young/lower-adoption platform not yet crawled at sufficient volume for CrUX/HTTP Archive to report on. Durable's own help center instead cites internal Google Lighthouse audit scores (see performance.image_optimization note) rather than field CWV data.

Help center: 'Automatic Image Compression - all images are automatically compressed and optimized for web delivery without sacrificing visual quality.' Durable also cites internal Lighthouse audits showing sites 'typically achieve 90+ scores for categories like SEO, Accessibility, and Best Practices' (a vendor-reported lab metric, not independently verified field data).

Help center confirms images/media load only as they approach the viewport to reduce initial page load time.

Content delivery is handled automatically through the Cloudflare CDN with no documented site-owner-facing cache-control settings or configuration panel.

Per-page SEO title and meta description are editable via page settings; an 'AI generate SEO' action can also regenerate them automatically after content changes.

Durable's foundational-SEO help article covers meta tags, sitemap, robots.txt, structured data, OG tags, and noindex in detail but does not explicitly address whether page URL slugs are user-editable; could not independently confirm from official sources.

No official documentation describing forced URL patterns (e.g., blog post path structure, page nesting rules) was found.

No native redirect-management feature is documented anywhere in Durable's help center or SEO guide (the SEO & GEO collection and the dedicated SEO-features article cover meta tags, sitemap, robots.txt, canonical/OG, and noindex, but redirects are absent), and no third-party source references a redirects tool. Treated as a verified absence rather than an unknown.

Durable's own blog SEO guide page uses a canonical tag in its metadata (confirming the platform emits canonical tags on its own content), but the foundational-SEO help article does not explicitly describe self-referencing canonical tag behavior or owner-level canonical overrides for customer sites; unverified for end-user sites specifically.

Help center: robots.txt is generated automatically 'to guide search engine crawlers' with no dashboard configuration option offered to site owners.

sitemap.xml is auto-generated and auto-updated listing all public pages with last-modified timestamps; owners may submit it to Google Search Console but cannot manually configure its contents.

Help center: JSON-LD structured data is automatically generated from the business profile and page content on all published pages and is explicitly 'not directly editable in the dashboard'; fully automatic with no manual JSON-LD authoring path documented.

Durable has no native multi-locale site structure (see i18n.multilingual), so there is no native hreflang implementation; multilingual/hreflang support would depend entirely on a third-party translation widget layered on top (e.g., Weglot), which is out of platform scope.

Open Graph tags are generated automatically, with the OG social-share image customizable per page via page settings.

A per-page 'noIndex' toggle in page settings adds a noindex meta directive, and also excludes the page from both the XML sitemap and Durable's llms.txt file (Durable's own AI-crawler-facing file); a notably AI-search-aware implementation detail.

All uploaded images automatically receive AI-generated descriptive alt text; whether owners can manually override/edit the AI-written alt text per image was not explicitly confirmed in official docs, but automatic generation itself is documented.

Native AI Blog Builder lets owners create long-form posts with AI-generated text and images; part of the core product, not a third-party plugin.

Durable's content model is limited to pages and blog posts; no documented ability to define custom content types/collections (e.g., a portfolio or events collection) beyond the built-in page and blog structures, unlike CMS-style competitors with a generic collections/CMS layer.

Blog posts can be organized into categories within the native blog builder; tagging beyond basic categories is not documented as available.

No native 'publish at a future date/time' scheduling for blog posts is documented; Durable's own SEO & GEO / blog materials describe on-demand AI generation and manual publishing, not a scheduling queue.

Same single-step Undo mechanism covers all editing (design and blog content); no dedicated content revision log or rollback-to-a-prior-version feature is documented for blog posts or pages specifically.

Additional team members/users can be added to a Durable workspace (unlimited on Grow, per the pricing FAQ), with a documented 'view-only for website, team, and settings' contributor role that can still manage contacts, invoices, bookings, and the blog; i.e., a real (if basic) multi-role authoring setup rather than single-user only.

No official documentation confirms or denies native RSS feed generation for the blog; not covered in the SEO & GEO collection or the blog SEO guide.

No public content/CMS API is documented anywhere in Durable's help center or developer-facing materials; the platform exposes no way to programmatically read or write site/blog content.

Durable's own blog post on the topic confirms there is no native store: 'you can use Durable to create an e-commerce website... All you need to do is generate a website and add a link from Stripe.' There is no product catalog, cart, or checkout inside Durable itself; individual product pages plus a 'List' section block can approximate a shop front, but every purchase button redirects off-platform to a Stripe-hosted payment page. Official pricing FAQ corroborates: 'Durable is not designed specifically to support e-commerce businesses.'

No native product catalog exists, so there is no Durable-defined product limit; any practical limit would come from how many individual product pages/Stripe Payment Links an owner manually creates, not a platform-enforced cap.

No native digital product delivery mechanism (e.g., automatic file/license delivery post-purchase); a Stripe Payment Link can technically be used to charge for a digital product, but there is no built-in fulfillment.

Recurring billing is possible only by configuring a recurring Stripe Payment Link externally; nothing native inside Durable manages subscriptions or recurring product billing (Durable's own native recurring-billing feature is its Invoicing tool, which is service/client-billing oriented rather than a product-subscription commerce feature).

No native multi-currency selling capability documented; since there is no native cart/checkout, currency handling would be whatever Stripe's Payment Link is configured for, not a Durable platform feature.

No point-of-sale capability documented anywhere in official Durable materials.

No cart concept exists on the platform at all (see ecommerce.native), so there is nothing to recover; abandoned-cart flows are structurally impossible without a native cart.

No documented content export feature (no CSV/JSON export of blog posts, CRM contacts, or page content) and no content API exists to pull data out programmatically; Terms of Service describe only a 7-day account-restoration window after a deletion request, not an export mechanism.

Multiple corroborating sources (third-party reviews plus the absence of any export feature in official docs) confirm you cannot copy or export a Durable site's code; the site exists only on Durable's infrastructure and cannot be taken elsewhere.

Custom domains registered/connected through Durable can be transferred out. Official pricing FAQ: 'When cancelling your account, simply get in touch with us and we'll arrange to have your custom domain transferred to you. Note that it takes a couple of weeks to transfer over and has a minimum subscription time.'

The built website itself cannot run anywhere except Durable's own Cloudflare-fronted infrastructure; there is no self-hosting, static export, or reverse-proxy path documented (see hosting.self_host_option and hosting.static_export).

No public content API exists (see content.content_api), so there is no programmatic path to full content access, automated or otherwise.

Editorial judgment: no code export, no static export, no content API, no documented data-export feature, and Terms of Service granting Durable broad rights to use Customer Data plus explicit non-refundable/non-cancelable billing terms. The only portable asset is the custom domain name itself. This is among the highest lock-in profiles in the comparison set, comparable to or worse than other hosted-builder platforms with no export path.

No public developer API is documented anywhere on durable.com or help.durable.com; this is consistent with the platform's no-code, non-extensible positioning.

No native webhook feature (e.g., for form submissions or CRM events) is documented in official Durable materials.

Custom HTML/CSS/JS can be embedded via a head/footer code panel; applies site-wide across all pages rather than per-page, and plan-gating could not be independently confirmed.

Durable is a fully no-code, closed proprietary platform; there is no developer framework, local dev environment, or codebase to work against, so this attribute does not meaningfully apply. Left null rather than 'none' since the schema expects a text description of a framework/stack, and none exists to describe.

No CLI, SDK, or developer tooling of any kind is documented; entirely a point-and-click, no-code product.

No official Zapier or Make app/integration listing found for Durable, and no native webhook mechanism exists that would allow an unofficial bridge either; multiple third-party reviews specifically flag Durable's lack of an integration ecosystem as a weakness.

Core product mechanic: answer three questions (business type, name, location) and Durable's AI generates a complete, industry-specific, mobile-responsive website in roughly 30 seconds, including copy, images, contact form, and SEO-ready structure.

AI copywriter generates initial site/section copy and an in-editor AI rewriting toolbar can lengthen, shorten, or change the tone (more casual/more professional) of existing text on demand.

Dedicated 'Studio' AI image tool (a full help-center collection of its own) generates on-brand marketing images, logos, and ad visuals; usage is metered by plan (5 to 500 images/month across Free/Launch/Grow).

An 'AI generate SEO' action can regenerate a page's title/meta description after content changes; separately, Durable's SEO & GEO suite includes an AI Visibility Score, AI Visibility Rankings (tracking presence in ChatGPT, Gemini, Claude, Perplexity, Grok), competitor analysis, and curated directory-submission recommendations, going meaningfully beyond basic on-page SEO assistance into generative-engine-optimization territory.

At least two role levels are documented: full editor/owner access, and a restricted contributor role described in the pricing page's usage-limit copy as able to 'manage contacts, invoices, bookings, and your blog. View-only for the website, team, and settings.' This is real but coarse-grained role separation, not the fully granular permission systems seen on larger platforms.

No official documentation confirms or denies real-time simultaneous multi-user editing of the same site/page; team members can be added and given access, but simultaneous live-collaboration behavior (e.g., multiplayer cursors) is not described anywhere in official materials.

No editorial approval/review workflow (e.g., draft-then-approve publishing) is documented; edits appear to publish directly, consistent with the single-step-undo model rather than a staged review process.

The Free plan explicitly frames 'build and preview' as the free-tier capability with publishing gated behind a paid plan, but this is a one-time pre-launch preview state rather than an ongoing staging environment for an already-live site; no dedicated staging/preview-environment feature for live sites is documented.

No in-editor commenting/annotation feature is documented anywhere in official Durable materials or the Website Editor help collection.

No official documentation of a customer-facing activity/audit log was found; unverified either way.

No published support-hours commitment or 24/7 claim found in official materials; unverified.

Editorial judgment: the Help Center is well-organized into 12 clear collections (Account, Website Editor, SEO & GEO, Bookings, Agents, Studio, Payments, Customers, Invoicing, Durable Essentials, Pro Tips, and a Legacy Editor archive) with substantive individual articles (e.g., the foundational SEO article is genuinely thorough on meta tags/sitemap/robots/structured data/OG/noindex). Falls short of 'excellent' because it's noticeably thinner than mature platforms in some areas (e.g., no clear documentation on slug editing, canonical control specifics, or concurrent editing), consistent with Durable being a comparatively young product.

No official or reliably-sized community forum, Discord, or subreddit metric was found for Durable during research; unverified.

No SOC 2, ISO 27001, or other security certification is published anywhere in official Durable materials (no dedicated trust/security center found), and searches for one turned up nothing Durable-specific. Left null rather than asserting 'none' since absence of a public claim is not fully conclusive proof of no certification, but no evidence of one exists.

No documented backup/restore feature for site content was found; the only restore-adjacent mechanism in official materials is the 7-day account-restoration window after an account deletion request (Terms of Service), which is an account-recovery safeguard, not a content backup/versioning system.

No dedicated accessibility-checking tooling (contrast checker, alt-text audit panel, ARIA controls) is documented beyond the automatic AI-generated image alt text noted under seo.image_alt_editable; no official accessibility guide comparable to competitors' dedicated accessibility help articles was found.

Durable has no native multi-locale site structure or in-product translation workflow; the editor interface and generated sites are English-only from the platform itself. Multilingual sites are achievable only by layering a third-party translation widget (e.g., Weglot, Commoninja Translator) on top, which is explicitly a workaround rather than a Durable feature.

No native translation management workflow exists; would require a third-party widget entirely outside Durable's own product surface.

No native hreflang or per-locale URL structure exists (see seo.hreflang and i18n.multilingual); this would be entirely dependent on a third-party translation integration.

No official documentation confirms or denies RTL layout support; given the absence of any native localization system, this is unverified from official sources within research scope.