In mid-July 2026, Mayor Zohran Mamdani and the city's Office of Technology and Innovation announced the Public Interest Technology (PIT) Crew — five in-house teams of product managers, designers, engineers, user researchers, and data experts, embedded with city agencies to design, build, and launch digital products quickly. The phrase the city chose to describe the ambition was "months, not years" — moving from idea to implementation on a timescale New Yorkers can actually feel. The first crew is already pointed at something concrete: an online portal for the city's Click-to-Cancel rule, built with the Department of Consumer and Worker Protection. (nyc.gov announcement; StateScoop coverage.)
This is a good bet, and it is worth rooting for out loud. A city that decides to build its own software, in-house, on a schedule measured in months has correctly diagnosed where the pain is. What follows is written in support of that instinct — not as a pitch to the program, and not on its behalf. The platform described here, codenow.nyc, is not affiliated with the City of New York or the PIT Crew program. It is a free, independent civic instance, and the reason to write about it now is that it happens to be a live, touchable answer to the exact question the city just asked in public.
Because "months, not years" is a promise about a specific kind of speed, and it is worth being precise about what actually stands between a government team and that speed. It is almost never the coding.
IThe bottleneck is governance, not code — and the government already proved it
The slow part of shipping software inside a regulated organization is not writing it. It is getting permission to run it: the security review, the control assessment, the authorization paperwork that has to be satisfied before a single user touches the thing. In the federal government this step has a name — the Authority to Operate, or ATO — and for years it was the reason a finished system could sit unused for the better part of eighteen months.
The government's own reformers have already shown the bottleneck is removable. The GSA's cloud.gov platform lets an agency inherit its security controls instead of re-implementing them: roughly 155 of the 323 NIST Moderate-baseline controls are owned by the platform, with another 98 shared, so a team building on top of it starts most of the way to compliant. The published result is an authorization "in weeks, not months." And in 2025 the GSA went further, launching FedRAMP 20x with an explicit goal of "reducing authorization times from years to weeks" by automating the compliance evidence itself.
Read those two facts together and the shape of the problem is clear. When governed delivery is slow, it is slow because the governance was designed as a separate, manual workstream bolted on after the software is built. When someone makes the governance inheritable — a property of the platform rather than a tax on the team — the same work that used to take years takes weeks. The engineers were never the slow part.
IIThe bottleneck is removable at bank grade
The federal examples prove the pattern in government. The most striking proof that it scales to a hard-regulated, high-stakes environment comes from banking.
Komerční Banka is a major Czech bank and a member of the Société Générale international financial group — several hundred developers, monolithic legacy systems, and the full weight of financial-sector audit obligations. According to CodeNOW's published case study, the bank went from only four major release cycles a year to an agile organization capable of over four hundred independent monthly releases — while improving the security and quality of what it shipped. The same write-up reports a 70% reduction in DevOps costs and a 20% drop in overall delivery costs.
That is a regulated bank shipping at a cadence most people associate with a startup — four annual release cycles to over four hundred monthly releases — and doing it on rails that a bank's auditors signed off on. The platform underneath that transformation later became CodeNOW: a governed execution platform for software delivery, ISO/IEC 27001:2022 certified, that integrates more than forty open-source tools on Kubernetes and treats audit trails, separation of duties, and policy-at-execution-time as structural properties rather than afterthoughts.
CodeNOW states the thesis plainly on its own homepage — and it is the same diagnosis the government's reformers reached from the other direction:
"The slowest actor in modern delivery is no longer the engineer — it is the governance process that was designed around them."
That is the whole argument in one sentence. The speed a city wants and the control a regulator demands are not opposites. When the governance is built into the platform — inherited, automated, reproducible — the fast path and the compliant path are the same path. A bank found that out. A federal platform found that out. The question is where a New York City team can go to touch it.
IIIThe rails are already running in New York — free
Here is the part that makes this more than an argument. The same platform is running in New York today, for free, on a community-owned stack — and anyone can sign up and ship to it without a procurement cycle, a contract, or an approval.
It is called codenow.nyc: a free software-delivery platform for civic projects, running the full CodeNOW stack on four reclaimed servers connected to the internet over a volunteer-owned NYC Mesh wireless link. It is not a slide deck or a sandbox toy. It runs real production workloads — including meshdb, the member database that a working volunteer ISP depends on — behind the same identity plane, promotion gates, and secret governance a paying tenant gets. Its public status and deployment-metrics page publishes the receipts. (The full story of the hardware, the 1.9-mile radio link, and how it all fits together is in a companion essay, The Sightline.)
And the detail that ought to be underlined: this multi-tenant, bank-grade, ISO-27001-platform-backed environment is operated by one half-time administrator. That is not a caveat to apologize for — it is the demonstration. If a single part-time operator can stand up governed, auditable, production-grade delivery on donated hardware, then the reason a large organization can't ship in months was never a law of nature. It was the tooling. The whole point of putting the instance in front of people, free, is that the operational leverage is difficult to believe until you have your hands on it.
The on-ramp is deliberately short. A vibe coder, a nonprofit, or a volunteer developer plans a project, gets platform access, and deploys to the cluster — the four phases (plan, send developers, build and deploy, run in production) are product features, not staff labor. The planning phase is a product of its own — The Starting Line — and its output, a spec and a staffed team, is what the platform takes as input.
IVA prediction, and an invitation
A friendly prediction, offered in the spirit of rooting for the crews. Product #1 — a single portal, a single agency, a clean scope — is the honeymoon. The coding will go fine; the first launch will land in months, exactly as promised. The governance wall does not appear on the first product. It appears on the second product, and the second agency — when the same team has to ship across departments with different security reviews, different data classifications, and different sign-off chains, and the manual authorization work that was invisible at single-product scale suddenly becomes the whole job. That is the moment the federal reformers built control inheritance to survive, and it is the moment bank-grade governed-delivery rails are actually for.
None of this is a proposal to anyone. It is an open door. If you are a New York technologist — inside government on your own nights and weekends, at a nonprofit, or just a builder who wants to ship something civic on rails that would pass an audit — you do not have to wait for a seat on one of five crews, and you do not have to wait for anyone's procurement office. You can start a project on codenow.nyc today, for free, and see how far governed velocity goes when the governance is already in the platform.
New York just said, in public, that it wants to move in months, not years. The rails that make that promise keepable — the ones a regulated bank already runs on — are quietly running a few miles away, on four salvaged servers and a radio link, waiting for someone to sign up.
from one half-time operator who runs the free instance a few miles away.