Platform health, in the open.
Real-time view of the operational health of every user-facing CreateLixir service — plus a public history of incidents and upcoming maintenance windows.
Automated live monitoring is on the roadmap. Until it lands, statuses reflect manual reporting and the Changelog. Nothing on this page is fabricated — empty states mean 'no incidents reported', not 'no data collected'.
Every service, current state.
One row per user-facing service. The list is designed to render the same regardless of state — only the pill changes.
- OperationalWebsite
createlixir.com and marketing surfaces.
- OperationalAuthentication
Sign-in, sign-up, and session management.
- OperationalPrompt Workspace
The central workspace for building software with AI.
- OperationalAI models
Foundation model routing across every enabled provider.
- OperationalProject Brain
Persistent project memory and structured knowledge.
- OperationalAI Architect
Planning intelligence and system design.
- OperationalContext Engine
Retrieval and context assembly per task.
- OperationalAI Engineering Team
Specialised AI engineers coordinating on projects.
- OperationalIntegrations
GitHub, Supabase, Stripe, and other providers.
- OperationalDeployments
Deployment Center and shipping workflows.
- OperationalAPI
Programmatic access to platform capabilities.
- OperationalDocumentation
Help center, docs, and the marketing site.
What's happened, when, and how it resolved.
Every user-affecting incident is added here — with timestamps, affected services, and every status update we posted while it was live.
No incidents reported.
When an incident happens, it appears here — with resolution, affected services, and every update we posted along the way.
Upcoming planned work.
Planned maintenance windows are posted here in advance — never surprise-scheduled — with expected duration and the services that will be affected.
No maintenance scheduled.
Planned windows appear here as soon as they're scheduled — with time, duration, and affected services.
Uptime metrics — pipeline pending.
This section is deliberately empty of numbers. We won't publish uptime percentages until real monitoring backs them.
Once automated monitoring is connected, each window below will display the measured uptime for every user-facing service — 24 hours, 7 days, 30 days, and 90 days. The layout will stay the same; only the values will change.
- Last 24 hours—Monitoring pending
- Last 7 days—Monitoring pending
- Last 30 days—Monitoring pending
- Last 90 days—Monitoring pending
Get told when something breaks.
Email subscriptions ship first. RSS, webhooks, and a Slack integration follow. Register interest below to be notified the moment subscriptions open.
Automated notifications require the monitoring pipeline to land first. Until then, we surface incidents on this page and via the Changelog — and, for large events, by direct customer communication.
- EmailFirst to ship
- RSSPlanned
- WebhooksPlanned
- SlackPlanned
Because reliability without transparency isn't reliability.
A public status page is a commitment. It says: when the platform stops behaving the way we said it would, you'll hear about it here — from us, in a place you can point at.
- Transparency
You should always know what's happening to a platform you rely on. Silence during an incident is a broken contract.
- Reliability
Availability is a product concern, not an infrastructure detail. We treat it accordingly.
- Accountability
Every incident gets a public record. Every resolution gets follow-through. No pretending nothing happened.
- Continuous improvement
Every incident is an input into how we make the next quarter better than the last.
Answers about the status page.
That the service is running as expected and no incidents are currently affecting it. Automated live monitoring is still being connected — until it lands, incidents are communicated here and through the Changelog manually.
The rest of the transparency stack.
Status shows what's happening right now. These are the surfaces that tell the story around it.
When it matters,
this is where the truth lives.
Transparency is essential to long-term trust. When something breaks, we'll say so here first — before the blog, before the email, before anywhere else.