The Best Free & Open-Source IT Glue Alternative | Weavestream

If you’re searching for a free alternative to IT Glue, you already know what you’re up against: per-seat pricing that compounds as your team grows, a Kaseya acquisition that reshuffled the roadmap and the billing, and a documentation platform that has become someone else’s leverage over your operation.

You need something that covers the same ground — structured asset tracking, credential vault, client documentation, domain monitoring — without the monthly bill or the vendor dependency. That’s exactly what Weavestream is built to be.

Why people leave IT Glue

IT Glue earned its position. A decade of MSP feedback built a mature data model, deep PSA integrations, and a feature set that’s genuinely hard to leave behind. That’s not the issue.

The issue is the ownership structure. Since the Kaseya acquisition in 2018, IT Glue pricing has moved — and MSPs who built their business on a predictable per-seat cost have found themselves repriced, re-tiered, or pushed toward bundle commitments that reach across the entire Kaseya stack. The July 2021 Kaseya VSA ransomware attack, one of the largest supply-chain attacks ever recorded, was a stark reminder of what vendor concentration risk looks like when it materialises.

Beyond cost and vendor risk, there’s the structural problem that applies to any vendor-hosted documentation platform: your data lives in their cloud, your uptime depends on their SLA, your migration path runs through their export API, and your security model is whatever they’ve decided it should be.

For MSPs with compliance obligations in healthcare, legal, or financial sectors, that last point is increasingly a real problem. For anyone who’s watched pricing shift once already, it’s a question of when it happens again, not if.

What a free, self-hosted alternative actually looks like

Weavestream is an open-source IT documentation platform licensed under AGPL-3.0. It covers the full IT Glue surface — assets, credentials, knowledge base articles, domain and SSL monitoring, client portals, IPAM — running entirely on infrastructure you control.

Three Docker containers. One compose.yml. Your Postgres database. Nothing calling home.

curl -O https://raw.githubusercontent.com/Weavestream/Weavestream/main/compose.yml
curl -O https://raw.githubusercontent.com/Weavestream/Weavestream/main/.env.example
mv .env.example .env
curl https://raw.githubusercontent.com/Weavestream/Weavestream/main/scripts/keygen.sh | bash >> .env
docker compose up -d

That’s the full install. Your data lives in host-mounted directories. Back it up with pg_dump and rsync. Restore it anywhere Postgres runs. No export API, no support ticket, no waiting.

“Free software” still requires infrastructure — a small VPS or an on-prem server running Docker is all you need. What it doesn’t require is a vendor license, a per-seat fee, or permission from anyone.

Feature comparison: IT Glue vs Weavestream

The honest read: IT Glue’s integration depth is a real advantage at scale in a full PSA-driven shop. If ConnectWise or Autotask sync is load-bearing for your daily workflow, that gap matters today. On data ownership, security posture, operational control, and cost — Weavestream has no competition in this comparison.

Why open source and self-hosted matters for IT documentation specifically

Most software categories can tolerate vendor dependency. Your documentation platform is not most software. It holds every password, every network credential, every client infrastructure detail your team depends on to do anything.

That data living in a vendor’s cloud means:

• Their breach is your breach. A compromise of the vendor’s environment exposes your entire client base. You have no remediation path except waiting for them to fix it.
• Their outage is your outage. A client emergency at 2am doesn’t pause for a vendor’s status page.
• Their roadmap is your roadmap. Features you need — or security controls you want — happen when they decide, not when you need them.

Self-hosting with Weavestream reverses all of this. You define the security model: custom TLS, network isolation, forced MFA, your own backup cadence, your own retention policy. You audit the code. You control the encryption key. You own the database.

Migrating from IT Glue to Weavestream

The biggest reason MSPs stay on IT Glue despite the billing pain isn’t loyalty — it’s fear of migration. Years of structured asset data, linked passwords, and client documentation feel impossible to move.

The reality is more manageable than it looks:

What moves cleanly: Client records, asset data, knowledge base articles, and credentials all map directly to Weavestream’s data model. CSV exports from IT Glue cover the bulk of structured data. Weavestream’s import tooling handles flat CSV files for clients, assets, and credentials.

What requires judgment: Flexible Asset relationships and cross-linked articles don’t export with their link graph intact — no platform migration does. Plan to rebuild relationship mappings on a client-by-client basis as you review each record. This is actually an opportunity: most MSPs discover their IT Glue data has drifted and needs a cleanup pass anyway.

Recommended approach: Run Weavestream in parallel for 30–60 days. Stand it up on a VPS, migrate one or two clients as a test, and validate your workflow before cutting over the full book.

The data is yours — it lives in a Postgres schema you can inspect, query, and transform directly. No export API limitations, no ticket to file.

Who should stay on IT Glue

• You’re deeply embedded in the Kaseya stack and ConnectWise or Autotask sync is non-negotiable.
• Checklists and structured runbook templates are daily-use features for your team.
• You have no interest in running infrastructure and the per-seat cost is not a concern.

Those are real reasons. IT Glue is a mature product. The question is whether you’re comfortable with your entire documentation stack being owned by a vendor whose incentives don’t necessarily align with yours.

Who should choose Weavestream

• You’re an MSP, internal IT team, or homelab operator who can run a Docker stack.
• You’ve watched IT Glue pricing shift and don’t want to be there when it shifts again.
• You have clients in regulated industries where vendor-hosted credentials are a compliance concern.
• You want to audit the code, fork it, or extend it.
• You want your documentation accessible regardless of what any vendor decides to do.

Security model

Weavestream’s security defaults are intentionally stricter than most platforms in this category. MFA is platform-enforced — there’s no per-user opt-out. Credentials are encrypted with AES-256-GCM using a key stored in your own environment. The audit log is append-only and protected at the database-role level, so even a compromised application layer cannot retroactively alter records. HaveIBeenPwned breach detection runs on every saved credential.

Full details are in the security documentation and encryption spec.

Get started

Deploy in under ten minutes: Quickstart guide.

The source, issue tracker, and release notes live at github.com/Weavestream/Weavestream. If a feature gap is keeping you on IT Glue, open an issue — the roadmap is public and driven by what operators actually need.

Your documentation stack shouldn’t be someone else’s leverage. Weavestream puts it back where it belongs.