SECURE REMOTE ACCESS + RMM · BUILT FOR MSPs
ManagedBit is a security-first remote control and RMM platform. End-to-end encrypted at 60 frames a second. Consent enforced by mechanisms, not policy documents. And honest about every feature — including the ones we haven't shipped yet.
THE NON-NEGOTIABLES
These aren't values-page decoration — they're standing engineering constraints, and several are enforced by tests that fail the build.
The relay forwards ciphertext. The control plane authorizes sessions it can never decrypt. There is no plaintext middle, ever — including every fallback path.
A non-removable, fail-closed presence indicator and a tamper-evident audit chain on every session and every channel. That rule binds us and our own staff too.
A security control whose precondition is missing refuses — it never warns and proceeds. Stand-ins are held to the same bar: if it can't enforce, it doesn't run.
Vetted primitives only — Noise, SPAKE2, ChaCha20-Poly1305, BLAKE3 — version-pinned, with the risky dependencies named and an external audit budgeted.
Agent, viewer, relay, control plane: all Rust. The C surface is a thin, audited boundary at the OS and codec edge — the CVE class that haunts this industry is designed out.
Anything recoverable recovers with your keys — BYOK, customer KMS, optional quorum escrow. Vendor-held master keys are structurally absent.
SIGNED AUTHORIZATION ONLY
Breach the middle and you hold noise. Keys are agreed endpoint-to-endpoint; the relay refuses unauthorized sessions but can never open authorized ones.
LAYER 01 CRYPTOGRAPHIC FOUNDATION
Every session is encrypted endpoint to endpoint. Everything in between — including our own infrastructure — forwards ciphertext and authorizes sessions it can never open. Keys live in silicon, proofs replace self-reports, and a stolen signing key mints refusals, not access.
NOISE XXpsk3 / IK · ChaCha20-POLY1305 · X25519 · BLAKE3
SPAKE2 PAKE · P-256 IN SECURE ENCLAVE / TPM · WEBAUTHN
Screen, input, terminal, files, clipboard — one authenticated Noise connection, per-channel AEAD, and no plaintext middle on any path.
The most exposed component holds the least: no keys, no frames, no tenant metadata — and it refuses sessions the control plane didn't sign for.
Device and technician identities are held in the Secure Enclave or TPM — usable on that machine, never copyable off it.
The control plane cryptographically proves a key lives in genuine hardware — policy sees verified verdicts, never the endpoint's word.
Seven separate signing roles behind an HSM-capable seam — and endpoints verify every grant against an independently-signed directory.
Sessions re-key continuously and re-prove both identities on a clock — a captured key or session state goes stale in minutes.
Protected tenants require a live hardware-key touch for every connection — and every resume. Stolen cookies stop being enough.
Attended support runs a real PAKE: short codes with no offline attack, and a spoken four-word check that defeats even a hostile relay.
LAYER 02 CONSENT & TRANSPARENCY
The person at the machine always knows — and their consent is enforced by mechanisms, not settings. If the indicator can't be proven visible, the session dies. If a notice can't render, the read refuses. And none of it can be bought away by a pricing tier.
VISIBILITY-PROOF WATCHDOG · PER-DISPLAY CHIPS · KNOCK
CAPTURE-EXCLUDED PROMPTS · HASH-CHAINED AUDIT
Screen sharing always shows a visible indicator — and visibility is proven, not assumed. Cover it, minimize it, wedge it: the session ends.
On "knock" devices a connection waits at the door — nothing captures, nothing injects — until a real human clicks Allow on a prompt built to resist fakery.
Sensitive actions mid-session prompt the person at the machine — on a surface the technician can neither see nor click.
Monitoring the monitors is a product feature: clients see what their MSP watches, and monitoring-shaped behavior gets flagged automatically.
Hash-chained, signed, append-only records on both the endpoint and the control plane. Edit, reorder, or delete anything and verification fails loudly.
Screen capture exists only while a screen session does — an idle managed machine is never "being recorded," and the OS's own indicator agrees.
Silent, notify, knock, or deny-while-in-use — per device, signed under its own control key, so posture can only ever tighten out from under an attacker.
No tier, add-on, or flag removes the consent indicator. We deliberately forfeited the covert-monitoring market so "no banner" is never ambiguous on any endpoint.
LAYER 03 THE LIVE SESSION
A screen-content codec that keeps text bit-exact, loss recovery measured in kilobytes, a rate controller that survives hostile networks — and every capability as a separately-permissioned channel inside one encrypted connection.
57–61 FPS MEASURED · LOSSLESS TEXT OVERLAY · ~3 KB LOSS HEALS
ROAMS IN ~5 ms · TERMINAL · FILES · CLIPBOARD · MULTI-MONITOR
Hardware HEVC capture-to-glass with encryption on — measured, on both desktop platforms, at desktop resolutions.
A content classifier routes every tile: text rides a lossless overlay above the video stream, bit-exact — even while scrolling.
Packet loss heals through tiny reference refreshes and per-frame parity — a momentary softness, not a frozen screen waiting on a keyframe.
The stream measures its path and degrades in a deliberate order — then climbs back on its own. On a clean network, all of it costs exactly nothing.
Networks change, processes crash, machines reboot — the session heals through all of it, and revocation still bites mid-heal.
Each remote monitor is an independent stream — one focused at full rate, the rest as live thumbnails that pause themselves under pressure.
Terminal, files, and clipboard are first-class channels with their own permissions — usable together or entirely without video.
GPU-less VMs and headless servers stream through a bespoke software codec with no video decoder at all — the case that breaks tools derived from game streaming.
LAYER 04 THE CONTROL PLANE
An MSP-shaped tenant tree with database-enforced isolation, policy-as-code that fails closed, grants that expire and re-authorize themselves, and enrollment that treats every new device as unproven until a human says otherwise.
POSTGRES RLS DAY 1 · CEDAR POLICY · DENY-BY-DEFAULT
REVOKE→KILL ~18 ms · OIDC + WEBAUTHN STEP-UP
MSP → client → site, with umbrella groups at any depth for resellers and holding companies. Acquisitions are a subtree move, not a migration project.
Tenants author real authorization policy — validated at write, inherited down the tree, with parent forbids that children cannot override.
Access is a short-lived signed capability, re-authorized on a schedule against current policy — and revocable to a dead session in tens of milliseconds.
Devices are born pending. A leaked installer token mints nothing — it buys a place in an approval queue, in front of a human, with risk flags attached.
A bundled Apache-2.0 identity provider behind a backend-for-frontend — tokens never touch the browser, and technicians start with exactly nothing.
Pin your whole environment to your networks — and recover from your own mistakes without the vendor ever being the recovery path.
Every endpoint holds one outbound connection carrying grants, revocations, policy, inventory, alerts, and jobs — with freshness measured by evidence, not socket optimism.
Your logo and colors on the console, the client, and the consent banner — cryptographically bound to your tenant, and impossible to weaponize.
LAYER 05 THE RMM
Inventory in seconds, monitoring at the edge, self-healing with hard floors, and fleet scripting that takes three independent keys to run — all built on the same consent and privacy machinery as the session core.
11 INVENTORY SECTIONS × 3 OSes · EDGE-EVALUATED MONITORS
EXACTLY-ONCE ACTIONS · SIGNED PRIVACY FLOORS
Software, patches, services, hardware, posture, network, certificates, users — from one agent on Windows, macOS, and Linux, kept fresh by deltas.
Sensitive collection is off until a signed tenant document turns it on — and some things are structurally not collectible at all.
Monitors evaluate on the endpoint against a signed per-device policy — the wire carries state changes, so cost scales with problems, not fleet size.
OS event capture where the privacy class of every source is decided by shipped code — not by whoever wrote the rule.
A crashed service restarts itself at 3 a.m. — inside limits stronger than the ones humans get, with a tamper-evident attempt trail.
Live CPU, memory, disk, and network at 1 Hz in the browser; processes and logged-in users on demand — audited, TTL-cached, structurally never historized.
Fleet scripting where the platform's authorization, a signed content directory, and the technician's own hardware touch must all agree — or nothing runs.
Blueprints, desired-state convergence, and patching — designed in depth with the per-platform truths stated honestly, landing phase by phase. The convergence engine is landing now.
LAYER 06 THE EXPERIENCE
A complete MSP console that never fakes a feature, and a native technician client where session states are first-class screens. If something isn't wired yet, it says so — the same rule this page follows.
21+ ROUTES · ⌘K PALETTE · NATIVE VIEWER
DEEP-LINK CONNECT · TERMINAL-FREE SETUP
Every surface without a backend carries a badge naming exactly what it awaits. Unwired actions disable instead of pretending. Refusals render verbatim.
⌘K to anywhere — including "connect to that machine." Scope the whole console to one client. Save your views. Export what you see.
Session states are first-class screens: the verification ceremony gates input and video, interruptions show a live countdown, endings tell the truth.
From console to live session in one click — through a handoff designed so a malicious link can never add trust.
A first-run wizard takes a technician's machine from blank to operational — pin the control plane, generate a hardware-backed key, register it — across as many consoles as they work in.
Console, technician client, and the endpoint's consent surfaces re-skin to your tenant at runtime — inside hard limits that keep branding from becoming phishing.
A no-install, nothing-left-behind support app: the user runs it, reads a code aloud, and gets help — engineered assuming criminals will try to abuse it.
Session recording as an authorized member of the encryption group — compliance-grade, higher quality than the live view, and still unreadable by the vendor.
THE PRACTICE
Process is a feature. Every security-bearing design goes through independent adversarial review before code exists; every landing publishes a verification matrix run on real hardware; every failure ever caught becomes a permanent regression scenario.
Three independent lenses — hostile peer, privacy, protocol — attack each design before code. Findings are binding. Criticals get found on paper, where they're cheap.
Nothing is "done" until a published matrix passes on real hardware — refusal paths included — with the audit chain re-verified at every landing.
Roughly fifty live-caught media failures are catalogued with mechanism and fix, and replayed by a deterministic harness so none of them can return quietly.
A standing cross-continent staging path (~200 ms round trip) through a public cloud relay — judged on experience metrics: time at zero fps, freeze duration, glass age.
The one recurring bug class in this industry is a control that fails open when its precondition is missing. Here that shape is a named rule, hunted in review, with exceptions argued in writing.
The threat model states its non-goals. The security review records what's still open next to what's fixed. Credibility comes from the list of things we say we don't do yet.
"The crypto core is the strongest part of the codebase… nearly every serious finding is one shape — an authorization control that fails open when its precondition is absent."
PLATFORMS & SOVEREIGNTY
Both desktop platforms are complete, Linux is deep into its arc — and the whole plane is built to run where you decide, with the honest state of every column below.
| CAPABILITY | macOS | WINDOWS | LINUX |
|---|---|---|---|
| Remote control | ● | ● | ◐ X11 |
| Terminal · files · clipboard | ● | ● | ◐ |
| Hardware-bound identity | ● | ● | ● |
| Key attestation | ○ MDA ARC | ● | ● |
| Inventory (11 sections) | ● | ● | ● |
| Monitoring + self-healing | ● | ◐ | ◐ |
| Fleet scripting | ● | ◐ | ◐ |
| Privileged service topology | ● | ● | ◐ |
| Technician viewer | ● | ● | ○ |
● LIVE ◐ PARTIAL — REMAINING HALVES TRACKED PER-DOC ○ PLANNED
WHERE A LINUX DESKTOP CAN'T PROVE THE CONSENT BANNER IS VISIBLE, WE REFUSE TO HOST — BY DESIGN.
One compose file stands up the control plane; the relay is a single binary on your own node. No PaaS dependencies, no Node runtime, no CDN or font callouts — the console is served by the Rust binary itself.
Control-plane signing runs behind a PKCS#11 seam — non-extractable on your token — with a cloud-KMS adapter on the same seam. Seven roles, independently rotatable, live.
Relay and control plane deploy where you choose. Customer-held keys (BYOK) and per-tenant encryption are designed arcs on the roadmap — stated as roadmap, not implied as shipped.
The bundled identity provider is Apache-2.0 — chosen for license, not fashion — and swappable behind one OIDC issuer URL. Per-client bring-your-own-IdP federation is the designed next step.
ROADMAP
Preview surfaces exist and say so in the product. Designed means an adversarially-reviewed design is ratified and waiting on build. Planned means we've named it and sequenced it — nothing more.
THE HONEST LEDGER
Generated from the same engineering documents the product is built from. LIVE means landed and verified end-to-end on real hardware. PREVIEW means the surface exists and says so. Nothing here is upgraded for marketing — that's the point.
ManagedBit is in active development with early MSP partners. If provable security and honest engineering are how you want your remote stack built — let's talk.