A technician standing in a client’s server closet, phone in one hand, patch cable in the other, needs one thing fast: the admin password for the switch they’re staring at. Pulling that up shouldn’t mean squinting at a desktop layout crammed onto a six-inch screen, and it definitely shouldn’t mean texting the office to look it up.
Weavestream ships a dedicated mobile app for exactly this moment — served from your existing instance at /m, with no separate deployment, no app store listing, and no second server to stand up.
Same Instance, Same Accounts, Same Audit Trail
The mobile app isn’t a stripped-down companion product — it’s part of the normal Weavestream container, using the same accounts, sessions, and permissions as desktop. Open your profile menu and choose Mobile app, or browse straight to https://your-instance/m on a phone. Sign-in, including MFA, works exactly as it does at a desk.
That matters for anyone thinking about this from a compliance angle: every action a technician takes on mobile is authorized server-side exactly like a desktop request, and it lands in the same append-only audit trail. There’s no separate mobile API with its own authorization logic to reason about — one system, one set of rules, one place auditors need to look.
Built Around a Different Question Than Desktop
Desktop Weavestream answers “help me organize and document a client’s environment.” The mobile app answers a narrower question: what does a technician need while standing in front of the hardware? That distinction shapes what’s actually on the phone.
Passwords get full create, edit, and archive support, with the same step-up re-authentication and reveal auditing as desktop, one-time TOTP codes with a countdown, and copy-to-clipboard that clears itself automatically. This is the core use case — an MSP mobile app that can’t reveal a credential with the same audit rigor as the desktop version isn’t worth opening in a server room.
Assets support full create, edit, and archive across your custom layouts, including file fields with direct camera capture — photograph a serial plate or a rack layout and it attaches straight to the asset record instead of living in a phone’s camera roll waiting to be uploaded later.
Documentation is read-only on mobile, for both rich-text and Markdown articles. Editing intentionally stays on desktop.
Search is scoped to whichever organization you’re inside — no scope toggle, deliberately, so a technician working a client site can’t accidentally surface another client’s records mid-search. From the launcher (before you’ve entered an organization), search runs across every organization you have access to, and every result names its organization before you open it.
Ask anything, the AI assistant, runs full-screen on mobile when AI is configured — including previewing, applying, and rejecting article change proposals right from the phone. Edits show a line diff against the current article, and applying a change re-checks authorization server-side exactly like desktop.
Installable, With No Data Left Behind
The mobile app is a Progressive Web App, so it installs to a home screen with a standalone window and fast startup — on Android via More → Install app in Chrome, on iOS via Safari’s Share → Add to Home Screen. No app store review, no separate binary to keep updated; the next deploy of your Weavestream instance is the next version technicians see on their phones.
What doesn’t happen is any local data caching. Passwords, articles, and assets all require a live connection — screens show an honest “no connection” state instead of serving stale records, and revealed secrets live only in memory, clearing when the app goes to the background. For a tool that puts client credentials on portable hardware technicians carry into the field, that’s a deliberate security posture, not a missing feature. What is cached is the app’s own code and static assets — nothing account-specific — so there’s nothing sensitive sitting on a lost or stolen phone.
What Deliberately Stays on Desktop
Weavestream’s docs are upfront about the boundary, and it’s worth knowing before you rely on the app for something it isn’t built for: article authoring, rich-text asset field editing, admin and integration settings, IPAM, domain monitoring, exports, and reporting all stay on desktop. Two-factor setup and backup codes are desktop-only by design, since enrollment is the one flow that would put a shared secret on the phone. A two-factor reset requires an administrator on any surface — there’s no self-service disable button, mobile or otherwise.
None of that is an accident. It’s the same philosophy that shapes the rest of Weavestream: give field technicians a fast, audited, purpose-built tool for the moment they’re actually in, and keep configuration-heavy work where a full keyboard and screen make it safer to do correctly.
Why This Belongs in Self-Hosted IT Documentation, Not a Separate App
A lot of MSP tooling treats mobile as an afterthought — a responsive web view that technically loads on a phone, or a native app with its own backend and its own security model to audit separately. Weavestream’s approach keeps the mobile surface inside the same self-hosted instance, the same RBAC, and the same audit log as everything else, which means adopting it doesn’t expand your attack surface or add a vendor dependency. It’s one more reason a self-hosted platform can out-execute SaaS competitors on the field-technician use case specifically: you’re not waiting on a vendor’s mobile roadmap, and you’re not trusting a second company with the same credentials you already trusted the first one with.
Getting Started
If you’re already running Weavestream, open your profile menu on desktop and choose Mobile app, or navigate to /m on a phone and sign in. Install it to the home screen and open it online once before counting on it in a spot with poor signal — iOS in particular needs that first online launch to populate the app’s own cache.
New to Weavestream? The quickstart guide gets the full stack running with Docker Compose in a few minutes — the mobile app works out of the box at /m once your instance is up, no extra configuration required.