LoginSign Up
← Back to all sparks
A

All Quiet

INFRA · APIS
Velocity7.5

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

allquiet.app ↗

All Quiet adds least-privilege API keys and Salesforce sync, signaling a push into larger security-conscious teams.

incident-managementoncallenterpriseintegrationsaccess-control
◆Current state
All Quiet is building out the integrations and access controls that enterprise incident management buyers require. Recent releases add Jira field mapping with loop-safe two-way sync, Salesforce case synchronization, scoped API keys for least-privilege agent access, and webhook rate limit visibility. These aren't feature experiments—they're the specific gaps that block deals with larger engineering organizations.
◆Where it's heading
The pattern across these releases is integration depth and access control maturity. Scoped API keys (with 403 returns for out-of-scope calls) and the Salesforce two-way sync both target the compliance and auditability requirements of enterprise buyers. Status page controls (override incident times, publish/unpublish comments) address the public communication layer, distinct from internal incident workflows.
◆Prediction
Role-based access controls and audit logging are the natural next steps after scoped API keys. The Salesforce integration will likely gain field mapping parity with the Jira integration—custom fields and status-filter controls—in subsequent releases.

◆Recent moves

  1. 13d ago

    Webhook Rate Limit Alerts and Diagnostics

    Webhook rate limit visibility surfaces HTTP 429 responses via email alerts and a 'Rate limited' badge on the integration—a practical observability addition that helps teams diagnose silently dropped webhook traffic before it causes missed alerts.

    View source ↗
  2. 16d ago

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

    Jira integration gains severity-to-priority field mapping, custom field defaults, and loop-safe two-way sync with status and label filters for incident creation. This removes the main friction point for teams that ran Jira alongside All Quiet and found the sync creating duplicate or misfired tickets.

    View source ↗
  3. 20d ago

    Publish and Unpublish Comments

    Status page comments can now be published or hidden after posting, giving incident owners control over what external stakeholders see during an ongoing incident without deleting content from the internal record.

    View source ↗
  4. 20d ago

    Override Incident Dates and Times

    Incident start/end time overrides on status pages let teams correct timelines after the fact—the override affects uptime graphs and the public timeline but leaves internal audit logs untouched, preserving the distinction between what's communicated publicly and what actually happened.

    View source ↗
  5. 22d ago

    Scoped API keys: least-privilege access for All Quiet agents

    ⚡ SPARK

    Scoped organization API keys and personal access tokens establish a proper least-privilege model for All Quiet integrations—agents now get access only to the specific resources they need, with out-of-scope calls returning 403. This is the access control primitive that enterprise security reviewers require before approving a tool.

    View source ↗
  6. 1mo ago

    Salesforce Two-Way Integration

    Salesforce two-way integration adds Case synchronization in bidirectional, inbound-only, or outbound-only modes—a direct response to the same enterprise buyer profile that pushed the Jira two-way sync to completion in the same release cycle.

    View source ↗