Grid .

[ 00 / brief ]

Grid is a managed operations service with two tracks running on a single platform and a single on-call team.

SOC — monitoring, triage, and response when something is going wrong on your endpoints, identity, network, or cloud. We watch the consoles when your team isn’t watching them, and we tell you about the things that actually matter.

NOC — availability, performance, fault prediction, and incident management for the teams running networks that can’t go down. The same operations backbone, applied to the parts of your infrastructure that move packets instead of catch attackers.

You can take one track or both. Pricing scales to what you need watched.

[ 01 / what’s covered ]

// soc — security operations

1. 24/7 monitoring — Continuous coverage of your endpoints, identity systems, network, and cloud — eyes on the consoles when yours aren’t.

2. Alert triage — Most alerts are noise. We separate the signal, kill the false positives, and only escalate the things that actually need your attention.

3. Incident response — When something real happens, we move fast: isolate it, investigate it, and walk you through containment and recovery without leaving you to figure out the next step alone.

4. Threat intelligence in context — What’s actually being used against organizations like yours, this week. Powered by our own Intel platform, enriched per-customer, no “the threat landscape is evolving” filler.

5. Monthly reporting — A short written report each month. What we saw, what we did about it, what’s trending in your environment, and what to plan for. Written for humans, not auditors.

6. On-call escalation — A real person, on a real number, when it matters. No portal queues, no offshore tier-one round-trip before someone reads what happened.

// noc — network operations

1. Availability and performance monitoring — Continuous visibility into uptime, latency, packet loss, and throughput across the network. Eyes on the pipes so you don’t have to be.

2. Fault prediction and remediation — Surface degrading links, drifting baselines, and emerging hot spots before they cascade. Where automation can fix it, automation does. Where it can’t, a human does.

3. Outage detection and coordinated response — When something breaks, we see it first and coordinate the response — including pulling the right people onto a bridge before you’ve finished pouring coffee.

4. Automated incident management — Tickets opened, updated, and routed automatically as state changes. The paper trail keeps itself; the humans do the thinking.

5. Field force optimization — For organizations with field techs: routing, dispatch, and prioritization that gets the right person to the right site without a phone tree.

6. Capacity, health, and traffic reporting — Monthly and on-demand reporting on what your network is doing. Trends, hotspots, capacity headroom. Written for engineers and decision-makers alike.

7. 24/7 escalations — A real person, on a real number, around the clock. The same on-call backbone as Grid SOC, applied to network incidents.

[ 02 / who this is for ]

• Regional businesses that are large enough to be a target and small enough that a full in-house SOC is out of reach — mostly in manufacturing, healthcare, finance, and retail.
• Public-sector organizations across the state, local, and tribal tier: school districts, municipalities, and agencies running on tight budgets against real adversaries.
• Nonprofits holding sensitive data on the people they serve, where coverage has to coexist with program spending instead of competing with it.
• IT teams who want a partner, not a takeover — you already have an IT function and you want security or network operations sitting alongside it, not a vendor angling to absorb it.
• Large institutions and ISPs, on the NOC track. Universities, hospital systems, regional ISPs, and the organizations running networks that can’t go down. We bring the operations backbone — monitoring, fault prediction, incident management, field-force coordination, around-the-clock escalation — while you keep ownership of the network.

[ 03 / how it fits ]

Grid doesn’t pretend to be the only thing running on your network, and it doesn’t pretend to be the only thing we make.

• Identity, tenancy, and access are handled by the same identity plane that runs the rest of our products. Your team logs into Grid the same way they log into Learn, Comply, or Intel — one identity, one off-boarding.
• Intel feeds Grid’s enrichment. Every alert that reaches an analyst has already been cross-referenced against our threat intelligence platform. The community feed Intel publishes is the same data we use internally; you can subscribe to it directly if you want.
• Learn closes the loop. When Grid detects a security mistake by a user — a clicked phishing link, a fumbled credential — it can hand that user a targeted training assignment in Learn. With an approval gate if you want one, without if you don’t.
• Comply hands gaps to Grid. If you also run Comply, posture changes in your M365 or Workspace tenant can land in Grid as cases. Drift becomes work.
• Cortex assists, doesn’t decide. Alert summaries and first-pass enrichment are AI-assisted on our hardware. The escalation call is always a human’s.

[ 04 / where we are ]

Grid is live and accepting customers. The platform has been running in production against our own workloads — catching real things before it ever sees a customer alert. Charter customers are being onboarded now; the customer portal and self-service controls are next on the roadmap.

We’re standing it up in our own region first. Local organizations, public sector entities, nonprofits, regional businesses — the teams that have been priced out of operations support for years. Once it’s solid here, we go wider.

Early access means real terms, not a waitlist. If you’re a fit, we’ll talk scope, pricing, and timing now — and the first cohort gets a seat at the table on what Grid becomes.