LoginSign Up
← Back to all sparks
A

All Quiet

INFRA · APIS
Velocity6.3

On-call scheduling, alerting and incident management platform for engineering teams

allquiet.app ↗

All Quiet is automating the incident ritual: war rooms, routing order, repeat-alert suppression.

incident-managementon-callchatopsintegrationsstatus-pagesapi-scoping
◆Current state
All Quiet shipped thirteen changes in twenty-five days, a dense run for an on-call product. The work clusters in three places: integrations gaining two-way sync and field-level mapping across Jira, Salesforce and Linear; status pages gaining editorial control over incident times and comment visibility; and the alerting path itself gaining snoozing of similar incidents and explicit drag-and-drop routing order. Scoped API keys and personal access tokens arrived on August 25, framed around giving agents least-privilege access.
◆Where it's heading
The direction is toward All Quiet running the incident rather than only paging about it. Dynamic incident channels open a war room in Slack, Teams or Mattermost on a severity trigger, invite whoever is on call, and archive it afterward, which is coordination work a responder used to do by hand. Routing is becoming explicit rather than incidental, with rules evaluated in an order you set instead of alphabetically. Underneath, the API is being prepared for non-human callers: scoped credentials that return 403 out of scope, published per-key rate limits, and outbound logs stripped of payload data. That credential work is parity with larger incident vendors rather than new ground, but the framing says plainly who All Quiet expects to be calling.
◆Prediction
Expect the war-room automation to grow post-incident output, a timeline or review draft assembled from the channel, since All Quiet now controls both the channel's creation and its archival. Further integrations will likely ship in the same two-way, field-mapped shape as Jira and Salesforce rather than as one-way notifications.

◆Recent moves

  1. 2d ago

    Jira Integration: Precise Field Mapping and Safer Two-Way Sync

    The Jira integration gains severity-to-priority mapping, custom field defaults, and loop-free two-way sync, with incident creation filtered by status and labels. Loop prevention is the substantive part: two-way sync between an alerting tool and a tracker is where duplicate-issue storms usually originate.

    View source ↗
  2. 6d ago

    Publish and Unpublish Comments

    Incident comments can be published or hidden on status pages after posting, with authors, owners and administrators controlling visibility. Together with editable incident times it makes the status page an editable public record rather than an append-only feed.

    View source ↗
  3. 6d ago

    Override Incident Dates and Times

    Status page incident start and end times can be overridden, and the custom times drive uptime graphs and the public timeline while internal audit logs keep the real values. It separates the public account of an outage from the recorded one, which is what teams reporting against an SLA actually need.

    View source ↗
  4. 8d ago

    Give Every Agent Least-Privilege API Access

    Organization API keys and personal access tokens can be scoped, with out-of-scope calls returning 403, on Pro and Enterprise plans. Scoped credentials are standard among larger incident vendors, so this is parity rather than new ground, but All Quiet frames it squarely around handing an agent a restricted key.

    View source ↗
  5. 19d ago

    Salesforce Two-Way Integration

    Incidents synchronize with Salesforce Cases in two-way, inbound-only or outbound-only modes. The directional modes matter more than the integration itself: they let support-led organizations decide which system holds the truth about an incident.

    View source ↗
  6. 19d ago

    Anonymize Outbound Logs

    Outbound integration activity logs can be stripped of payload data, retaining only operation, outcome and HTTP status for delivery verification. A privacy control aimed at teams whose incident payloads carry customer data into third-party systems.

    View source ↗