System status

All systems operational

Last checked: · page generated in 1200 ms

This page reflects automated probes only (configuration plus a live database read). It is not a legal SLA or uptime guarantee unless your contract says otherwise. For enterprise agreements, refer to your order form or MSA.

Components · last 90 days

Database & API
Can we reach Supabase and read core catalog data?
Operational
90 days ago300 ms latencyToday
AI agents (Anthropic)
Required to run in-app AI agent tasks.
Operational
90 days agoToday
Billing (Stripe)
Required for paid plans and checkout.
Operational
90 days agoToday
Support embeddings (OpenAI)
Optional; improves Help assistant semantic search.
Operational
90 days agoToday

Persistent historical tracking is on the roadmap. Until then each bar mirrors the current probe so the visual stays honest about what we know.

Subscribe to status updates

Pick the channel that matches how you already get on-call alerts.

  • Email

    One message when something breaks. No marketing noise.

    Email to subscribe→
  • JSON / RSS

    Machine-readable probe at /api/health for your own status board.

    Open feed→
  • SMS

    Text alerts for incidents that affect production traffic.

    Coming soon
  • Slack

    Native Slack app for status updates in your team channel.

    Coming soon

What we target (informational)

  • Availability mindset: we design for the app to be usable during your business hours; maintenance may happen off-peak with notice when practical.
  • Transparency: this page and /api/health exist so you can verify the same signal your monitors see.
  • Not covered here: third parties (Stripe, Supabase, your network) have their own status pages; a green check here does not imply all of those are green.

Recent incidents

No reportable incidents in the last 90 days. When something does go wrong we post the timeline, root cause, and remediation here within 48 hours of resolution.

Report an issue

This template is plain language. Fill it in and send it to your workspace owner or your Implementation Prosupport channel. It does not open a ticket by itself.

Implementation Pro incident report (copy and send to your admin or support)

1) Time (with timezone): 
2) Your organization / workspace name: 
3) Your email (login): 
4) What you were trying to do (1–2 sentences): 
5) What happened instead (exact error text or screenshot reference): 
6) Browser and device (e.g. Chrome on Windows, Safari on iPhone): 
7) Does it happen every time or intermittently? 
8) Link to this status page if you checked it: [paste /status URL]

Optional: Reference ID from Settings or billing if you have one.

Thank you. This structure helps us reproduce and fix issues faster.

JSON for machines: /api/health