Use WAIT Local Agent to connect plans, approvals, execution, and evidence without losing the boundaries that make managed IT work trustworthy.
WAIT Local Agent supports different types of IT work, from day-to-day support and solution planning to project reviews and handoffs.
Best for
MSPs and internal IT teams
Make support faster and easier for your team.
Flow: Ticket or operational signal → local context → triage / plan → bounded action or workflow → approval when required → execution → audit evidence
Best for
Consultants, architects, and technical teams
Turn ideas into clear plans that everyone can follow.
Flow: Business problem → guided discovery → provider-neutral blueprint → architecture decision → implementation target → governance / evaluation → delivery handoff
Best for
Product and engineering teams
Launch with clarity and full documentation.
Flow: Local project → local scan → review the evidence package → explicit upload confirmation → Launch Passport handoff → results
Each path needs the same core controls: identity, tenant or client scope, deterministic policy, approvals, bounded connectors, execution records, evidence, and audit. Keeping those controls in one runtime avoids separate safety models for each workflow.
Give operators a readable path through routine support, system changes, and the records that make handoffs easier.
Per-client evidence collection, requirement mapping, readiness tracking, and operations records that support a customer's own NIS2 work. WAIT provides evidence and mapping support, not compliance determinations.
Adds assurance-oriented evidence review, readiness reporting, and operations support for European engagements on top of the per-client MSP lane.
Local Agent turns a business requirement into a bounded execution path that your team can inspect and approve.
A data processing agreement is available as part of the enterprise and MSP sales process through the inquiry path.
“WAIT Certified Local Agent” designates an official WAIT build and product-assurance level. It is a WAIT build assurance mark, not a regulatory certification of any kind.
A managed client is one distinct customer organization whose systems an MSP operates through WAIT Local Agent under a per-client subscription.
Each organization keeps its own scoped runtime, approvals, evidence, and support context. Talk with WAIT about onboarding and the operating model that fits your service.
Each client organization has its own data, approvals, and context, so you stay organized, secure, and in control.
WAIT Local Agent 1.x is the earlier Apache 2.0 line. If you use that version, the original Apache era rights remain in place, including the latest 1.x release.
Precisely: 1.x is a preserved Apache-2.0 baseline. Rights previously granted under Apache-2.0 remain unchanged, and the latest 1.x release, v1.1.1, comes from this Apache-era line.
View 1.x licensing details ↗The newer 2.x line uses a different license and includes WAIT branding terms. Community use is still allowed. Commercial branding or white label use is available through a WAIT commercial agreement.
Precisely: the WAIT Local Agent 2.x development line is AGPL-3.0-only plus WAIT Section 7 additional terms, in force now. Those terms include a visible “Powered by WAIT” attribution in applicable interactive interfaces.
The attribution is not removable through a normal Community preference. Removing it is a commercial branding entitlement available through a WAIT commercial agreement.
Community remains genuinely useful. It is not forbidden to MSPs or commercial operators who comply with the license, and Apache-era 1.x users owe WAIT no fee for multi-client or commercial use of that line.
View 2.x licensing details ↗