This is the operational posture for today’s devnet deployment: honest monitoring, visible incidents, managed infrastructure, and no fake SLA promises.
The current live control points across API, gateway, and supporting services.
Gateway and API health checks are captured continuously and surfaced on the public status page.
Request logs, latency rollups, webhook failures, CSP violations, and assistant health are visible in admin and product diagnostics.
Project-level analytics, alerting, and request traces are available to authenticated teams operating real integrations.
What happens when something is degraded or broken.
Incidents are recorded explicitly and shown on the status page rather than hidden behind vague “issues” language.
Operational alerts link back to incident context when a platform-wide problem may explain project-level symptoms.
Status history is generated from service health snapshots instead of hand-written uptime claims.
Current protection mechanisms in the live stack.
Webhook retries and permanent failure tracking are built into the delivery pipeline.
API idempotency and scoped key checks reduce accidental duplicate writes and overly broad access.
Simulation mode offers a safer testing path before sending live funded request flow.
What that means in the current devnet phase.
Fyxvo currently runs managed operator infrastructure for the devnet launch.
The reliability posture is controlled and observable, but it is not yet an open mainnet marketplace claim.
The status page and admin readiness views are designed to make that distinction visible.
Why the wording stays careful today.
Devnet is useful for integration validation, funded request flow, and operational practice.
It is not a substitute for future mainnet reliability work, governance hardening, or external audit posture.
Fyxvo is explicit about current scope so teams know exactly what is live and what is still ahead.
No fake SLA claims
