Mission Control
The Vikstra answer to ServiceNow's AI Control Tower — built for the MCP world. Discover, observe, govern, secure, and measure every AI agent driving your ServiceNow MCP fleet, without ever sending customer records to Vikstra.
The same shape SN picked, re-scoped for MCP
Discover · Observe · Govern · Secure · Measure — same five corners, different runtime, different price, different blast radius.
Every running vikstra-mcp binary phones home with license id, app version, OS, arch, hostname-hash. Stale binaries, per-machine fingerprints and version drift surface across the customer estate.
Per-call telemetry from every binary: tool, status, duration, bytes in/out, token estimate, encoder used, policy pack + rule id, projection field count. Never tool arguments. Never response bodies.
Ed25519-signed policy bundles delivered to every binary. Built-in packs (pdi-permissive, hipaa-baseline, sox-baseline, fedramp-moderate) plus a bundle simulator that replays the last 24h/7d of traces against a draft pack before publishing.
Kill switch scoped by license, version, or machine fingerprint. Binaries pick up active orders on their next 5-minute poll and refuse new calls within ~30 seconds. Refused calls still emit a trace with status=killed.
Token + byte rollups per license, per tool, per 24h/7d/30d window. Headline: baseline-vs-actual savings %, comparing the kept-field count after Vikstra projection against the all-defaults baseline SN-native MCPs return.
Bundle → toolset → tool map. See exactly what every published pack exposes before you publish the next one. No D3 cult, no graph DB — just the truth in one viewport.
On the roadmap
Wired customer-side when we ship, not before. No invented dates.
Push every trace record as OpenTelemetry spans into your existing Datadog / Honeycomb / Langfuse / Phoenix backend. Drop-in for shops already paying for an observability platform.
Opt-in stack-trace upload for panics + recovered crashes. The admin UI buckets crash signatures so you see the same regression once instead of N times.
Binary checks the control plane for a newer signed release on startup, stages it locally, swaps on next launch. SHA-256 + Ed25519 signatures on every artefact.
Provide your $/MTok rate; the Spend console converts the token estimate into dollars so finance + engineering see the same number when planning.
Where we're different
SN AICT is the right answer for Now Assist customers governing native SN agents. Mission Control is the right answer for MCP shops who want governance without an SN platform tax.
SN AICT runs inside ServiceNow; your records and prompts traverse SN-managed infra. The Vikstra binary on the developer's machine talks directly to your SN instance — customer records never reach Vikstra. The control plane sees license keys, signed bundles and anonymous trace metadata. Nothing else.
SN AICT is effectively bundled with Now Assist behind a custom-quoted, opaque price. Vikstra works against a vanilla PDI and any paid SN instance.
We model the exact MCP tools your agents call (sn_record, sn_aggregate, sn_attachment …) and what SN tables/fields each one touches. SN AICT models agents in the abstract.
Per-call records ship as plain JSON over HTTPS; an OTLP exporter is on the roadmap so you can pipe them into Datadog, Honeycomb, Langfuse, or Phoenix. SN AICT keeps observability inside SN.
Replay the last 24h or 7d of traces against a draft pack to see exactly what would have been blocked before publishing. SN AICT ships governance as a static gate.
The Spend console computes the % of tokens Vikstra's projection actually saved versus the all-defaults baseline. Numbers backed by the recorded trace, not vendor hand-waving.
Want early access?
The MCP server primitives (trace, kill switch, signed packs) are already live. The control-plane dashboard is rolling out behind early-access licenses.