StatusPulse StatusPulse
Product ▾
Features Detection, status pages, incidents, notifications, reports Probes HTTP, SSL, DNS, gRPC, WebSocket, Database, mail, and more AI agents & MCP Run pages and incidents from Claude Code, Cursor or VS Code
Pricing
Resources ▾
Guides How to monitor HTTP, databases, gRPC, email, cron jobs and more Changelog Everything shipped, dated Blog Notes on uptime, incidents and status pages
Contact Status SSO Login
← Back to home |

Security

How we protect your data.

StatusPulse is built on Microsoft Azure. All customer data is stored in one Azure SQL database in Azure West Europe, and the web app and status pages run there too. This page will expand into a full security posture document before public launch — covering data encryption, access controls, incident response, and sub-processors.

Today, in beta

  • All traffic over HTTPS with HSTS enforced
  • Authentication via Microsoft Entra External ID (CIAM)
  • Data encrypted at rest (Azure SQL TDE)
  • IP addresses stored only as salted hashes

StatusPulse

Uptime monitoring and status pages.

Latest update: 5 Nov 2026 — Short videos of the product at work

Compare

  • vs Statuspage.io
  • vs Uptime Kuma
  • vs UptimeRobot
  • vs BetterStack
  • vs Pingdom
  • All comparisons →

Features

  • AI agents & MCP
  • Probes
  • Status pages
  • Incidents & alerts
  • Anomaly detection
  • Outbound webhooks
  • All features →
  • Probe types →

Resources

  • Guides
  • Changelog
  • Blog
  • Status
  • Pricing
  • Contact
© 2026 StatusPulse by 3D Tesla · Built and answered by Marcelo Jarretta
Privacy · Terms · Security · GDPR