Enterprise securityInternationalReviewed June 2026

Is Bubble.io ISO 27001 compliant?

Bubble is not ISO 27001 certified. The ISO certificate AWS holds sits at the cloud-infrastructure layer and does not transfer to Bubble or to your app. Bubble lists ISO 27001 only "for information purposes" in its Other Frameworks page. For EU and UK enterprise sales — where ISO is often preferred over SOC 2 — you certify your own information-security management system. ISMS-level certification on Bubble is partial-viable; many teams pair SOC 2 with ISO once international deals demand it.

The honest verdict

Not officially. Not the way you’d ship ISO 27001 in production.

Bubble has no public stance. The platform's architecture makes a real audit hard. That's the entire Bubble position on ISO 27001 — a one-line description on the Other Frameworks page. Bubble itself is not certified. AWS holds an ISO 27001 certificate as Bubble's infrastructure provider, but a sub-processor's certificate does not propagate to Bubble's ISMS, and it does not propagate to yours. Treat ISO as a standard you implement at your own organisation level.

International standard for information security management systems
— Source:Bubble.io documentation

Reviewed by

Greg· Founder, bubbletocode.com — has migrated 30+ Bubble apps to code

Independently sourced — no Bubble partnershipLast reviewed June 2026
Credentials
  • 01 / 04

    Bubble's stance

    Silent — not certified

    Listed "for information purposes" only

  • 02 / 04

    Procurement consequence

    EU/UK enterprise gate

    Non-accredited certs routinely rejected

  • 03 / 04

    Industries impacted

    B2B SaaS · Cloud · Finance · Telecom · Manufacturing

  • 04 / 04

    Compliant on Bubble

    $15k–$60k · 12–52 weeks

    ISMS-level certification with platform inheritance

What ISO 27001 actually requires

The requirements behind the checkbox.

ISO/IEC 27001:2022 is the international standard for an information-security management system (ISMS). Accredited certification bodies under ISO/IEC 17021-1 audit and certify organisations. There are no statutory penalties. The 2013-to-2022 transition deadline passed on Oct 31, 2025 — every 2013 certificate is now expired.

  • 01

    Establish the ISMS scope and context, including internal and external issues plus interested-party requirements that bound what you're certifying (ISO/IEC 27001:2022 Clause 4).

  • 02

    Secure leadership commitment with a written information-security policy and clearly defined roles and responsibilities, including a top-management mandate (Clause 5).

  • 03

    Conduct a documented information-security risk assessment and risk treatment plan, producing a Statement of Applicability that maps the 93 Annex A controls to your risks (Clause 6).

  • 04

    Provide resources, competence, awareness, and documented information across the team — training records, evidence of competence, controlled documentation (Clause 7).

  • 05

    Operate the ISMS day-to-day and implement the applicable Annex A controls from the 93-control catalogue, 11 of which are new in the 2022 edition (Clause 8 / Annex A).

  • 06

    Monitor, measure, perform internal audits, run management review, and drive continual improvement with corrective action tracked to closure (Clauses 9–10).

Official source: iso.org

Why Bubble fails ISO 27001

Not opinions — architectural facts.

Every reason below comes from Bubble’s published platform limits or their own documentation. Reading the list top-to-bottom tells you which one will bite you first.

  1. 01

    Bubble itself is not ISO 27001 certified

    Blocker

    Bubble holds no ISO 27001 certificate covering its own ISMS. AWS's certificate covers the AWS infrastructure layer, not Bubble's company, processes, or platform. Customers who treat "my app runs on AWS" as ISO inheritance fail vendor-risk reviews in the EU and UK every time. Accredited certification bodies require the certificate be issued to the organisation operating the ISMS — that's you, not your platform.

    Sources[02][01]

  2. 02

    Listed for information only — no commitment

    Major

    Bubble's Other Frameworks page mentions ISO 27001 as a description of what the standard is. There is no statement of compliance, no certificate number, no scope statement, no certification body named. Auditors and procurement teams reading the page see exactly what's there: an information-only listing. Compare with the explicit SOC 2 Type II page where Bubble names the auditor (Sensiba LLP) and the report.

    Sources[01]

  3. 03

    Two-week log retention undercuts ISMS monitoring controls

    Major

    Annex A monitoring controls expect managed log retention, search, and review windows much longer than 14 days. Bubble's logs interface limits search to the previous two weeks. For Annex A control 8.15 (logging) and 8.16 (monitoring activities) you'll need to design and evidence an external log-aggregation pipeline — that's a control your auditor will scrutinise, not something Bubble provides.

    Sources[03]

  4. 04

    Shared multi-tenant cluster limits asset and environment control

    Minor

    The default Bubble environment is a shared US-AWS cluster. ISO Annex A controls 5.9 (inventory of information and other associated assets) and 8.1 (user endpoint devices) expect a documented, controlled environment. You can certify your organisation around an inherited shared platform, but you cannot certify the platform itself, and auditors will note the dependency in your Statement of Applicability.

    Sources[02]

  5. 05

    No customer control over keys or storage

    Minor

    Annex A controls 8.24 (cryptography) and 8.10 (information deletion) expect an organisation to manage its own keys and storage lifecycle. Bubble encrypts at rest with AES-256 on AWS RDS, but the customer has no visibility into key rotation, key management ownership, or per-customer encryption envelopes. That's not a blocker for ISMS certification — but it is a control you must document as inherited.

    Sources[02]

