First-ever The 2027 State of DOAP Survey is open. Take the survey

The brief

What is DevOps for App Platforms?

DevOps was three jobs. App platforms collapsed them into one browser tab and one person, and handed that person none of the tooling. DOAP is the practice that fills the gap, and the profession that does it.

How DevOps is built

Three pillars, with security and AI through all of them

Three kinds of DevOps existed before app platforms. This is what a platform does to each of them, and what it leaves behind.

Read the full brief →

System DevOps

Docker · Kubernetes · Terraform

The machines the application runs on.

Application DevOps

Git · CI/CD · environments

The development and deployment lifecycle.

Database DevOps

Postgres · MySQL · migration frameworks

The data.

SECURITY AI APP PLATFORMS Airtable Notion Coda Supabase Retool Glide monday.com Smartsheet
  1. Security AI Run through all three
  2. System DevOpsDocker · Kubernetes
    Application DevOpsGit · CI/CD
    Database DevOpsPostgres · MySQL
    Together: DevOps for app platforms
  3. App platforms AirtableNotionCodaSupabaseRetoolGlidemonday.comSmartsheet
  4. The DOAP Alliance
What changed

What a platform does to each pillar

Airtable, Notion, Supabase, Retool, Vercel and their peers absorb the first pillar, collapse much of the second and hide the third behind a UI. That is their value, and it is real: nobody provisions a server to ship an Airtable base. But the obligations did not go away; they changed shape.

  1. System DevOpsAbsorbed

    The servers, containers and scaling are the platform’s problem now. Uptime, regions and limits are set by a vendor you do not control, and read in a status page.

    What is left: knowing the platform’s limits, retention rules and outage behaviour before they bite.

  2. Application DevOpsCollapsed

    There is no repository, no branch, no review. A change to the interface or an automation is live the moment it is made, often with no record of who made it.

    What is left: staging, change visibility, release discipline, rollback, done with the platform’s own means or none.

  3. Database DevOpsHidden

    The schema is edited in the same click as the application. A migration is a field rename in production, with the data already in it.

    What is left: backup and restore, schema hygiene, integrity, and knowing what changed, when and by whom.

New ways to break

Failure modes none of the three pillars ever had

The platforms did not only remove the old tooling. They added ways to lose data and change production that have no precedent in any of the three columns, and no incumbent practice.

  • Silent automation failures

    An automation stops running and nothing tells anyone until a customer does.

  • Retention limits nobody read

    Revision history and the trash keep data for a window set by the plan, then it is gone.

  • Exports that skip the application

    A CSV keeps the rows; the interfaces, automations and permissions are not in it.

  • Links that expire

    Attachment URLs and shared views that stop working on a schedule nobody set.

  • One click, two changes

    Renaming a field changes the schema and every view, formula and automation that used it, at once.

  • Agents with write access

    An AI assistant connected to production, editing the schema in natural language, with no branch and no review.

The gap with no incumbent

The 2026 story is AI, and it is the clearest case that this is a new practice.

None of the three classical pillars has a practice for an autonomous, natural-language actor editing production schema in a system with no branch and no review. Neither do the platforms. The first State of DOAP survey already asks whether AI tools make changes to bases, whether assistants are connected through MCP or connectors, and whether the team can tell what changed. Crossing those three is the headline: the agents are already inside.

Who this is for

The practitioner is the unit, not the platform

The pains are platform-specific: Airtable’s retention rules are not Notion’s. The practice is not. Backup coverage, restore rehearsal, change visibility, staging, documentation and incident response are the same questions on every platform. A person who has moved between three platforms in six years has one career and three vendor badges. DOAP exists because the career is the durable thing, and nothing serves it.

The five member classes →

What DOAP is, and is not

DOAP isDOAP is not
The professional body for a discipline that has practitioners but no institution. Not a software product.
Neutral across platforms and across tool vendors, by charter rather than by promise. Not a vendor academy for any one platform.
The holder of the category’s standard, the DOAP Score, and its benchmark, the annual report. Not an agency or consultancy.
A benefit corporation: the mission is in the charter and reported against every year. Not a general DevOps body. DASA and DevOps Institute have that, and DOAP does not compete there.
Launching 2027

Join the Alliance.

We are asking before we build. Add your name and your platform: each one brings the Alliance closer to forming.

  1. Sep 2026 · now Founding members join

    Gathering initial interest: your name on the join form, and the first survey open, for every platform.

  2. Q1 2027 The report

    The industry report, the rubric published with it, and the first benchmark.

  3. Summer 2027 The Alliance forms

    Three platforms at twenty, councils seated, the benefit corporation filed.

  4. After Certification opens

    The exam follows the nine domains the survey measures.