The product · v1.8.8

Structured IT documentation,
without the SaaS handcuffs.

Weavestream brings clients, assets, credentials, articles, domains, SSL records, IP ranges, files, portals, integrations, search, and audit history into one self-hosted documentation system.

Built for MSPs, IT pros, and small teams who need more than a wiki and want to own the platform that holds their operational memory.

Open source Docker-first No telemetry No license checks Structured records
Product overview

Everything your IT documentation needs in one connected system.

Weavestream is built around structured records instead of loose pages. Companies, assets, passwords, articles, domains, files, IP ranges, users, and integrations each have a proper place — and the real value comes from how they connect.

Records Security Infrastructure Workflow 14 modules · 1 connected schema
Companies
tenants · sites · contacts
Assets
14+ field types · custom layouts
Articles
WYSIWYG · Markdown · folders
Files
images · docs · configs
Relationships
typed edges · n-to-n · backrefs
Password Vault
AES-256-GCM · TOTP · HIBP
Domains & SSL
WHOIS · DNS · TLS validity
IPAM
subnets · utilization · conflicts
Integrations
scheduled · on-demand · per-run
Search
FTS · Cmd+K palette
Starred
per-user · sidebar · dashboard
AI Chat
persistent panel · OpenAI-compatible
Users & RBAC
invite-only · MFA · roles
Audit Log
append-only · diffs · tamper-proof
Client Portal
read-only · scoped · per-tenant
Core modules · 14

Documentation modules built to stay searchable, consistent, and connected.

Each module is a real, structured part of the platform — not a marketing checkbox. Browse the cards below to see what each one covers.

Company Management

Organize documentation around the companies, clients, departments, or environments you support.

contactsaddresseslogohierarchytype
Asset Management

Document servers, workstations, network gear, applications, licenses, and services with structured records.

custom layouts14+ field typessearchablevendors
Password Vault

Store credentials in context — linked to the clients, assets, and procedures that need them.

AES-256-GCMTOTPHIBPhistorygenerator
Documentation Articles

WYSIWYG or raw Markdown — procedures, runbooks, notes, and reference material, organized into per-tenant folders.

TiptapMarkdownper-tenant treelinked records
Domain & SSL Monitoring

Track WHOIS expiry, DNS health, and TLS certificate validity across every hostname you support.

WHOISDNS healthTLSexpiry dashboards
IP Address Management

Per-company IPv4 subnets with utilization, conflict detection, manual reservations, and asset occupancy.

IPv4 subnetsutilizationconflictsreservations
File Uploads & Photos

Attach files, photos, configs, exports, and scripts directly to the records they support.

per-tenantthumbnailsPDF · JSON · YAML
Client Portal

A scoped read-only view per tenant — expose articles, assets, passwords, and domains selectively.

read-onlyper-tenantvisibility flags
Search & Command Palette

Postgres full-text search across articles, assets, and uploads, plus a fast Cmd+K command palette.

FTSCmd+Kscope prefsfast nav
Starred Items

Per-user shortcuts to frequently used companies, assets, passwords, and articles — pinned to the sidebar.

per-usersidebardashboard
User Management & RBAC

Invite-only onboarding, forced TOTP MFA, two-layer roles, contractor access, and time-expiring memberships.

invite-onlyMFArolescontractorexpiring
Audit & Compliance

Append-only audit log with before/after JSON diffs, filters, pagination, and DB-role tamper protection.

append-onlyJSON difftamper-proof
Integrations

Built-in drivers that sync external inventory into tenant asset records, on demand or on a schedule.

driversscheduledper-run status
AI Chat

A persistent chat panel — ask questions, draft documentation, and edit articles using your own OpenAI-compatible LLM.

persistentOpenAI-compatiblearticle edits
Up close

Four modules, in the actual UI.

A closer look at four of the most important modules.

Module · Password Vault

Credentials, in context.

