The Best IT Glue Alternative Is the One You Own

If you're searching for an IT Glue alternative, you're probably already frustrated. Maybe it's the pricing that landed after the Kaseya acquisition. Maybe it's the creeping sense that your documentation stack — the thing your entire operation depends on — is controlled by a company whose priorities don't align with yours. Maybe you've just done the per-seat math and felt it.

Whatever brought you here, you've found the same landscape: comparison sites pushing other SaaS tools, and nobody writing it from the perspective of the open-source, self-hosted option. That's this article.

What IT Glue does well

IT Glue has been the MSP documentation standard for over a decade, and it earned that position. Its data model is mature: Flexible Assets let you define structured layouts for any kind of infrastructure record, the relationship engine links assets, passwords, contacts, and articles across your client base, and the integrations run deep into the PSA and RMM ecosystem. ConnectWise, Autotask, Datto, Kaseya VSA, NinjaRMM — if you're running a full MSP stack, IT Glue has a connector for it.

The documentation side is equally strong. Runbook templates, checklists, expiration tracking, and a mobile app round out a product that has clearly been shaped by years of real MSP feedback.

If you're managing 50 clients, running ConnectWise Manage, and need every piece of that stack to talk to each other on day one — IT Glue delivers that. No other platform in this space has its depth of integrations.

This article isn't about pretending otherwise. It's about identifying what IT Glue can't give you, and whether that matters to you.

The Kaseya problem

IT Glue was acquired by Kaseya in 2018. For many MSPs, that acquisition is the single biggest reason they're reading this article right now.

Kaseya's track record with acquired products includes aggressive pricing restructuring, cross-sell pressure, and bundling that makes it increasingly difficult to use IT Glue without buying into the broader Kaseya stack. Pricing that was predictable pre-acquisition has, for many customers, become opaque. Tiers have multiplied. Features have moved between plans.

There's also the July 2021 Kaseya VSA ransomware attack — one of the largest supply-chain attacks ever recorded, affecting thousands of MSPs downstream. It didn't compromise IT Glue directly, but it demonstrated what vendor concentration risk looks like in practice: a single vendor's compromise ripples through your entire client portfolio.

This isn't Kaseya-bashing. These are documented facts that belong in any honest comparison. When your documentation platform is owned by a company with this history, the question isn't whether you trust them today — it's whether you can afford to trust them indefinitely.

The structural problem with vendor-hosted documentation

The Kaseya situation is a specific instance of a general problem: when your documentation lives in a vendor's cloud, you've accepted a set of terms you didn't fully negotiate.

• Your data residency is wherever their servers are.
• Your uptime is whatever their SLA says — and SLAs don't bring back a client call where you couldn't pull the firewall password.
• Your export path is a support ticket and a waiting game, and no export is complete. Relationship graphs, asset cross-references, linked passwords — these don't survive a migration intact.
• Your security model is theirs. If you want stronger MFA enforcement, stricter session expiry, or a tamper-resistant audit log, you're waiting on their roadmap.

For homelab operators and small internal IT teams, this is academic — they're not on IT Glue anyway because the cost doesn't fit. For MSPs with compliance obligations in healthcare, legal, or finance, it's increasingly a real problem. For teams that have watched pricing shift once already, it's a question of when it happens again, not if.

What the open-source option actually looks like

Weavestream is a self-hosted IT documentation platform that covers the core IT Glue surface — assets, credentials, articles, domain monitoring, client portals — running entirely on your own infrastructure. Three Docker containers on top of Postgres and Redis. One compose.yml.

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 entire install. Your data lives in host-mounted directories you control. No Kaseya. No acquisition risk. No pricing restructure. Back it up with pg_dump and rsync, restore it the same way, and migrate it anywhere Postgres runs.

The license is AGPL-3.0-or-later. Source is on GitHub, images are on GHCR, and there are no telemetry calls, license checks, or paywalled features.

Side-by-side comparison

The honest read: IT Glue's integration depth and maturity are real advantages, especially at scale in a full PSA-driven MSP. Weavestream's integration catalog is smaller. If ConnectWise or Autotask sync is load-bearing for your workflow, that gap matters and you should weigh it seriously.

On data ownership, vendor independence, security posture, and total cost — Weavestream has no equal in this comparison.

Who should choose IT Glue

• You're a mid-to-large MSP fully committed to the Kaseya stack.
• ConnectWise, Autotask, or Datto integration is non-negotiable and needs to work on day one.
• Checklists and runbook templates are daily-use features for your team.
• You have no appetite for running infrastructure and the per-seat cost fits.

Those are legitimate reasons. IT Glue is a mature, capable product — the question is whether its ownership structure is one you can build your business on for the next decade.

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's pricing move once and don't want to be there when it moves again.
• You have clients in regulated industries where vendor-hosted credential storage is a compliance question.
• You want to audit the code, fork it, or extend it for your own tooling.
• You want your documentation accessible regardless of what happens to any vendor's infrastructure.
• You want to own the data, full stop.

Weavestream was built for operators who understand infrastructure and want their documentation platform to behave like infrastructure — something they run, control, and back up, not something they rent.

Security worth noting

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

When your documentation contains every password, every network device, and every server credential for every client — the security model of the platform holding that data matters enormously. With Weavestream, you define that model. With any cloud vendor, you inherit theirs.

The security documentation and encryption spec cover the full threat model if you want to read it before deploying.

Getting started

Deploy in under ten minutes with the Quickstart guide, or read the full Getting Started section for a production rollout with TLS and a reverse proxy.

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

Your documentation stack shouldn't be someone else's leverage. Weavestream puts it back in your hands.