If you’ve been running an MSP for more than a few years, you’ve probably felt the squeeze: a documentation platform you depend on gets acquired, pricing jumps at renewal, and the export tools that were supposed to protect you turn out to be incomplete CSV dumps. Switching costs for MSP tooling have been estimated in the hundreds of thousands of dollars once you factor in migration time, retraining, and lost productivity. For documentation platforms specifically, the lock-in is often worse than people expect — because the data isn’t just in the tool, it’s woven through every runbook, every client credential, every network diagram your team has built over years.
This is a practical look at where MSP documentation lock-in actually comes from, what it costs, and what a genuine exit looks like.
How Documentation Platforms Lock You In
Vendor lock-in in MSP documentation isn’t usually written into a contract clause. It accumulates quietly across four pressure points.
Proprietary data formats. Most SaaS documentation platforms store your data in ways that make clean exports difficult. You can often export articles as PDFs or flat HTML, but the relationships between assets, credentials, networks, and clients — the structure that makes the documentation actually useful — rarely survives the export. You get a pile of files, not a working knowledge base.
Per-seat pricing that scales against you. As your team grows, documentation costs grow with it. Platforms priced per technician mean that hiring creates a direct cost increase in your tooling budget. For small MSPs adding a technician or two, that can mean hundreds of dollars a month in new recurring SaaS costs just to keep documentation working.
Acquisition risk. The MSP software market has consolidated aggressively. When a platform gets acquired, pricing models change, roadmaps shift, and the tool you built your workflows around may become a different product entirely — or get deprecated in favour of the acquirer’s existing suite. Several major MSP documentation platforms have changed hands in recent years, and the pattern is consistent: pricing goes up, exit gets harder.
API and integration dependencies. If your RMM, PSA, or monitoring tools are tightly integrated with your documentation platform, switching one often means breaking others. Vendors design integrations to deepen lock-in, not to make migration easier.
What the Lock-In Actually Costs
The direct costs are visible: per-seat license fees, implementation costs when you switch, and training time. The indirect costs are usually larger. Documentation debt — the period where your old system is being wound down but isn’t gone, and your new system is live but not yet trusted — is a real productivity drag. Technicians work around incomplete documentation rather than from it, which is where onboarding slows down and client incidents increase.
There’s also the negotiating position problem. If your documentation is trapped in a proprietary format inside a platform you can’t easily leave, your leverage at renewal is close to zero. Vendors know this, and renewal pricing reflects it.
What a Real Exit Looks Like
The only reliable way out of documentation vendor lock-in is to own the data and the platform. That means self-hosted infrastructure, an open data store you can query directly, and software licensed in a way that can’t be revoked or changed by an acquisition.
For MSP IT documentation specifically, this means looking for:
- Self-hosted deployment so the data lives on infrastructure you control, not a vendor’s cloud
- Open data format — ideally a standard relational database (Postgres is the most portable) that you can query, back up, and migrate without vendor cooperation
- Open-source licensing so the software can’t be taken away, repriced arbitrarily, or discontinued when it gets acquired
- Integrated features rather than a documentation wiki that requires three other SaaS tools to cover credentials, assets, and network management — each adding their own lock-in surface
Weavestream is built around exactly these principles. It’s self-hosted, Postgres-backed, and licensed under AGPL-3.0. Your documentation, asset records, credential vault, IPAM data, SSL/domain monitoring, and client portal all live in a single Postgres database on your own infrastructure. You can take a pg_dump at any time and have a complete, portable copy of everything. There are no per-seat fees, no renewal negotiations, and no acquisition that can change what you paid for.
Avoiding Lock-In Going Forward
If you’re evaluating documentation platforms — or reconsidering your current one — the questions to ask are straightforward. Can you export your data in a format that’s actually usable, not just downloadable? Do you control the infrastructure it runs on? Does the licensing protect you if the company is sold or changes direction?
Self-hosted, open-source tooling doesn’t eliminate every risk, but it eliminates the specific risks that cost MSPs the most: arbitrary pricing changes, data hostage situations, and forced migrations on someone else’s timeline.
Getting Started
Weavestream runs in Docker and is designed to be up and running in under an hour. It covers IT documentation, asset management, a client credential vault, IPAM, SSL and domain monitoring, a client portal, role-based access control, and a security center — all in one self-hosted platform with no per-seat fees.
If you’re ready to own your data and cut the lock-in surface, start at weavestream.io.