Bubble vs a compliant stack

Where each requirement passes or breaks.

The same 7requirements an auditor will ask about, scored on both stacks. Read across each row — every red cell is a deal you can’t close on Bubble.

Requirement
On Bubble.io
On a compliant rebuild
  • Organisation-level ISO 27001 certificate

    Fail

    Not certified

    Listed for information only on Other Frameworks page

    Pass

    Vercel Enterprise + AWS hold ISO 27001

  • Statement of Applicability evidence

    Partial

    Document Bubble as inherited platform

    Works for organisational ISMS; auditors note dependency

    Pass

    Self-managed control mapping per Annex A

  • Annex A monitoring + logging (8.15 / 8.16)

    Partial

    Two-week search — ship logs off-platform

    Pass

    Postgres event log + S3 archive + SIEM

  • Annex A 8.24 cryptography — key control

    Partial

    Platform-managed AES-256, no key visibility

    Pass

    KMS-backed envelope encryption, per-record

  • Asset inventory and environment control (Clause 8 / 5.9)

    Partial

    Shared multi-tenant US cluster

    Pass

    Dedicated infra + tagged assets + IaC

  • EU / UK data residency at platform level

    Partial

    Only via Enterprise dedicated AWS region

    Pass

    Region-pinned Vercel / AWS / Azure

  • Accredited certification body recognised by EU buyers

    Fail

    Bubble has no certificate to inherit

    Pass

    UKAS / ANAB accredited certificate available

What it costs your business

The deals you lose
without ISO 27001.

International enterprise procurement — particularly in the EU and UK — increasingly demands an ISO 27001 certificate from an accredited certification body (UKAS, ANAB, or equivalent). Non-accredited certifications are routinely rejected at vendor-risk review. SOC 2 is the US trust currency; ISO is the international one. Selling globally usually means both.

  • An EU enterprise prospect runs a vendor-risk review and asks for your ISO 27001 certificate before contract — without one, the deal sits unresolved while procurement asks for compensating evidence.

  • A UK financial-services buyer requires UKAS-accredited certification specifically; a low-cost non-accredited certificate gets returned and you start over with an accredited body.

  • A renewal request from a long-standing customer references the Oct 31, 2025 transition deadline — your 2013-era cert (or that of your sub-processor) is now expired and triggers a vendor-risk re-review.

  • Tender RFPs in EU public-sector and large private supply-chains pre-screen on ISO 27001 — without the certificate, you don't make the shortlist regardless of price or fit.

Three honest paths forward

Stay, hybrid, or rebuild — pick the one true to your stage.

We don’t recommend a rebuild for every founder. Below: what each path costs you, what it preserves, and where it breaks for ISO 27001.

01

Cheapest now · riskiest later

Partial fit

Certify your ISMS on Bubble — partial-viable

ISO 27001 certifies an organisation's ISMS, not a product. You can scope your ISMS around your team, processes, and the Bubble-hosted product with inherited platform controls documented in your Statement of Applicability. Add SOC 2 first, then layer ISO on the same control set.

Pros

  • No migration — preserve the Bubble build
  • 70% control overlap with SOC 2 lets you reuse evidence
  • Stage 1 + 2 audit ~$14–16k for SMB ISMS

Cons

  • Auditors note the platform dependency in your SoA
  • Annex A logging and monitoring controls need external log aggregation
  • Surveillance audits annually — control discipline is not a one-off
Read the hybrid trade-offs
02

Phased · auditor-defensible

Partial fit

Hybrid — rarely the right answer for ISO alone

Carve specific data flows off Bubble only if a customer demands strict EU residency or a tighter control set than Bubble's shared cluster supports. ISO certifies an organisation, so a hybrid setup is more about residency than about the certification mechanic itself.

Pros

  • Useful if you need EU data residency now
  • Lets you tighten Annex A 8.x technical controls outside Bubble

Cons

  • Two environments inside one ISMS scope — paperwork doubles
  • Migration risk against a standard you can pass on Bubble
Score with the hybrid planner
Recommended
03

Highest upfront · clean audit

Viable

Full rebuild — only when international residency or scale forces it

Rebuild on Next.js with Vercel Enterprise or AWS as the host. Vercel Enterprise holds ISO/IEC 27001 and SOC 2; AWS holds ISO 27001 across all regions. Customer keys, dedicated infrastructure, region-pinned data — all become evidence-friendly under your direct control.

Pros

  • Single ISMS scope, single environment, easier audit narrative
  • Direct control over Annex A 8.x technical controls
  • Unlocks EU/UK data residency at the host level

