System DevOps
Docker · Kubernetes · Terraform
The machines the application runs on.
Airtable, Notion, Supabase, Retool, Vercel and their peers collapsed three kinds of DevOps into one browser tab and one person — and handed that person none of the tooling. The DOAP Alliance is the organisation for that person: training, certification, community, and a benchmark that did not exist.
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.
The Alliance is for the people responsible for DevOps on app platforms, and for everyone who pays them, builds for them or sells to them. Each has a door, and each door has published terms.
Practitioners, self-funded.
Member-only working sessions, regular networking touchpoints, webinars, the members-only forum channels (some channels are open to everyone), vendor discounts, the benchmark and the job board. Tiered by access and by the number of platforms you subscribe to; the entry tier is one platform.
Employers buying membership for their staff.
Seats in blocks; a company profile; the benchmark for your organisation.
The company behind a supported platform.
A non-voting observer seat on the platform council, early sight of the platform’s benchmark results, and a participating-platform badge. Not the exam, not the benchmark’s questions, not the membership roll, not a vote.
Agencies and consultants who deliver DevOps for app platforms as a service.
A directory listing, certified-staff badges, referral of member organisations looking for help.
Software and service vendors who serve these professionals.
Vendor membership and sponsorship tiers, and the ability to offer members a discount, under published rules for what vendors may and may not do. Never the membership roll.
We declare these four core tenets as our standard.
We advocate for structured workflows that separate development from live production data. Even when platforms lack native environment tools, DOAP professionals implement intentional staging, duplication, and verification processes before changes touch active business users.
AI is a force multiplier, but human judgment remains in the loop. We champion structured context engineering, auditable deployment trails, and rigorous review processes over raw generation speed.
Automated systems require automated oversight. We advocate for the implementation of centralized error logging, automated unit tests, and real-time alerts across all application platform pipelines.
As a Benefit Corporation, we break down these artificial barriers. By training and certifying builders in elite DOAP methodologies, we transform self-taught creators into highly sought-after Application Platform Engineers and DevOps Professionals capable of commanding enterprise-grade compensation.
Nobody has measured how teams protect, change and document what their business runs on. The first State of DOAP survey does, on any platform: you say which ones you answer for. One survey, two scores: yours the moment you finish, and your platform’s once everyone has answered.
Six scored practices, each 0 to 3, expressed out of 100. You get yours the moment you finish; the rubric is published with the report.
How strong you are as a practitioner. One number out of 100.
How well your platform supports the role. From everyone’s answers.
The same nine the survey measures today, so your DOAP Score is the first step. Platform-neutral at the core, platform-specific where it matters, and security and AI through all of them.
Using it to do the job, and managing it inside the platform
Access, secrets, audit, compliance, in every domain
Backup and restore
Code management, deploy, rollback
Schema monitoring, change visibility
Users, auth, access control
In the platform and across teams
Cleansing, hygiene, integrity
What connects, and how, securely
From the platform, to end users
Hands-on, and what it changes
The Alliance launches on interest. Every platform here is collecting it; a platform opens when its people join and a council is seated. It is never added because a vendor asked.
A curriculum across nine domains, platform-neutral at the core and platform-specific where it matters.
A credential for the practice — not for any one vendor’s product — written by the practitioners who do the work.
A place for the person who is “the Airtable person”, or the Notion person, or the Supabase person, and has never met another one.
A job board and a directory, and the paths between roles, so the career advances and the role gets a name, a market and a rate.
Nothing yet, and nothing is charged before 2027. The join form asks what you would expect to pay, and that sets the tiers. Individuals pay for themselves; organisations pay per seat; platforms, agencies and vendors pay per organisation.
No. The survey is for every platform: you say which ones you answer for, and each platform gets its own report. Forty-eight platforms are in scope, and each one moves forward when twenty people commit to it and a council of three is ready to seat.
Nobody who sells to you. It is being formed as a standalone benefit corporation, operated under contract by Openside, with Baseout as a founding partner on published, non-exclusive terms and BuiltOnAir as a community partner. None of them owns it, and the operating contract is disclosed.
A vendor certifies its product. DOAP certifies the practice: nine domains, platform-neutral at the core, written by the practitioners who do the work. No product names in the exam, and nobody who drafts exam content trains on it for pay.
You get your DOAP Score the moment you finish. Your answers go into the State of DOAP report in aggregate; the rubric is published with it, and no answer is shown against a name or a company.
Then that platform stays collecting interest, and you are not charged for it. The Alliance itself launches when three platforms reach twenty; if that never happens, the pledges stay pledges and nobody pays for an institution that did not form.
Yes. There is one inclusion test: you build and operate an application on it, rather than only run code there. Propose it, it goes under review, and it opens the same way as every other one.
After the Alliance forms, which is targeted for Summer 2027. The curriculum and the exam follow the nine domains the survey already measures, so the survey is the first step toward it.
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.