System DevOps
Containers · Servers · Databases
The machines the application runs on.
DevOps is complicated. App platforms collapsed it 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.
Systems, applications, databases, security and AI each grew their own DevOps practice. App platforms fold much of that into one product, which is why people use them. The work didn’t go away: someone still has to manage changes, backups, access and the AI agents writing to production — just done in different, yet to be defined ways. That is where the Alliance steps in.
Containers · Servers · Databases
The machines the application runs on.
Git · CI/CD · environments
The development and deployment lifecycle.
Migrations · Backups · Rollbacks
The data.
Airtable, Notion, Supabase, Retool, Vercel and the rest take over the servers, fold the code into the product and hide the database behind a UI. That is why people use them: nobody provisions a server to ship an app with them. But DevOps didn’t go away. It just 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 behavior 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.
Platforms removed some of the old problems and brought new ones: new ways to lose data or end up with mismatched versions, and no agreed way yet to prevent them.
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 classic pillars has a practice for an AI agent that edits a production schema in plain language, in a system with no branch and no review. Neither do the platforms. The first State of DOAP survey asks whether AI tools make changes to your data/schema, whether assistants are connected through MCP or connectors, and whether you can tell what changed.
Most platform admins work without a shared standard, and without anyone else who does the same job. The Alliance is being formed around their needs first, with the agencies, employers, vendors and platforms around them.
“Am I doing this right, and how exposed am I?”
Owns the platform at one company, often alone. Looking for support and fellow platform owners.
“How can we scale our expertise across our client base?”
Serves several clients across platforms. Looking for a shared standard to work to, and a credential clients recognize.
“Where are my environments, code repos, databases?”
Brings real DevOps knowledge but lacks platform understanding. Looking for how to work within the limits of a platform.
“How do I know my team is running this properly?”
Joins as an organization, and wants the whole team certified.
Training covers nine domains, with security and AI running through all of them. The DOAP Score measures platforms and practitioners on the same ground.
Woven into all domains
Oversight of Privacy and Security is essential in all domains.
The Alliance forms platform by platform, when twenty people register for each. Add your name, and your platform gets one closer.
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, steering committees seated, the benefit corporation filed.
The exam follows the nine domains the survey measures.