Knox connects dispatching, training, and knowledge into one platform — unifying the tools our technicians use daily, powered by AI that runs inside our own walls.
Tickets land without structured matching to who's qualified. Training isn't tied to the work techs do. Knowledge lives in scattered systems. Each gap reinforces the others.
Type a client name. See everything that matters about them. Ask a question and Knox pulls the answer from whichever system has it. Resolve a ticket and Knox drafts the documentation.
Structured ticket-to-tech matching. Certified techs ranked by fit, availability, and track record. Remote-first prompting. Ticket bundling for on-site visits.
AI-generated assessments tied to dispatch categories. Techs certify to become eligible. Pre-certified from 8 years of historical performance data.
One box. Every system. Semantic search that understands what you mean, not just what you typed.
Resolve a ticket, click once, get a draft KB article. Three tiers: general, per-client, and procedural. Configuration changes documented automatically.
Knox flags tickets that resolved without matching documentation. Closure quality gate catches empty resolution notes before they disappear.
Tenant type, MFA, license mix, recent activity, risk trend, what's coming due. At a glance.
Knox is what techs see. Underneath is a layered platform where each layer has one job. The Privacy Boundary is the hard rule: nothing identifying crosses it without being tokenized first.
Client identifiers are tokenized before any external AI call. Sensitive analysis runs on local hardware with ECC memory. Nothing identifying leaves the building.
Client names, hostnames, emails, IPs — all replaced with stable anonymous tokens before any external AI call. The mapping never leaves our key store.
Sensitive workloads — security incidents, anything touching credentials or PII — run on a dedicated local AI server with 96 GB of ECC GPU memory. Never leaves the building. Ever.
Knox has no public DNS, no internet-facing ports. Every connection — technicians, dashboards, anything — runs through our private Netbird mesh. From the office, from home, from a client site: same private network.
Knox has no live connection to Passportal. Credentials never enter the AI pipeline. Documentation may be exported once as a seed for Knox's own KB; after that, all new docs land in Knox.
External AI services run on contractual no-training tiers. Documented vendor agreements, not handshake assurances.
Every AI call is logged: what was sent, what came back, who triggered it. Reviewable, reportable, defensible.
Stable tokens mean Knox can still cluster, score, and trend across clients — privacy doesn't cost us insight.
Development begins with a discovery analysis against 8 years of ConnectWise data — before any code is written. That analysis produces the taxonomy, certifications, KB priorities, and training plan that Knox operationalizes phase by phase.
Python everywhere so both developers can work on any part. Well-supported, internally hostable, replaceable if needed.
Other languages permitted for one-off tools and experiments. The platform standardizes.