Test it
Run Weavestream in your own environment and report what works, what breaks, and what feels missing.
Self-hosting docsOpen source · AGPL-3.0-or-laterOpen source because
Open source because
your documentation should not be
a hostage.
Your IT documentation is more than a collection of notes. It is the operational memory of your business: clients, assets, credentials, procedures, domains, IPs, and the relationships between them.
Weavestream is open source because that kind of information should not be locked behind a vendor-controlled platform, hidden roadmap, license server, or pricing model you cannot control.
Open source
Self-hosted
Docker-first
No telemetry
No license checks
No feature gates
The trust model
This is not just a license. It is a trust model.
Closed documentation platforms ask you to trust the vendor completely. Trust their security. Trust their pricing. Trust their roadmap. Trust their export tools. Trust that the product will not change in a way that makes your business harder to run. Weavestream takes a different approach.
Closed The rented model
- Your data lives on the vendor's infrastructure, not yours
- Features arrive when (and if) the vendor decides
- Pricing can change — per-user, per-client, per-tier
- Export quality only becomes clear when you try to leave
- Your access requires a working license callback
- You cannot inspect what you cannot see
Weavestream The owned model
- Self-hosted on your server, NAS, VPS, or private cloud
- Source is open, auditable, and forkable under AGPL-3.0
- Your database and backups, on your schedule, in your bucket
- No license checks — the app runs offline, forever
- No telemetry — nothing phones home
- Issues, PRs, and roadmap visible to everyone
What it means here
What "open source" means in Weavestream.
Open source should mean more than being able to see a repository. For Weavestream, it means building the product around ownership and transparency from the start.
01
Source code you can inspect
The application code is available so users can review how the platform works, understand what it is doing, and contribute improvements.
02
Self-hosted by design
Weavestream is built to run on your own infrastructure: a server, NAS, VPS, homelab, or private cloud — not a vendor-controlled tenant.
03
Your database, your backups
Your documentation lives in a stack you control. You decide where it runs, how it is backed up, and how it fits into your operational processes.
04
No telemetry
Weavestream does not phone home with your usage data. Your documentation platform does not need to report back to a vendor to be useful.
05
No license checks
The system does not depend on a remote license server to decide whether you can access your own documentation. Run it offline, run it forever.
06
No artificial feature gates
No open-core maze where the useful features are always one paid tier away. Weavestream is useful as a self-hosted open-source product.
No nonsense
No telemetry. No license checks. No nonsense.
Your documentation platform should not need to call home to prove it is allowed to run. It should not collect usage data because that is convenient for the vendor. It should not place your operational memory behind a remote entitlement system.
phones home
No telemetry.
Your usage data stays with you. No background analytics SDK. No silent metrics. No "anonymous diagnostics" you cannot disable.
$curl localhost:8080/healthz
{ "telemetry": "disabled" }
{ "telemetry": "disabled" }
license server
No license checks.
Your access should not depend on a vendor's license server. Run Weavestream offline, on an air-gapped network, forever, with no callback to anyone.
$curl localhost:8080/healthz
{ "license_check": false }
{ "license_check": false }
paid tier
No feature games.
The useful parts of the platform should not be hidden behind artificial tiers. One edition. All modules. Same source for everyone.
$curl localhost:8080/version
{ "edition": "weavestream" }
{ "edition": "weavestream" }
Built for self-hosting
Run it where your documentation belongs.
Weavestream is designed for people who are comfortable owning their infrastructure. Deploy it on your server, NAS, VPS, private cloud, or homelab — close to the systems and workflows it documents. For MSPs and IT pros, self-hosting is not just a technical preference. It is a control decision.
your boundary
Admin / TechBrowser · HTTPS
Reverse proxyNginx · Caddy · Traefik
TLS & authYour certs · Your IdP
Weavestreamweb · api · workers · 4 containers
DatabasePostgres · SQLite
File storageLocal · S3 · MinIO
Backupsrestic · borg · your bucket
No outbound · no telemetry · no license callback
You control the environment. You control access. You control backups. You control the upgrade window. You control the future of the platform.
Built in the open
Used in the real world. Built in the open.
Weavestream was created to solve a real problem: structured IT documentation without renting the platform forever. It is actively used, actively improved, and developed in public. Rough edges are not hidden behind sales copy. Roadmap decisions can be discussed. Users help shape the product instead of waiting on a vendor roadmap.
●
a3f719d
FEATipam: detect overlapping subnets across companies
2h
●
7c0b22e
FIXvault: TOTP rotation invalidates cached secret correctly
5h
●
e218fc0
DOCSself-hosting: postgres tuning notes for >1k assets
14h
●
1ff8a44
FEATarticles: WYSIWYG/markdown toggle persists per-article
1d
●
52ac9b1
FEATaudit: cursor-paginated UI with URL-sticky filters
2d
●
d04e8a9
FIXportal: visibleToClients honored on file attachments
3d
●
b6c1230
DOCSreadme: docker-compose quickstart now under 60s
4d
●
f8e4471
FEATsearch: full-text indexing for KB articles & uploads
6d
Open issues, open PRs, open direction.
Every change happens in a public commit. Every bug becomes a public issue. Every roadmap decision is visible to anyone who wants to see where the project is going. That's how trust gets built in open source — by doing the work where everyone can read it.
Commits · 30d
218
Contributors
12 and counting
Open issues
42
Current release
v1.8.8
How to contribute
Help shape the project.
Weavestream is open to people who want to test, improve, document, discuss, and extend it. You do not need to be a full-time developer to help. Real-world feedback from MSPs, IT pros, and self-hosters is just as valuable as code.
Open issues
Found a bug or confusing workflow? Open an issue so it can be tracked, discussed, and improved in public.
GitHub IssuesRequest features
Describe the real-world documentation workflow behind the request. That context is what helps the project prioritize well.
Feature requestsImprove docs
Clear documentation helps more people self-host successfully. Typos, examples, edge-cases — all welcome.
Docs sourceSubmit code
Contribute fixes, improvements, new integrations, and new capabilities. PRs welcome; check the contribution guide first.
Contribution guideShare feedback
The best product direction comes from people using it for real IT work. Tell us what's wrong. Tell us what's right.
DiscussionsLicense & philosophy
The license matters.
Weavestream is open source so users can inspect it, run it, improve it, and keep control of their documentation stack. The license is part of that philosophy.
Why AGPL-3.0-or-later?
AGPL is a copyleft license designed to keep software open even when it is offered as a network service. For a self-hosted documentation platform, that protection matters: anyone who runs Weavestream and exposes it over a network is expected to keep the source available under the same terms.
For MSPs, IT pros, and self-hosters running Weavestream for their own operations, this is a normal, unremarkable license. For anyone considering re-hosting a closed fork of Weavestream as a paid SaaS without sharing improvements back — it is not.
Plain-English note: We are not lawyers, and this is not legal advice. The full license text is available in the repository — read it, share it with counsel if your situation calls for it, and reach out if anything is unclear.
Own the stack
Own your documentation stack.
Weavestream gives MSPs, IT pros, and self-hosters a structured documentation system they can run, inspect, back up, and improve on their own terms. If your documentation is the memory of your business, it should live somewhere you control.