Skip to main content
status.pulsehq.tech

All systems operational.

Pulse is in early access. Every public-facing component, tracked by hand. No production incident yet — when one lands, it shows here with the postmortem linked from the changelog.

manually updated · public monitoring on the roadmap

Component health

These badges reflect the team’s last review, not an automated feed. Grouped by what runs it.

product5 components

Pulse Web App

pulsehq.tech/app

Operational

Retrieval & map graph

internal · query path

Operational

Briefing delivery

scheduled jobs · 06:00 to 10:00 local

Operational

Inference · Anthropic route

no-training API terms

Operational

Inference · OpenAI route

no-training API terms

Operational
connectors3 components

Google Workspace

OAuth + sync

Operational

Slack

events + sync

Operational

GitHub

webhooks + sync

Operational
api & interfaces4 components

Public API

pulsehq.tech/api/v1

Operational

MCP Server

pulsehq.tech/api/mcp

Operational

Audit log API

GET /api/v1/audit · pull into your SIEM

Operational

Auth · SSO & SCIM

SAML · OIDC · SCIM 2.0

Operational

Recent incidents

We have not had a public production incident yet. When we do, it shows up here as a Sev-1 or Sev-2 with date, impact, time-to-resolution, and a published postmortem. We don't bury incidents.

No incidents reported. Postmortems are published if we ever have one.

No self-serve status feed yet. Ask us and we’ll tell you.

While we are in early access, tell us how you want to be reached and we will email you when a component changes state or an incident opens: detected, mitigated, resolved.