← Back to all sparks
S

StatusPal

INFRA · APIS
Velocity5.0

Hosted status pages and incident communication for SaaS teams

StatusPal Next is finishing what it started: global services now reach every surface.

status-pagesincident-managemententerprise-ssomonitoringslacknext-migration
Current state
StatusPal is shipping two changelogs side by side. Next, the rebuilt product, gets the structural work — a service model that spans containers, SCIM provisioning, monitoring check history, an onboarding flow. Classic gets narrow additions and long-tail fixes: image uploads in incident descriptions, subscriber language that survives a cancellation, an API key that reaches access groups.
Where it's heading
The Next releases read as a rollout being completed rather than features being invented. Global Services existed as a concept; this month propagated them through settings, the dashboard, subscriptions, the public page and notice forms so the model is consistent everywhere. Alongside that, the enterprise checklist is being worked through in order — SCIM after SSO, access groups over the API, Slack both as an incident-declaration path and now as a subscriber notification channel.
Prediction
With services unified and Slack wired for both operators and subscribers, the next gaps are the ones Classic still covers better and Next does not — expect continued Classic-to-Next feature transfer rather than new surfaces.

Recent moves

  1. 2d ago

    [StatusPal Next] Global Services and real-time Slack notifications

    Global Services stop being a partial concept and reach the whole product — created and managed in settings, scoped or global, visible in subscriptions, on the public page and in notice forms. Slack joins the subscriber notification channels alongside it. Both are the propagation work the Next rebuild has been building toward, not a new capability.

    View source ↗
  2. 9d ago

    [StatusPal Next] More reliable status pages, incident management, and access control

    SCIM provisioning lands for SSO organizations, syncing roles and group membership from the identity provider — the enterprise item that usually follows SSO. The rest is render and lifecycle correctness on public pages and incident cards.

    View source ↗
  3. 15d ago

    [StatusPal Classic] Image uploads and better language handling

    Classic gains image uploads in incident and template descriptions, plus a fix so a subscriber's chosen language survives cancelling a subscription. Small, but it is the kind of addition Classic still receives while Next takes the structural work.

    View source ↗
  4. 23d ago

    [StatusPal Next] Better monitoring visibility and clearer notices

    Monitoring gets down-threshold settings surfaced on the check itself and a real history of checks and results, so operators can see how a check has behaved over time rather than only its current state. Notices get display and spacing fixes across email and web.

    View source ↗
  5. 27d ago

    [StatusPal Classic] Better language handling and API access

    Subscription pages, emails and the CAPTCHA widget follow the subscriber's chosen language instead of the browser's, and organization API keys reach the access groups API like every other resource. Language handling on Classic has now been corrected twice in a month, which suggests it was a systemic fallback rather than one bug.

    View source ↗
  6. 27d ago

    [StatusPal Next] Easier onboarding

    A guided onboarding screen for new Next workspaces, with progress tracking and a streamlined Slack collaboration step. It is the earliest of the Next entries here and sets up the Slack work that arrives at the end of the month.

    View source ↗