Cons

  • Highest up-front cost
  • Hard to justify on ISO alone — usually paired with HIPAA or FedRAMP
Start the free rebuild analysis

Composite case study

What an honest ISO 27001 migration looks like in practice.

Mid-market SaaS expanding into the EU · 14 months on Bubble

B2B SaaS founder closed a German enterprise pilot whose procurement team asked for an accredited ISO 27001 certificate before production rollout. We scoped the ISMS around the founder's team and the existing Bubble app, documented Bubble as a sub-service organisation in the Statement of Applicability, set up log shipping off Bubble for the monitoring controls, and engaged a UKAS-accredited certification body. Stage 1 documentation review at month two, Stage 2 audit at month four, certificate issued at month five.

Outcome: Certificate issued at month five with one minor non-conformity remediated in two weeks; the German deal closed inside 60 days of certificate delivery, and two additional EU conversations that had been pre-screened out re-opened.

Composite case study assembled from patterns we've seen across ISO 27001 readiness engagements with B2B SaaS teams running on Bubble. Anonymised for client privacy — happy to walk you through the actual engagements in a scoping call.

Frequently asked

What founders ask about ISO 27001 on Bubble.

Pulled from real conversations with founders running healthcare, fintech, and B2B SaaS apps off Bubble. Every answer is grounded in the source we cited above — no marketing fluff.

Q01Has Bubble ever been ISO 27001 certified?
No. Bubble lists ISO 27001 in their Other Frameworks page as a description of the standard, with no certificate, no certification body, no scope. AWS — Bubble's infrastructure provider — is ISO 27001 certified at the cloud-infrastructure layer, but that certificate covers AWS's ISMS, not Bubble's. The certificate does not transfer.
Q02Will SOC 2 satisfy an EU buyer asking for ISO 27001?
Sometimes — but doing a SOC 2 audit does not give you an ISO 27001 certificate. There's roughly 70% control overlap between SOC 2 and ISO 27001:2022 Annex A, so the evidence reuses, but they're different artefacts: SOC 2 is a CPA attestation over a window (typically 3–12 months), ISO 27001 is an accredited certification of a continuously operating ISMS. US buyers usually accept SOC 2 alone; EU and UK enterprise buyers increasingly insist on the ISO certificate itself. Many SaaS hold both for exactly that reason.
Q03Can I certify my organisation while staying on Bubble?
Yes. ISO 27001 certifies an organisation's ISMS, not a product. You scope your ISMS around your team and processes, document Bubble as an inherited platform in your Statement of Applicability, and certify against the 93 Annex A controls. You'll need to ship logs off Bubble for monitoring controls — that's the main operational change.
Q04How long does ISO 27001 actually take?
Fast-track engagements complete Stage 1 and Stage 2 audits in 3–6 months; typical first-time certification runs 12+ months. After certification, surveillance audits happen annually and recertification every three years. If you already hold a current SOC 2, you can reuse most of the control evidence and shave the readiness phase materially.
Q05My 2013-era certificate — is it still valid?
No. The transition deadline from ISO/IEC 27001:2013 to the 2022 edition was October 31, 2025. After that date all 2013-version certificates expired and the 2022 edition with its 93 Annex A controls (11 new) became mandatory. If you or a sub-processor are showing a 2013 cert in 2026, treat that as expired and ask for the 2022-equivalent.
Q06Does Bubble sign anything that helps my ISO audit?
Bubble signs a GDPR-compliant DPA with Standard Contractual Clauses and the EU-US Data Privacy Framework. That DPA is what you reference in your ISO scope as the contract with your platform provider. Bubble does not sign BAAs. For ISO purposes the DPA is the relevant artifact; for HIPAA it's not enough.
Q07Should I use an accredited certification body?
Yes. EU and UK enterprise procurement frequently rejects non-accredited certificates outright. Look for bodies accredited under ISO/IEC 17021-1 by UKAS in the UK, ANAB in the US, or your national accreditation body. The cost difference between accredited and non-accredited audits is small — the rejection cost downstream is not.

Sources

Every claim, traced to a primary source.

The numbered references in the body link here. We cite first-party documents — regulator guidance, vendor manuals, industry standards — never marketing copy.

  1. [01]
  2. [02]
  3. [03]
    Logs tab — server log retention and search window

    Bubble Group Inc.manual.bubble.io

  4. [04]
    ISO/IEC 27001:2022 — Information security management systems — Requirements

    International Organization for Standardizationiso.org

  5. [05]
    ISO/IEC 17021-1 — accreditation requirements for certification bodies

    International Organization for Standardizationiso.org

  6. [06]
  7. [07]

Want a real answer for your app, not your category?

Drop your .bubble export. We’ll tell you what ISO 27001 costs to actually achieve.

Free. 10 minutes. No call. Reads every workflow, surfaces every PII / WU / scaling risk, and produces a fixed-price rebuild plan grounded in ISO 27001’s real requirements.