ACTEE (FNCCR)

ACTEE is the programme run by the FNCCR (the French federation of local authorities in charge of public utilities) that supports and funds local authorities in the energy renovation of their buildings: audits, energy manager positions, project engineering and tools.

Its digital team builds the platform on which local authorities submit and follow their applications, from the call for projects to the payment requests. Move2Cloud is responsible for managing the whole infrastructure: sovereign hosting, the delivery chain, service continuity and cost control.

Client Challenge

The platform carries the whole life cycle of a grant: application to a call for projects, review, decision, agreement, payment requests and payments. It handles the data of local authorities, their supporting documents and their bank details.

The programme is funded by energy savings certificates (CEE), a mechanism regulated by the French State. It requires full traceability of every application, and hosting located in France, subject to French and European law only.

Continuity is the second issue: a platform used by local authorities across the country cannot depend on a single host or a single site. It must be possible to bring it back up elsewhere, quickly and with recent data.

Lastly, the team is small. The solution has to leave it autonomous, with no heavy infrastructure to administer day to day.

Client Challenge

Move2Cloud Solution Approach

Responsible for the whole infrastructure, Move2Cloud runs it on two French cloud providers that complement each other: OVHcloud, where the legacy platform has moved to Kubernetes, and Scalingo, where the new platform runs with a standby on OVHcloud. Everything is described as code and driven from GitHub Actions.

ACTEE (FNCCR) — Move2Cloud Solution Approach

ACTEE (FNCCR) — Move2Cloud Solution Approach
Migration to OVHcloud Managed Kubernetes: The legacy platform, previously hosted on OVHcloud servers, now runs on managed Kubernetes clusters, on dedicated private networks in France. The switch was made one environment at a time, starting with development.
GitOps deployment with Argo CD and Helm: Argo CD deploys the API and the frontend from the Git repository, with shared Helm charts and values per environment. A single image serves every environment: configuration is injected at start-up.
A review environment per pull request: Every labelled pull request gets its own environment on the cluster, created then removed automatically by GitHub Actions and Argo CD.
FinOps: non-production off in the evening and at the weekend: Non-production environments are switched off in the evening and at the weekend, then brought back up automatically in the morning by scheduled workflows. The databases, the storage and the network stay in place: only unused compute stops being billed, a saving of about 50% on these environments.
Sovereign hosting on Scalingo: The platform is deployed on Scalingo, a French PaaS certified ISO 27001 and HDS, whose infrastructure is located in France. Data is encrypted at rest and in transit, and the team deploys without administering servers.
Separate environments: Integration, pre-production and production are isolated. Pre-production is created as a copy of production to validate a release or a fix before it goes live.
A CI/CD chain on GitHub Actions: Every change goes through a pull request: code analysis, unit and functional tests, then the build of the Docker images. A check verifies that the API contract and the interface stay in sync.
Security built into delivery: Images and source code are scanned by Trivy on every run, and the deployment branches are protected: nothing reaches production without a review.
Off-platform backups, at OVHcloud: Database backups are copied automatically to OVHcloud, a second French provider. The data therefore remains available even if the main host is unavailable.
A standby environment ready to start: A complete environment is described with Terraform on OVHcloud. Switched off in normal times, it is launched by a single workflow that creates the servers, restores the latest backup and deploys the application, in an estimated ten to fifteen minutes.

ACTEE (FNCCR) — Move2Cloud Solution Approach

ACTEE (FNCCR) — Move2Cloud Solution Approach

Conclusion

ACTEE has grant management platforms hosted in France end to end, on two independent French providers, with a platform migrated to Kubernetes and a deployment driven by Git.

The team delivers on its own, with a chain that tests and scans every release, hosting costs matched to actual use (about 50% saved outside production), and the ability to bring the service back online elsewhere should a major incident occur.

À propos de nousNous contacter

Go further

Cloud Sovereignty in Europe: SecNumCloud, AWS European Sovereign Cloud, and Choosing the Right FitCloud

Cloud Sovereignty in Europe: SecNumCloud, AWS European Sovereign Cloud, and Choosing the Right Fit

Between the arrival of AWS European Sovereign Cloud, the rise of Bleu and S3ns, and the upcoming European EUCS certification scheme, cloud sovereignty has become a central decision criterion for French CIOs. An overview of the offerings and a decision framework.

OVH Public Cloud: Getting Started Guide for DevOps TeamsCloud

OVH Public Cloud: Getting Started Guide for DevOps Teams

OVH Public Cloud offers a competitive alternative to AWS and Azure for European companies. Here is a practical guide to deploying a complete DevOps stack.

NIS2 — Becoming Compliant Before the DeadlineWhitepaper

NIS2 — Becoming Compliant Before the Deadline

A practical guide for French SMEs and mid-sized companies: who is affected, what the directive really requires, and how to structure compliance without dedicating a full-time team.