Question 1

What does Nightglass do with our telemetry — who sees it and where does it live?

Accepted Answer

SOC 2 Type II and ISO 27001 evidence packs are available under NDA. EU tenants pin signals and postmortems to our Frankfurt region; US tenants pin to Virginia. Our full sub-processor list, plus the TLS and KMS posture, ships with the security review packet. Tenant data is never used to train shared models — every model is fine-tuned per tenant or runs against your repos only.

Question 2

How does Nightglass avoid paging on noise?

Accepted Answer

A confidence floor per service, tuned against your error budget rather than a generic static threshold. Auto-PRs only open on signals above the floor; signals under the floor still land in the audit log, they just stay off the page. The floor itself is tunable per team, not per tenant — and we never auto-page on a hypothesis we cannot defend.

Question 3

How much wiring does it take to plug Nightglass in?

Accepted Answer

GitHub or GitLab App installed per repo or group, scoped tokens, no org-wide god-mode credential. Slack, PagerDuty, and Datadog are live today; Opsgenie, GitLab, and Teams come in on the Team tier. PRs are the only side effect — no out-of-band agents, no daemon to host, two-day wiring for a mid-sized monorepo.

Question 4

What does it cost and what does it preserve?

Accepted Answer

Three tiers, all live: Starter at $25 a month, Team at $299 a month, and an Enterprise contract. The ROI frame is the cost of an incident: minutes shaved off MTTR per event, multiplied by incidents per quarter, almost always clears the monthly line item. Day-pass free trial requests go through the demo request — no card needed to look at the console.

Question 5

Will Nightglass replace the on-call?

Accepted Answer

Nightglass is the radar, not the operator. Hypothesis confirmation, customer-context lookup, and mitigation-vs-rollback decisions stay human-side. Auto-PRs draft, the on-call merges. The on-call signs off the hypothesis the desk surfaced before the page goes out — and the rollback lives in the same PR, behind the merge button, not on a separate runbook page.

The five questions buyers ask before the page goes out.

Five answers, no runaround.

Buyer objection unanswered? See pricing.