Status
All systems operational.
Live readiness from the platform itself, plus how we communicate incidents.
All core services responding
Live readiness probe checked · database: ok (511ms) · decision engine: ok
The banner above auto-refreshes every minute. A dedicated status host with historical uptime + incident log is on the roadmap.
Components
- Operational
Application & dashboard
Sign-in, the studio, builder and analytics views.
- Operational
Forms runtime
Public form rendering and the hosted form pages.
- Operational
Submissions
The audited write path that accepts and stores responses.
- Operational
Public API
/api/v1/* - Bearer-token REST surface (30 endpoints, OpenAPI 3.1).
- Operational
Webhooks delivery
Signed outbound webhooks, retries and the delivery log.
- Operational
AI authoring
Draft generation and conversational refinement.
- Operational
Decision Engine sandbox
Server-side QuickJS pod that scores submissions with customer code.
- Operational
MCP server
Model Context Protocol bridge for agent integrations.
- Operational
Database
Postgres data layer, row-level security and export.
How we communicate incidents
If a component degrades or goes down, we update this page first with the affected component, what we know, and a plain-language description of impact - no jargon, no minimizing. We post follow-ups as we learn more and a clear “resolved” note when service is restored.
Severity and what to expect
- Operational - everything is working normally.
- Degraded - the component works but is slow or partially impaired; we explain what is affected.
- Outage - the component is unavailable; we post the impact and an updating ETA where we can give one honestly.
Post-incident
After a significant incident we publish a short, honest summary: what happened, the impact, and what we changed so it's less likely to recur. Uptime history and the incident log will appear here as that record accumulates.
Think something's wrong?
If you're seeing an issue that isn't reflected here, tell us at support@askery.app or via the contact page - reports help us catch partial issues faster. For how the underlying system is built, see security.