Per-tenant credential storage with AES-256-GCM encryption, TOTP secrets, password history, breach checks, strength scoring, and an offline password generator — all linked to the systems they unlock.

  • Per-tenant credential storage with AES-256-GCM encryption
  • TOTP secrets stored alongside the password they pair with
  • HaveIBeenPwned breach checking and strength scoring
  • Full version history per credential
  • Offline password generator — no third-party calls
  • Linked back to the assets, clients, and procedures that need them
acme-co / passwords
Acme Co. · Credentials
67 ITEMS · 12 WITH TOTP
+ NEW
FW
root@fw-edge-01linked · asset: fw-edge-01 · proc: failover-runbook
TOTP
2d
VP
vpn-adminlinked · asset: fw-edge-01 · domain: vpn.acme.co
TOTP
8d
NS
nas-mgmtlinked · asset: nas-hq-01
no TOTP
94d
FT
fortinet-portallinked · vendor: Fortinet · contract
TOTP
21d
SV
portal-svclinked · asset: srv-app-01 · article: deploy
TOTP
6d
SW
sw-core-04 · enablelinked · asset: sw-core-04
no TOTP
3d
Module · Documentation Articles

WYSIWYG when you want it, raw Markdown when you need it.

Articles give teams a place for human-readable documentation: procedures, troubleshooting steps, client notes, standards, internal runbooks. Each article can be authored in a Tiptap WYSIWYG editor or raw Markdown — chosen per article — and organized into a folder hierarchy per tenant.

  • WYSIWYG article editor backed by Tiptap
  • Raw Markdown mode toggle per article
  • Per-tenant folder hierarchy with drag-and-drop reorder
  • Inline links to other records — assets, credentials, articles
  • Useful for procedures, runbooks, standards, and reference material
  • Designed to live alongside structured records, not replace them
acme-co / articles / runbooks / vpn-failover
H1H2BI· · ·Link WYSIWYGMARKDOWN
VPN failover · Acme HQ

This runbook covers the secondary path when vpn.acme.co fails the daily health check. The procedure references the fw-edge-01 asset and the vpn-admin credential.

  1. SSH into the secondary firewall using root@fw-edge-02.
  2. Promote the standby tunnel — run fnsysctl vpn-fail-over.
  3. Verify the SSL certificate on vpn.acme.co still chains correctly.
  4. Update the SSL · Domains view if the cert was rotated.

If the secondary tunnel does not come up, follow the vendor escalation article instead.

Module · Domains & SSL

The infrastructure details that quietly expire.

Domains and certificates are easy to forget until they fail. Weavestream helps track WHOIS expiry, DNS health, and TLS certificate validity across hostnames, with aggregate dashboards for upcoming expirations.

  • WHOIS expiration monitoring across registrars
  • DNS health checks per hostname
  • TLS certificate validity and chain inspection
  • Aggregate dashboards for upcoming expirations
  • Per-company filters and ownership tracking
  • Useful for portals, apps, infrastructure endpoints, and client domains
acme-co / domains · expiring
Hostname90d · expiry window
vpn.acme.coWHOIS · DNS · TLS
31d
soon
portal.northwind.ioWHOIS · DNS · TLS
44d
watch
mail.globex.netWHOIS · DNS · TLS
62d
watch
acme.coWHOIS · DNS · TLS
418d
healthy
portal.acme.coWHOIS · DNS · TLS
204d
healthy
mail.acme.coWHOIS · DNS · TLS
312d
healthy
Module · IPAM

IPv4 address space, finally in context.

Weavestream includes IPAM for managing per-company IPv4 address spaces. Track subnets, see utilization, detect conflicts, reserve addresses manually, and visualize address-space usage. Replaces scattered spreadsheets and stale network notes.

  • Per-company IPv4 subnet management
  • Utilization tracking with live counts
  • Auto-discovered asset occupancy from linked assets
  • Conflict detection across subnets
  • Manual reservations with notes and owners
  • Address-space visualization at a glance
acme-co / ipam / 10.40.0.0/24
10.40.0.0/24 · HQ Core LANauto-discovered · 2 conflicts
147/256 · 57%
USED · 132 ASSET · 15 RESERVED · 2 CONFLICT
Asset Critical Reserved Conflict
10.40.0.1fw-edge-01
10.40.0.5sw-core-04
10.40.0.20nas-hq-01
10.40.0.50(reserved · printer pool)
The weave · asset view

