Choose the NOC purchase
Six companies and eight NOC purchases, listed alphabetically. Benchmark365 plans retain separate allowances. Open a purchase for dated terms, its RFP and brief.
Benchmark365 / 3 NOC purchases
The NOC page lists Auvik alongside its three work-allowance plans. NOC network-monitoring tool list / 2026-10-21 (external website)
NOC Launch
Price and charging basis: USD 990/month starting price. Includes 3 customer environments and 10 investigations per month, with email intake. Endpoint, user and ticket intake is advertised as unlimited; completed work is capped by the plan allowances. NOC plans / 2026-10-17 (external website)
Read provider details / RFP for this service / Download service brief
NOC Connect
Price and charging basis: USD 2,990/month starting price. Includes 10 customer environments, 25 investigations and 10 remediations per month, plus live two-way PSA integration. Major Incident Response is an add-on; unlimited tickets do not mean unlimited completed work. NOC plans / 2026-10-17 (external website)
Read provider details / RFP for this service / Download service brief
NOC Enterprise
Price and charging basis: USD 9,990/month starting price for customized scope, with unlimited approved customer environments. The page lists contractual SLA alignment, compliance agreements and a named-resources option; investigation and remediation quantities need a written scope. NOC plans / 2026-10-17 (external website)
Read provider details / RFP for this service / Download service brief
Ask in the proposal: Which Auvik-to-ticket intake is included in this plan? How do related sites, duplicate events and extra investigations or remediations count against its allowance?
Flexis IT / MANAGE - shared NOC remediation
The MANAGE NOC FAQ lists Auvik. MANAGE RMM and PSA list / 2026-11-06 (external website)
MANAGE - shared NOC remediation
Purchased work model: MANAGE is a shared NOC providing monitoring, troubleshooting and remediation. Scope, permitted changes and retained escalation duties belong in the order. MANAGE shared NOC and FAQ / 2026-11-06 (external website)
Read provider details / RFP for this service / Download service brief
Ask in the proposal: Which collector-health and network-triage duties are included in MANAGE? Identify the PSA destination, permitted network actions and accepting owner if ticket delivery fails.
HEX64 / MSP NOC offer
The MSP NOC tools list includes Auvik; the separate Care packages have their own scope. Source / 2026-11-06 (external website)
MSP NOC offer
Read provider details / RFP for this service / Download service brief
Ask in the proposal: Which Auvik Network Management tasks belong in the MSP NOC order? Identify the receiving ticket and network-change approval; keep Help Desk and Care work on their own schedules.
LTVplus / Managed NOC - NOC seat
The managed NOC page includes Auvik in the MSP tool stack. Managed NOC service / 2026-10-18 (external website)
Managed NOC - NOC seat
Price and charging basis: The advertised starting figure is $3,000 per NOC seat/month. Confirm required staffed seats, billing currency and the invoice calendar. General terms describe four-week billing, so obtain the controlling order before calculating a yearly total. Managed NOC service / 2026-10-18 (external website) Public terms dated 13 August 2026 / 2026-10-18 (external website)
Read provider details / RFP for this service / Download service brief
Ask in the proposal: What Auvik work does the quoted NOC seat own, and who supervises or accepts escalations? Agree collector, ticket and permitted-action duties alongside the staffing and coverage arrangement.
NOC 24/7 / Managed MSP NOC
The NOC service page names Auvik in its supported-tool sections. Detailed RMM / PSA sections / 2026-10-15 (external website)
Managed MSP NOC
Price and charging basis: Per endpoint per month; no numeric rate is shown on the reviewed pricing page. Source / 2026-10-15 (external website)
Read provider details / RFP for this service / Download service brief
Ask in the proposal: Which sites, operator role and notification associations are included? Demonstrate the receiving PSA owner and list network actions requiring approval.
Worksent / MSP NOC
The NOC service information lists Auvik alongside Standard and Premium work plans. NOC service page / 2026-10-15 (external website)
MSP NOC
Choose the work plan: Both Worksent NOC plans list continuous monitoring, alert triage/remediation, patching, AV/EDR administration and daily summaries. The Standard plan marks RMM consulting, backup checks and vendor coordination as excluded; Premium marks them included. Select the plan in the order, separately from shared or exclusively assigned POD staffing. Define the permitted changes, backup-check result and vendor handoff; plan ticks alone do not establish restore validation or security incident response. NOC Standard/Premium plan table / 2026-10-20 (external website)
Read provider details / RFP for this service / Download service brief
Ask in the proposal: Which Standard or Premium tasks and POD assignment are quoted? Identify who handles collector or ticket failures requiring vendor coordination, and any work priced separately.
Use this guide for an Auvik Network Management workflow. Ask each candidate to name the product, deployed collector type and included operations in its quote, then carry the selected service into the RFP.
Assign the collector and site owner
Auvik's collector introduction (external website) describes collection of network information and delivery to its cloud service. Identify the collector type and deployment actually proposed for your account. Assign someone to a collection problem as well as to the device events it normally produces.
| Boundary | Put in the proposed scope | Keep with the proposal |
|---|---|---|
| Collector and host | Who maintains the collector, its host and connectivity; who accepts a collection-health incident | Collector reference, responsible team and escalation contact |
| Client and site reach | Which approved sites and network entities the team may see and manage | Site inventory and a demonstration using the proposed operator identity |
| Shared dependency | Which sites use the same collector, and who lists the affected sites when it is unavailable | Collector-to-site map and an accepting incident owner |
| Device work | Which observations, configuration checks and approved changes are purchased | Task list, approval path and completion evidence |
Keep the collector dependency beside the client/site inventory during onboarding. For the cutover and rollback owners, use the transition guide.
Review the proposed operator role
Auvik's role documentation (external website) separates permission areas for collectors and integrations, device access, documentation and audit, discovery and credentials, alerts and API operations. Have the candidate show the actual role together with its assigned clients and sites.
Write down the decisions separately:
- Who can inspect device and configuration information, and what the NOC needs for investigation.
- Who can use remote-management functions or make an approved network change.
- Who can alter discovery, credentials, alert definitions, notification channels or maintenance windows.
- Which API identity is used for an integration, who maintains it and which history remains available to your team.
Retain approval for actions outside the purchased task list. A demonstration should include an allowed task and the handoff for an action that requires your authorization. Name the approving owner before the bounded NOC pilot.
Check the actual notification destinations
Auvik's notification-channel inheritance documentation (external website) distinguishes channel configuration from alert-definition configuration. A customized child-site or alert channel list needs its own review when root channels change.
Have the proposed operator inspect the channel list for each critical site and alert, including any site association on the channel. Keep the intended recipient, PSA destination and configuration owner in the handover log. Check those associations directly instead of inferring delivery from a changed threshold.
Agree who maintains site-specific exceptions after onboarding. Include the receiving queue and the fallback contact for a delivery failure in the integration worksheet.
Count the shared incident and the work
Auvik's shared-collector guidance (external website) describes an Alerts v2 option that sends a shared-collector disconnection notification at the parent multi-site. Its October 5 release note (external website) distinguishes the default for new customers from the choice in an existing alert definition. Ask which behavior is configured in the deployment you are handing over.
Agree how the receiving team identifies every affected site, groups related tickets and identifies the collector incident. Also check for equivalent legacy and Alerts v2 definitions using the same notification route.
Take that incident record into the commercial discussion. Ask whether the supplier counts an investigation or remediation once, per site or under another agreed rule. Reconcile the included allowance, duplicate handling and chargeable extra work against the selected NOC quote. Keep the configured alert delay and the NOC's contractual acknowledgement or action target as separate definitions.
Follow an event into an accepting PSA owner
Auvik's external-ticket troubleshooting guide (external website) separates the alert event, notification channel and receiving-system mapping. Use those checkpoints when agreeing the proposed workflow:
- Identify the expected site, entity and alert definition, including legacy or Alerts v2.
- Review the applicable notification channel and its site association.
- Check the receiving PSA company/site, queue or board, priority and required fields.
- Find the resulting ticket reference and the team accepting responsibility for it.
- Agree how failed delivery, repeated events, clearance and an open handback remain assigned.
Ask for a channel-delivery check and a separately authorized end-to-end case. Log the results against the expected workflow. Select the current agreement's acknowledgement, work-start, mitigation, restoration and resolution definitions in the SLA comparison.
Agree six bounded pilot cases
Use these as proposed cases for an approved test setting or agreed rehearsal. Set the scope, expected outcome, owner and stop condition in advance. Keep first attempts and retests in the existing NOC pilot case log.
| Proposed case | Agree the expected result | Include in the case log |
|---|---|---|
| Shared collector becomes unavailable in an authorized rehearsal | The nominated owner receives the intended collector incident and can identify affected sites | Collector/site references, delivery log and accepting owner |
| A child site has an intentional channel exception | Its approved recipient and destination remain identifiable alongside the root configuration | Reviewed channel lists and a safe delivery-check reference |
| An alert cannot create the test PSA ticket | The failed handoff stays assigned; the team identifies the failed mapping or delivery stage | Alert reference, site, rejected destination, timestamps and failure owner |
| Equivalent legacy and Alerts v2 events reach the test workflow | The team handles the agreed duplicate pattern and logs the related work consistently | Event source, related ticket references and agreed billing treatment |
| A requested network action exceeds the NOC's approved scope | The team obtains the required approval or escalates to the named retained owner | Request, permitted scope, approval decision and handback reference |
| A test operator is removed at the end of the pilot | Access ends for the intended identity while your team retains the agreed incident and audit records | Access-review result, retained log locations and successor owner |
For the client boundary, use approved test identities and synthetic or authorized client data. Choose test conditions that preserve production service; retain the original alert/channel configuration and the agreed rollback owner.
Keep the handover material when the service changes
Include collector and channel ownership, operator identities, site assignments, open tickets and retained history in the exit plan. Identify who accepts those duties before changing access or ending the supplier's coverage. Keep the original proposal, the selected service brief and the accepted workflow case log together.