Nuvetralise Book a demo
Book a demo
Engagements · 04

Four ways we show up.

We don't sell seats. We sell finished work — a deployed collector, a quieter pager, a postmortem that doesn't read like a press release. Pick the closest fit; we'll tell you over a call if it's wrong.

01 — Collector

Edge collector, deployed and adopted

We bring our 3.4-MB Rust collector to your fleet — POPs, kiosks, RTUs, whatever you've got — and run the rollout ourselves. By week three you have telemetry coming in from every box that has ever phoned home. By week four your team owns it.

  • Provisioning script + signed firmware bundle
  • Toronto (YYZ-1) ingest, optional Montréal failover
  • Three on-site days during the rollout window
FromCAD 28k4–6 weeks
02 — Triage

Signal triage & pager diet

You have 200 alerts. We sit with your on-call rotation for two weeks, watch what they actually act on, and quietly delete the 180 that nobody reads. The remaining twenty get rewritten so the runbook fits on one screen.

  • Two weeks shadowing the rotation
  • Alert-to-action map, written in plain English
  • Per-signal cost-of-noise spreadsheet
FlatCAD 18k2 weeks
03 — Custom

Anomaly engineering, your domain

The default detectors catch what every fleet catches. The interesting bugs are domain-specific — a refrigerated truck telematics drift, a card-reader handshake quirk, a failing capacitor that announces itself only in cold-soak. We build the detector with one of your senior engineers in the room.

  • Pair-built with your subject expert
  • Streaming Python detector, runs in-platform
  • Replay harness against six months of history
FromCAD 9kper detector
04 — Coverage

On-call coverage, weeknights and stat holidays

You don't have an SRE rotation yet. Or — you do, and they'd like to sleep through Easter Monday. We pick up the pager from 19:00 ET to 07:00 ET, plus Canadian statutory holidays. Median acknowledge time last quarter: 3 minutes 41 seconds.

  • Two on-call engineers, Toronto + Vancouver
  • Quarterly handover note to your team
  • Hard escalation cap of four pages per night
RetainerCAD 11k / moquarterly
How an engagement actually goes

Week one: we shut up and read your runbooks.
Week two: we ask the questions your last vendor never asked.
Week three: we ship something small.
Week four: you decide if we keep going.

— Engagement playbook, revision 7

Things we don't do.

An honest list, in case it saves us both a call.

№ 01

Out of scopeWhite-label our platform under your brand

Ask Datadog
№ 02

Out of scopeReplace your CMDB or asset inventory

We integrate, we don't replace
№ 03

Out of scopeAnything below 500 devices in fleet size

Try Prometheus first
№ 04

Out of scopeSOC 2 audit work, GRC consulting, ISO 27001

Adjacent, not us