All public systems operational

Foravo is serving traffic.

This snapshot is published from the same OVH Kubernetes platform as the Foravo portal and records the latest verified public routes, runtime dependencies, backup evidence, and known residual risks.

Forge

Forgejo web, Git over HTTPS, issues, pull requests, Hovia sign-in, PostgreSQL, and Valkey-backed runtime state.

Operational

Agent API

Rust/Axum health, readiness, policy evaluation, task request, access request, and receipt endpoints.

Operational

Portal

Public entrypoint at foravo.dev and app.foravo.dev with Hovia account creation and reviewed access requests.

Operational

Backups

Hourly in-cluster PostgreSQL logical backups to OVH Object Storage, with the latest manual restore verification recorded.

Operational

Latest verified evidence

Forgejo health reports cache and database checks passing.
Forgejo uses OVH Managed PostgreSQL and OVH Managed Valkey for cache, sessions, and queues.
Forge workflow smoke passed: private repository creation, HTTPS push, clone, branch push, issue creation, and pull request creation.
Agent API readiness reports database, token, receipt signing key, and migrations configured.
Access-request events are written through the PostgreSQL outbox and processed by the worker.
Latest documented restore verification: 2026-05-17 20:45 UTC backup restored into temporary managed PostgreSQL databases.

Last static status publication: 2026-05-17 23:58 Europe/Paris. Remaining known risks are Hovia client-secret rotation, RabbitMQ replacement for PostgreSQL outbox mode, automated restore verification, and an authenticated Foravo dashboard.