Documentation is too important to rent forever.
Weavestream was built for MSPs, IT pros, and small teams who believe documentation should be structured, connected, self-hosted, and under their control.
It started with a simple frustration: good structured documentation matters, but renting the system that holds your operational memory forever does not feel right.
Built because the problem was real.
Weavestream started as a practical problem. I liked the idea of structured MSP documentation. I liked having clients, assets, credentials, articles, domains, and procedures organized in a real system instead of scattered across random notes.
But I did not want to keep renting the place where that knowledge lived. Not the database. Not the source. Not the hosting. Not the export buttons that don't quite work when you eventually try to leave.
So Weavestream was built as the self-hosted documentation system I wanted to use: structured enough for real IT work, open enough to inspect, and owned by the people running it.

Your operational memory should not live behind someone else's lock.
IT documentation is not just content. It is how you support clients, recover systems, onboard technicians, remember decisions, find credentials, trace infrastructure, and keep environments understandable.
When that knowledge lives entirely inside a rented platform, your business memory becomes dependent on someone else's pricing, roadmap, policies, exports, uptime, and incentives.
That may be acceptable for some teams. But for people who prefer to own their stack, it creates the wrong kind of dependency.
Your documentation should be an asset, not a hostage.
Notes are flexible. Structure makes them dependable.
A wiki can store almost anything. That flexibility is useful, but it also means every client, asset, password, domain, and procedure can be documented differently. That works until you need consistency.
new one starts with fG7…?
renew in
ask Liang
run fnsysctl …
(full thing on confluence??)
rotated last month
backup proc lives in old wiki
Structured documentation gives every important part of an environment a proper place. Clients are clients. Assets are assets. Credentials are credentials. Domains, IP ranges, procedures, files, and articles are not just paragraphs buried in a page — they are records that can be searched, linked, audited, and reused.
The real value is the weave.
IT work rarely starts and ends in one place. You might begin with a client, then need the firewall, then the WAN IP, then the VPN credential, then the backup procedure, then the domain record, then the article explaining how it was configured.
A record should not live alone. An asset should know the credentials, files, procedures, IPs, domains, and client it belongs to. A password should point back to the systems that use it. A document should connect to the thing it explains. Weavestream is named for that idea: weaving information into a system instead of letting it drift apart.
Search helps when you know what you need. Relationships help when you only know where to start.
Open source is a trust model.
Weavestream is open source because documentation software asks for a lot of trust. It may hold client details, infrastructure notes, credentials, procedures, files, domains, internal decisions, and the map of how systems fit together.
For that kind of software, visibility matters. You should be able to inspect the source, understand how the system works, run it where you choose, back it up on your terms, and keep using it without license checks or artificial gates.
Inspectable
The source is available so technical users can see how the system works.
Self-hosted
Run it on your own server, NAS, VPS, or private cloud.
No telemetry
No background product tracking built into the platform.
No license checks
No artificial gate between you and the system you operate.
Built for people who take documentation seriously.
Weavestream is for MSPs, solo IT consultants, internal IT teams, and serious self-hosters who want structured documentation without surrendering control. It is especially useful if you manage multiple environments, support clients, maintain credentials, track infrastructure, or document repeatable procedures.
It is not trying to be every PSA, RMM, password manager, wiki, or monitoring platform at once. It is focused on one job.
Client documentation, consistently.
Companies, assets, credentials, procedures, and relationships across every client — without another rented platform.
Records you can actually rely on.
Consistent records for infrastructure, systems, procedures, access, and operational knowledge — built for the work, not the slide.
A serious stack for serious homelabs.
A real documentation platform for the infrastructure you run yourself — servers, NAS, containers, domains, SSL, IPs.
Seven convictions we won't compromise on.
- 01
Documentation is infrastructure.
- 02
Structure beats scattered notes.
- 03
Relationships matter more than folders.
- 04
Ownership matters when the data is important.
- 05
Open source builds trust.
- 06
Self-hosting should be practical, not painful.
- 07
Good documentation makes the next problem easier to solve.
Own your IT documentation.
Explore the product, review the source, or start self-hosting Weavestream and see how structured, connected documentation changes the way you manage IT knowledge.