# The Hidden Costs of Municipal Software Subscriptions How cloud-based services create long-term dependencies for local governments. - **Source:** [O'Reilly Radar](https://www.oreilly.com/radar) - **Published:** 2026-09-24 - **Original article:** - **On Brifing:** https://brifing.si/s/0a2eebcc-1a26-4e21-ac5e-1c12671adb93 ## From author to mayor Dan Gookin, original author of DOS For Dummies and now mayor of Coeur d'Alene, Idaho, highlights an unexpected challenge in municipal governance: software subscriptions. His city spends $700,000 annually on cloud-based services, including financial software they no longer own. This shift from ownership to subscription models raises fundamental questions about data control and long-term costs for public institutions. ## The $700,000 question Coeur d'Alene's annual software subscription costs equal the salary of multiple full-time developers. Mayor Gookin questions whether building in-house solutions might offer better long-term value and control. However, recreating complex municipal systems like financial software, records management, and public safety applications presents significant technical and security challenges that may outweigh potential savings. ## Data ownership concerns Key issue isn't legal ownership but practical control: Can the city retrieve all its data if switching vendors? Current systems provide no guarantee of clean data export formats. This creates risk if vendors are hacked, raise prices, or discontinue services. The problem mirrors Gookin's personal experience replacing $800/year Adobe subscriptions with Linux alternatives. ## Reversibility as metric Cloud contracts include 'reversibility' clauses for data retrieval, but municipalities rarely evaluate this during procurement. Gookin suggests treating exit costs as a core evaluation criterion alongside features and price. Without planning for transitions, cities risk accumulating technical debt that makes vendor switching prohibitively expensive or technically impossible. ## The maintenance paradox While subscription models eliminate some maintenance burdens, they create new dependencies. In-house development brings its own long-term costs for updates, security patches, and staff retention. The build-vs-buy analysis remains complex, especially when proprietary systems become deeply embedded in municipal operations over years of use. ## Organizational capability erosion Extended SaaS use can atrophy internal technical skills, leaving organizations unable to perform basic functions without vendors. This dependency becomes critical when systems are so specialized that only the original vendor can maintain them. The risk grows as more municipal services move to cloud platforms with proprietary formats. ## Cloud's undeniable value Subscription models provide smaller cities access to enterprise-grade systems they couldn't otherwise afford. The solution isn't abandoning cloud services but consciously choosing dependencies rather than acquiring them by default. This requires understanding data location, retrieval processes, and replacement costs before signing contracts. ## A coming reckoning As subscription costs consume larger budget shares, more organizations will question the true price of convenience. The personal computing revolution began with hobbyists; Gookin predicts similar grassroots experimentation with alternatives before large-scale adoption. The fundamental question remains: Which capabilities justify ownership despite higher costs? ## Sources covering this story - https://www.oreilly.com/radar/when-software-subscriptions-become-public-policy/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._