When a government agency signs a contract with a technology vendor, it is making a bet. The bet is that the vendor will continue to serve the agency's interests for the duration of the contract — and beyond. If the vendor raises prices, degrades service, or changes direction, the agency needs to be able to walk away.
Vendor lock-in is the practice of making that walk-away expensive, difficult, or impossible. It takes many forms: proprietary data formats, cloud-only deployment, opaque APIs, contract terms that penalize migration, and features that only work within the vendor's ecosystem.
In the private sector, lock-in is a competitive strategy. In government, it is an accountability failure. Here's why.
The five costs of lock-in
1. You lose negotiating power
Once your data is in a proprietary format on a vendor's cloud, the cost of switching exceeds the cost of accepting a price increase. The vendor knows this. Year-over-year price escalation in locked-in government contracts averages 8-15%, compared to 2-4% for portable contracts with competitive alternatives.
2. You can't audit what you don't control
Government accountability depends on the ability to inspect, verify, and audit. When your data processing happens inside a vendor's black box — in their cloud, in their format, through their algorithms — you are trusting without verifying. That trust may be warranted today. It may not be warranted when the vendor is acquired, pivots strategy, or faces its own regulatory pressure.
3. Continuity of government requires continuity of data
Government outlasts every vendor. The records an agency creates today may need to be accessible in 20, 50, or 100 years. A proprietary format from a vendor that no longer exists is a digital dark age. Standard formats — JSON, CSV, SQL — are readable by any system, in any era, by any successor.
4. Cloud dependency is a security dependency
Every network connection is an attack surface. Every cloud dependency is a point of failure outside your control. For agencies handling sensitive, classified, or critical infrastructure data, the question is not “is the cloud secure?” but “who controls the security perimeter?” On-premise deployment means the answer is always “you.”
5. Public money demands public accountability
When a government agency cannot export its own data, it cannot fully respond to FOIA requests about its own processes. It cannot provide complete records to inspectors general. It cannot hand off to successor agencies cleanly during reorganizations. The data the taxpayer funded is trapped inside a private company's product.
What anti-lock-in looks like in practice
Anti-lock-in is not a feature. It is a set of engineering decisions that a vendor either makes or does not make. Here is how to evaluate whether a technology vendor is serious about portability:
| Criterion | Lock-in | Portable |
|---|---|---|
| Data format | Proprietary or undocumented | Standard JSON, CSV, SQL — documented schema |
| Export | Partial, lossy, or fee-gated | Full export, lossless, free, at any time |
| Deployment | Cloud-only | On-premise or agency cloud — your choice |
| Network | Requires internet / phones home | Air-gapped capable, zero outbound connections |
| APIs | Closed or version-locked | Standard JSON APIs, documented, stable |
| If you stop paying | Data inaccessible or deleted | You keep everything on your hardware |
These are not aspirational criteria. They are table stakes for any technology that handles government data. Any vendor that fails on more than one of these criteria is prioritizing their revenue model over your agency's autonomy.
The procurement question to ask
Before signing any government technology contract, ask one question: “If we stop paying you tomorrow, what happens to our data and our workflows?”
The right answer is: “Everything stays exactly where it is, in standard formats, on your hardware. You keep everything.”
Any other answer is a lock-in risk. Evaluate accordingly.
A note on incentives
Vendors that prioritize portability are betting on a different business model: that you will stay because the tools work, not because leaving is hard. This aligns vendor incentives with agency outcomes. If the tools stop providing value, the agency can leave. So the vendor is continuously motivated to provide value.
Lock-in reverses that incentive. Once switching costs are high enough, the vendor is motivated to raise prices and reduce investment in the product. The agency has no leverage. The taxpayer pays.
Choose vendors whose business model requires them to earn your renewal. That is the structural guarantee that their interests remain aligned with yours.