Documentation becomes more useful when it knows what it belongs to.

Most documentation systems can store information. Weavestream is designed to connect it. Here is what a single asset — a firewall at a client's HQ — looks like from the inside.

Asset · Firewallfw-edge-01 · Acme HQ
CO
CompanyAcme Co.
VP
VPN credentialvpn-admin
WI
WAN IP72.14.180.22
SS
SSL certificatevpn.acme.co
PW
Admin passwordroot@fw-edge-01
BK
ProcedureBackup & restore
ND
Network diagramHQ-core-v3.pdf
SA
Support articleVPN failover steps
VA
Vendor accountFortinet portal
Search helps when you know what you need. Relationships help when you only know where to start.
Designed for

Real IT workflows, not feature theater.

Weavestream is built for the everyday documentation work that keeps IT environments supportable: onboarding clients, documenting infrastructure, securing credentials, tracking expirations, and finding context when something breaks.

01 Onboarding

Document a new client consistently.

Create the company record, add assets, attach credentials, write procedures, upload reference files, document domains, map IP ranges, and expose selected records through the portal.

  1. Create the company / tenant record
  2. Add assets and custom fields
  3. Store credentials and TOTP secrets
  4. Write procedures and KB articles
  5. Attach files and photos
  6. Track domains, SSL, DNS, and IP ranges
  7. Select what clients see in the portal
02 Troubleshooting

Follow the trail when something breaks.

Start from a client, asset, credential, domain, or search result. Follow related records until you find the procedure, access details, or supporting file you need.

  1. Search or open the client
  2. Find the affected asset
  3. Review linked credentials and procedures
  4. Check domains, SSL, DNS, or IP records
  5. Open supporting files or notes
  6. Update documentation after resolution
03 Maintenance

Keep documentation from going stale.

Use integrations, scheduled syncs, audit history, starred items, expiration tracking, and structured records to prevent the slow drift into a forgotten pile of old notes.

  1. Sync inventory from integrations
  2. Review domain and SSL expiration dashboards
  3. Track IP utilization and conflicts
  4. Use audit logs to see what changed
  5. Star important records for quick recall
  6. Update procedures as systems evolve
Security & control

Self-hosted control with security-minded defaults.

Weavestream is designed for teams who care where their documentation lives. Run it yourself, control the database, manage access, enforce MFA, review audit history, and keep sensitive records inside infrastructure you choose.

Self-hosted by design

Run Weavestream on your own server, NAS, VPS, or private cloud. Your hardware, your database, your control.

Credential encryption

Password vault records use AES-256-GCM encryption. TOTP secrets are stored alongside the credential they pair with.

MFA and roles

Invite-only onboarding, forced TOTP MFA, and two-layer role-based access controls — including time-expiring contractor access.

Audit visibility

Append-only audit log with before-and-after JSON diffs, cursor-paginated UI, URL-sticky filters, and DB-role tamper protection.

No telemetry · no license checks

The product is open source and built without background tracking, license callbacks, or artificial feature gates.

Honest framing

What Weavestream is — and what it is not.

Open-source IT documentation comes with expectations in both directions. Here is the honest read.

IS Weavestream is

  • A structured IT documentation platform
  • Self-hosted and open source
  • Built for MSP-style client documentation
  • Useful for IT teams and serious self-hosters
  • Designed around assets, credentials, articles, domains, IPs, and relationships
  • Practical today and actively improving

IS NOT Weavestream is not

  • A generic wiki with a nicer theme
  • A closed SaaS platform
  • A per-user subscription product
  • A clone trying to match every enterprise feature overnight
  • A replacement for every PSA / RMM / security platform
  • A polished sales machine pretending there are no rough edges
Start building

Build documentation
you can actually depend on.

Explore the product, review the source, or start self-hosting Weavestream and see how structured documentation changes the way you support clients and infrastructure.