System DevOps
Docker · Kubernetes · Terraform
The machines the application runs on.
The brief
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.
Three kinds of DevOps existed before app platforms. This is what a platform does to each of them, and what it leaves behind.
Docker · Kubernetes · Terraform
The machines the application runs on.
Git · CI/CD · environments
The development and deployment lifecycle.
Postgres · MySQL · migration frameworks
The data.
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.
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.
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.
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.
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.
An automation stops running and nothing tells anyone until a customer does.
Revision history and the trash keep data for a window set by the plan, then it is gone.
A CSV keeps the rows; the interfaces, automations and permissions are not in it.
Attachment URLs and shared views that stop working on a schedule nobody set.
Renaming a field changes the schema and every view, formula and automation that used it, at once.
An AI assistant connected to production, editing the schema in natural language, with no branch and no review.
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.
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.
“Am I doing this right, and how exposed am I?”
Owns the platform at one company, often alone. Came for a mirror; the DOAP Score is the mirror.
“Is there a commercial relationship here, and am I early enough?”
Serves many clients across platforms. A credential is a trust mark to sell; the directory is where clients find them.
“Is this real research or a funnel?”
Brings real DevOps instincts and no platform knowledge. Checks who runs it and what they sell, in that order.
“What is the number for the board?”
Reads the report, never joins. One number, one comparison, one risk statement.
Nine domains carry the practice: the curriculum, the exam and the survey all follow them. The survey turns them into a number, the DOAP Score, 0 to 100 in four bands, and into a benchmark per platform.
We are asking before we build. Add your name and your platform: each one brings the Alliance closer to forming.
Gathering initial interest: your name on the join form, and the first survey open, for every platform.
The industry report, the rubric published with it, and the first benchmark.
Three platforms at twenty, councils seated, the benefit corporation filed.
The exam follows the nine domains the survey measures.