This transformation is taking place within a context of cost reduction, rationalization of existing infrastructures, and the pooling of IT resources.

In this constrained environment, the question is not only which provider or technology to choose, but which application execution model is best suited to the project at hand. PaaS (Platform as a Service) is one of the available options, provided its benefits, limitations, and applicable frameworks are clearly understood.

Challenges and issues specific to the public sector

Public organizations face structural constraints that directly influence their technical decisions. Budget pressure is constant, with explicit objectives to control or even reduce IT operating costs. Technical teams are often understaffed, with recruitment challenges for specialized roles such as system administrators, developers, cybersecurity experts, and cloud or DevOps engineers.

In addition, public organizations often rely on a heterogeneous and sometimes aging application landscape, built on technologies or environments that are no longer maintained or are difficult to evolve. Security, availability, and regulatory compliance requirements are high, while project timelines must remain aligned with the operational needs of administrations, local authorities, and public institutions.

How PaaS can address these challenges in the public sector

Using a cloud platform can address part of these challenges, without being a universal solution. One of its main benefits is the reduction of operational workload. In practice, this means that operating systems, application runtimes, deployment processes, restarts, and monitoring mechanisms are managed at the platform level. Technical teams no longer need to handle day-to-day infrastructure management and can focus on developing, improving, and maintaining applications.

From a security and update perspective, an application hosting solution also helps maintain technical environments more consistently up to date. In the public sector, where legacy management is a key concern, this reduces risks associated with obsolete systems, unmaintained dependencies, and delayed security patching. While this approach does not eliminate existing legacy systems, it helps structure their operation and supports gradual modernization without requiring a full overhaul of the information system.

In this context, a PaaS for public services can be a relevant lever, provided it is selected for clearly identified use cases.

Not all public projects fall under the same deployment framework

Public sector digital projects vary widely. An internal business application, a citizen-facing digital service, a data platform, or a research project do not involve the same constraints or levels of requirements.

Some contexts, particularly those related to defense or the processing of sensitive information, require enhanced guarantees in terms of security, control, and sovereignty. In such cases, specific qualification frameworks such as SecNumCloud may be required, limiting the available technical options. PaaS is therefore not suitable for all scenarios, and its use must be assessed based on data sensitivity and applicable regulatory requirements.

Existing public frameworks for deploying PaaS

Contrary to common belief, public sector organizations already have operational frameworks to access compliant cloud and application hosting services.

For administrations and public institutions, using UGAP provides access to a national purchasing body with pooled and legally secure contracts.

At a regional level, initiatives such as La Fabrique IA Territoriale, led by GIGALIS, offer local authorities and institutions in the Pays de la Loire region a structured framework to access digital and cloud services, with a focus on mutualization and support.

In the healthcare sector, hospitals can rely on Resah, which references solutions tailored to the specific requirements of healthcare environments.

These frameworks do not define technical use cases but provide concrete access points to services compliant with public procurement regulations.

When PaaS is particularly relevant

A managed cloud model is especially well suited when the goal is to build a new application without the need to handle system administration. It is also relevant for modernizing or refactoring existing applications, where the main objective is to simplify operations while improving reliability and security.

For application projects requiring fast deployment cycles, better cost predictability, and reduced administrative overhead, a cloud offering for public sector organizations can be a consistent choice, provided the functional and regulatory scope is clearly defined.

Key considerations before making this choice

Before choosing a PaaS, several factors must be carefully evaluated: the actual scope of platform responsibility, reversibility conditions, data location and protection, and alignment between data sensitivity and the guarantees provided. These elements determine whether the model is appropriate and sustainable over time.

Are you working on an application project within a public service and wondering whether a PaaS model is relevant in your context?

Identifying the right contractual framework helps save time and ensures compliance with public sector digital projects.

Or access Clever Cloud directly via public platforms:
UGAP for administrations and public institutions, La Fabrique IA Territoriale for organizations in the Pays de la Loire region, and Resah for healthcare institutions.

At the same time, in its  summary published earlier this year, the cybersecurity body CERT-FR, operated by the French National Cybersecurity Agency (ANSSI), reports that 218 cyber incidents were handled in 2024 involving local authorities. In its 2024 activity report,
ANSSI also describes the cyber threat as “systemic” for the public and social sectors.

In this context, choosing a secure cloud solution for public administrations has become a central concern for CIOs, CISOs, and digital project managers.

The objective is not simply to select a high-performance infrastructure, but to ensure that the chosen cloud solution meets the legal, regulatory, technical, and operational requirements specific to the public sector.

Understanding what cloud security means in the public sector

The data handled by public administrations — personal data, health data, financial information, and sensitive data related to public infrastructures — are subject to strict regulatory frameworks, notably enforced by the CNIL and the GDPR. In addition, the public sector is expected to rely on recognised security certifications, such as ISO/IEC 27001, HDS for health data, and, for the most critical environments, SecNumCloud.

These requirements demonstrate that a secure cloud goes far beyond firewalls or encryption alone. It requires a comprehensive, structured, and auditable approach to security.

Digital sovereignty: a criterion that has become essential

For a public administration, it is essential to know where data is hosted and under which jurisdiction it falls, in order to comply with the GDPR and to properly govern any potential data transfers outside the European Union.

A sovereign cloud implies not only that data is hosted within the European Union, but also that it is not subject to extraterritorial legislation, such as the US Cloud Act (2018), which allows a foreign government to request access to data stored by a provider under its jurisdiction.

Digital sovereignty also contributes to the resilience of information systems. By limiting technical, contractual, or legal dependencies on a single provider, public administrations retain the ability to react quickly when constraints arise—for example, by changing providers or relocating a service when regulatory, operational, or strategic conditions require it. This margin of manoeuvre is an important factor in maintaining control and ensuring the long-term sustainability of public digital services.

Sovereignty is therefore a key differentiating criterion when choosing between a European provider and a US-based provider.

Beyond compliance: essential technical requirements

To ensure a level of security appropriate for the public sector, a cloud solution must provide strong isolation between environments, systematic encryption of data in transit and at rest, host hardening, as well as continuous monitoring mechanisms (logs, metrics, alerts).

Identity and access management (IAM), multi-factor authentication, and the application of the principle of least privilege are part of a Zero Trust approach, now recommended by ANSSI to reduce the attack surface.

Security also relies on operational resilience: service continuity, recovery capabilities, high availability, and fault-tolerant architectures.

The role of automation in risk reduction

Automation is often seen as a convenience for developers; in the public sector, it is above all a lever for reducing human-related risks.

Automated deployments, automatic scalability, and self-healing mechanisms help limit operational errors, which account for a significant proportion of security incidents.

By reducing the number of manual operations, organisations lower the risk of misconfiguration and improve the overall availability of services.

Total cost of ownership and governance

Choosing a secure cloud is not just a matter of comparing list prices.

Public sector organisations must take into account the notion of total cost of ownership (TCO):

• Infrastructure costs,
• Internal staffing costs,
• Operational complexity,
• Maintenance,
• Time spent handling incidents,
• Effort required to migrate a service or ensure its reversibility.

A platform that automates most operational tasks and enables reproducible environments can significantly reduce internal workload, and therefore the overall cost.

How to objectively assess market solutions

To evaluate a cloud solution intended for the public sector, it is essential to rely on factual criteria: the level of sovereignty, available certifications, technical capabilities, reversibility, the availability of private cloud or on-premise options, the existence of air-gapped environments, the quality of support, and compatibility with existing tools.

The most common mistakes include choosing a provider out of habit, focusing solely on price, or confusing data localisation with legal sovereignty.

Another recurring mistake is overestimating the complexity of migration. In many cases, a test or a Proof of Concept is sufficient to validate feasibility.

A simple method for choosing the right cloud solution

The most effective approach consists in:

This approach provides a balanced view of security, compliance, performance, and sustainability.

What Clever Cloud brings to these challenges

Clever Cloud is a European hosting provider certified ISO/IEC 27001:2022 and HDS, offering public cloud, private cloud, on-premise and air-gapped environments. For highly regulated requirements, a zone already qualified SecNumCloud is available on request through our partnership with Cloud Temple. This makes it possible to meet “trusted cloud” requirements while benefiting from the Clever Cloud platform.

The platform follows a security-by-design approach based on environment isolation, system hardening, strong authentication, and built-in observability.

Automated deployments, automatic scaling (auto-scaling), and self-healing mechanisms reduce operational effort and limit human error.

Data remains hosted in Europe, and data portability is ensured, with no proprietary lock-in.

Support is human-led and provided from France.

Finally, for public organisations that rely on pooled public procurement frameworks, it is worth noting that Clever Cloud is listed on the “Nuage Public” (UGAP) framework. Public administrations can therefore subscribe to our services within an already validated public purchasing framework, simplifying administrative procedures and accelerating service deployment.

Towards a secure, sovereign, and sustainable public cloud

For a public administration, choosing a secure cloud solution means finding the right balance between sovereignty, compliance, technical security, productivity, and cost control.

By relying on clear criteria and official reference frameworks (ANSSI, ISO, GDPR, HDS), it becomes possible to select a solution genuinely suited to the needs of the public sector—one that can ensure both service continuity and the protection of citizens’ data.

Would you like to evaluate a sovereign and automated cloud platform?

Contact us

Somewhat paradoxically, the biggest change of the past few months is also the least visible from the outside: the strengthening of our “Clever Cloud Everywhere” approach.

An open cloud platform that adapts anywhere, to your needs

Because we are more than a PaaS provider with our own infrastructures,we offer our customers the ability to deploy their applications and services with our partners (Cloud Temple, Ionos, OVHcloud, Scaleway, etc.), or even on their own servers, for use cases ranging from edge deployments (local machines) to fully air-gapped environments (disconnected from the Internet).

So, you don’t have to adapt to the constraints of our cloud, the opposite is true. In 2025, a growing number of customers asked us for fine-grained adjustments to fit their needs, which we are always happy to provide. As a result, if you want your own Clever Cloud, that’s entirely possible: we can supply partner hardware or install our platform on infrastructure you already have. This is precisely how we operate outside of Paris.

Moreover, after opening a zone in London and establishing partnerships in West Africa and Kazakhstan, we have also announced our new Moroccan subsidiary. At the same time, we continue to strengthen our local presence, through our integration into the Fabrique IA Territoriale in Pays de la Loire, our support for startups via the UP Program, and our partnership with the German company SpiNNcloud to build a European computing platform for AI.

Kubernetes at Clever Cloud

Another major milestone reached by our teams is the launch of Clever Kubernetes Engine (CKE), our managed Kubernetes offering. It is currently available to a limited number of customers who are actively using it, and can already be accessed through our API, Clever Tools, and the Console. It will be opened more broadly in the coming weeks.

Two new points of presence in Paris

This expansion of our services goes hand in hand with an expansion of our infrastructure, as we move from 3 to 5 datacenters in the Paris region. We have begun our deployment both in Vélizy with our partner Etix and by strengthening our partnership with TeleHouse through a presence at TH3 (Magny).

This will enable us to meet our customers’ growing needs while preparing the introduction of new services, such as our forthcoming Infrastructure-as-a-Service (IaaS) offering, which you should hear more about next year.

Are you Clever Cloud certified?

2025 was also the year we launched our first certification program, which had been highly requested by several of our customers and partners. This first step was accompanied by the continued strengthening of our sales team over the past few months.

A second, intermediate-level course is arriving very soon. This will allow us to better support you on a daily basis and take the time to address your needs, while multiplying workshops and training sessions—both in person, via webinars and through live streams on YouTube and Twitch. Next step: Clever Cloud ambassadors!

Continuous improvement of our offering

Naturally, we have continued to improve our long-standing PaaS solution by releasing new images and features every week. Integration has become faster as well, with updates such as Node.js 24 and Java 25 now supported, along with improved compatibility for pnpm and Yarn alongside Bun. .NET 10 and PHP 8.5 are next in line.

We are also gradually shortening update cycles for several database services. As a result, PostgreSQL 18 is already available, and Redis 8.4 as well as Elasticsearch 9 are on the way.

In addition, we have kept strengthening the managed services we offer across the platform, including Keycloak, Matomo, Metabase, and Otoroshi. All of them are now available in their latest versions, with the ability to manage updates at creation time and from the Console dashboard, as well as to enable advanced features when needed.

Thus, we introduced Secure Multi Instances in Keycloak a few months ago, leveraging our Network Groups. These groups can also be enabled in a single click within the Otoroshi API Gateway to connect multiple applications. Otoroshi now also supports loading third-party plugins and configuring domains at creation time.

Other services continue to evolve as well. For example, Materia KV is now available in beta and will keep improving ahead of its planned general availability early next year. Similarly, Apache Pulsar will reach the same milestone soon, with updated pricing to accompany the release.

Our offering is also becoming increasingly accessible through a tool we significantly strengthened this year to support some of our customers’ needs: our provider Terraform. After reaching version 1.0 this summer, it is now available as version 1.7.1,providing a wide range of capabilities. Feel free to try it out and share your feedback and suggestions.

Clever Tools and Console evolve, the revolution in 2026

Clever Tools can now be executed via npx, support the new drains, and have gained numerous features over the past months. We began a major redesign with version 4.0, released last September. And this work will continue throughout 2026.

In the Console, we recently rolled out our new interface for access logs, with add-on logs coming next. We will progressively extend the new dashboards to all our services, then integrate Network Groups and introduce a native management interface for our object storage solution, Cellar.

But the most significant shift has been the deeper redesign of the Console itself. This work comes alongside new APIs aimed at modernising the platform and the services it provides, with the same goal as always: making developers’ lives easier.

Such progress are supported by foundational work carried out quietly throughout the year: the complete overhaul of our JavaScript client. Easier to use, more complete, type-safe, and managing API Tokens, it will serve as the basis for several upcoming initiatives we will announce soon.

Want to know more? Join us at ACCES!

As you can see, 2025 has been a year full of updates and significant changes for Clever Cloud and our team. And 2026 is set to follow the same trajectory. To see what’s coming next, feel free to join us at the Amazing Clever Cloud Enterprise Summit (ACCES) taking place on Thursday, 11 December 2025 during FOST (formerly apidays), which will take place from 9 to 11 December. We will host a pavilion with several of our clients and partners to showcase what we are preparing for the months ahead — from Clever IA to Materia TS to our KMS.

The protection of health data now concerns many sectors of activity. Software publishers, healthcare establishments, public services, laboratories… More and more players need to guarantee secure hosting for this sensitive data.

Ready to secure and optimise your data hosting? Contact our teams to find out more!

Make an appointment now!

Understanding Health Data Hosting ("Hébergement des Données de Santé" - HDS) cloud certification

What is health data?

Any information that makes it possible to identify a person and learn about their state of health, whether physical or mental, is health data (information collected during medical monitoring, results of medical examinations, information relating to an illness, allergy, treatment or disability, etc.).

What is HDS certification?

HDS (Health Data Hosting) certification aims to enhance the security and confidentiality of personal health data, thereby guaranteeing a trusted environment for e-health and patient monitoring. To meet these high standards, it is based on ISO-compliant standards and the RGPD. Issued by an accredited independent body, it covers six areas of activity: the provision and maintenance in operational and security conditions of physical sites, the hardware infrastructure, the virtual infrastructure, the platform for hosting IS applications processing personal health data, as well as the administration and operation of the IS and the backup of personal health data.

Why choose an HDS cloud?

A legal obligation for players in the healthcare sector

All players (public or private) who host, use or store health data for a third party (with the exception of IT archiving services, which are not affected by these obligations) must be HDS-certified. Only health establishments that manage their own information systems are exempt (L.1111-8 of the Public Health Code).

Data security and confidentiality

Unlike an on-premise infrastructure, where the company would have to manage data hosting, operation and security itself, a Platform as a Service HDS cloud like Clever Cloud enables these critical aspects to be automated. This guarantees rapid deployment, automatic scalability, one-click database control, advanced security (encryption, service continuity, anonymisation) and effortless maintenance, all in a certified way.

By choosing an HDS cloud, you can concentrate on your core business, while ensuring that your infrastructure complies with the highest standards of healthcare data protection.

Rely on Clever Cloud for HDS hosting of your sensitive data

Contact our teams!

Our main goal is to offer our users a tool that's easy to handle, makes their lives easier, and can be used in scripts as a complement to our API and Console. In 2023, we decided to rework this open source project to give it a new impulse. Here's a report on our first year's work.

v3: the foundations for renewal

We started out from an observation: our CLI had not evolved much for two years. Of course, we had released a few updates and beta versions, but nothing more.

Yet a tool like Clever Tools is used on a daily basis by our customers, and is vital in the progress of our offering. Based on our public API, it enables us to deliver new services easily and quickly, so that our customers can use them in a wide range of situations.

As we prepared to make major changes to Clever Cloud, Clever Tools had to reflect this evolution. Capitalizing on our teams' growth, Hubert Sablonnière, in charge of the “Front” and lead developer of the project at the time, launched an initiative to integrate new contributors and organize regular exchanges on its progress.

Release of Clever Tools 3.0 at the end of 2023 was an initial turning point. More than just a technical upgrade to Node.js 18, this version paved the way for a more powerful, easy-to-use CLI. Its distribution mode has been entirely reworked to facilitate releases, but also to avoid alpha/beta channels: each PR leads to the creation of test binaries.

Our new log stack appeared first in Clever Tools, with text and date/duration search capabilities, improved formatting and more. Above all, this release set the scene for all the enhancements we were planning for 2024.

Streamlined management

In 2024, we introduced some long-awaited features to simplify your day-to-day operations. In small ways, such as updating zones in auto-completion, no longer having to provide a name when creating an application, Clever Tasks creation, displaying useful information at various places. But we've also adopted new paradigms.

The best example is probably the introduction and generalization of the --app option to commands linked to applications in our “Big Summer Update”. Until last July, you had to “link” a Clever Cloud application to a local folder to control it. Since release 3.8.0, this is no longer necessary. You can, for example, clever ssh or clever restart any application simply by specifying its name or ID. It was also at this time that we introduced a command to list all the applications an account has access to, by organization (clever applications list).

We've done the same with the --format/-F option, generalized to as many commands as possible, to provide classic output by default but to be able to request a JSON formatted result, which can be handy in scripts/CI or for passing to tools such as jq/jless. Sometimes we've also introduced specific formats, such as json-stream for (access) logs, or shell for some commands linked to environment variables.

An open project that evolves to fit your needs

Providing greater flexibility of use was another of our concerns this year. Here, one of the best examples is probably the official integration of the clever curl command, which lets you make requests to our API in the context of the current user. This has been accompanied by enhanced context-sensitive help. At the same time, we revamped the Clever Tools documentation.

It is also through our CLI that we have introduced features enabling us to respond to customer needs, such as the ability to add plugins as soon as an Elasticsearch add-on is created. With release 3.11 which went live yesterday, we've introduced a feature flags system that takes over from the old alpha/beta channels. This gives us greater flexibility in the deployment of new features, allowing us to test and refine them according to your feedback. So don't hesitate to share your needs, ideas and comments with us, through issues on the project or even by contributing to it.

# We create a Materia KV add-on
clever addon create kv myMateriaKV

# Then we use it instantly with the experimental clever kv command
clever features enable kv
clever kv myMateriaKV PING

# We write data, instantly replicated over 3 data centers in Paris
clever kv myMateriaKV SET myKey myValue
clever kv myMateriaKV GET myKey

The beginning of a technical overhaul, a more didactic approach

Clever Tools follow our evolution, with the introduction of token expiration dates ( displayed in clever profile), and support for the many add-ons launched this year: Keycloak, Materia KV, Metabase, Otoroshi with LLM, etc.

The latter were also an opportunity for us to pursue the didactic approach introduced around clever curl, adding instructions following the creation of an add-on. Our aim here is to support our customers in the use of new services and tools, with increasing references to useful information and cross-references to our documentation.

But also diagnostic commands such as clever domain diag, which lets you check whether application's DNS are correctly configured. Its addition was accompanied by the clever domain overview command, which lists all the domains and paths linked to your various applications.

On the road to v4, a continuous improvement

We spent part of the summer cleaning up the code under the hood. We migrated to EcmaScript Modules (ESM) with the introduction of a bundling step. All this has given us a more modern and maintainable code base, paving the way for future developments in Clever Tools architecture.

2025 promises to be just as rich in new features, with the imminent arrival of release 4.0. It will mark the transition to Node 22, introduce a new self-packaging build system and continue to improve the user experience. We will also soon add access to Network Groups with the experimental clever ng command.

The focus will be on improved ergonomics, new functionalities and, above all, a complete overhaul of commands naming and organization, which will be introduced progressively. Documentation generation will be automated and releases scheduled on a regular basis. All this will be made possible by a major upgrade of the Clever Tools technical stack.

This new phase reflects our ongoing commitment to provide you with a reliable, efficient tool tailored to your needs. Beyond the technical features, it's the collaboration with our community that guides the evolution of Clever Tools. The changes made since 2023 are just the beginning of a new era for your deployment CLI.

Check back in a few weeks to start discovering all the possibilities version 4 has to offer. Don't forget to follow our changelog to be informed of the latest developments.

To address these needs, we teamed up with Mathieu Ancelin, creator and core developer of Otoroshi and API Management expert who founded Cloud APIM, to integrate Otoroshi with LLM on Clever Cloud. This add-on is now available in beta to all our users. Shipped with a ready-to-use configuration and an intuitive interface, it simplifies the implementation of advanced AI workflows and offers centralized management of your APIs, WAF, etc.

• Learn more about Otoroshi
• Learn more about Otoroshi with LLM on Clever Cloud
• Video tutorials of Otoroshi with LLM extension

Providing AI services beyond the hype

At Clever Cloud, our mission is not limited to deploying applications and add-ons. We were founded on a desire to simplify developer's life, and to provide them with services that extend beyond our turnkey deployment solution. Our main focus is to understand the needs of our customers on a daily basis, with a single obsession: to find the best way to meet them, in the best possible way. In the emerging field of AI as elsewhere.

And while we can see how much artificial intelligence has already changed our businesses, and how quickly things are evolving, we have a duty not to simply jump on the latest fashionable feature and jump from trend to trend to make headlines.

Over the last few months, we've been looking at how we can contribute to a challenge that seems essential to us: adapting AI to the specific contexts and needs of businesses, not for one service, but for an entire ecosystem.

That's why we've worked to identify robust tools for your teams: centralized rights and billing management, integrations, observability, auditability, resilience, and much more. With Otoroshi with LLM, we offer much more than an API gateway: a turnkey service to manage your APIs and maximize the potential of your AI interactions.

And as usual, we don't just provide a “1-click” open source deployment, our approach is to integrate professional tools that are truly adapted to everyday use, with real lifecycle management. Otoroshi with LLM, as an add-on to our Marketplace, takes full advantage of our platform: scalability, simplified updates, secure integrations and unified payment.

LLM extension: your single point of entry for artificial intelligence

With its LLM extension, Otoroshi turns into a central hub for all your interactions with large-scale language models. By unifying your access to providers such as OpenAI, Anthropic, Hugging Face, Mistral as well as OVHcloud and Scaleway solutions, it simplifies management and optimizes operations.

For example, you can integrate the tokens of these providers and enable their use with a single URL for all your teams, or one in particular, by selecting the models to which it has access to, with a specific token, its rights, usage limits and so on. You can also adapt the prompts sent to the models on the fly, to guarantee the quality of responses and give them context. You no longer need to manage this on an application-by-application basis; it's directly included in your API.

In the event of heavy loads, the system intelligently distributes requests between several providers and can cache relevant results to accelerate response times. Finally, every interaction is logged and auditable, offering full traceability to optimize your workflows or meet compliance requirements.

Enhanced security: protect your data and models

Security concerns are at the core of the LLM extension. Thanks to its advanced access control mechanisms, you can prevent the leakage of sensitive information and protect your data through moderation mechanisms, for example. But you can define your own rules, basic or programmatic, to suit your needs.

Access authorizations are defined granularly, based on consumer metadata or query parameters. In addition, tools such as validation rules ensure that sensitive information is not included in queries.

Simplified deployment on Clever Cloud

With Clever Cloud, deploying Otoroshi with LLM is straightforward. You can either do it from the Console, the API or Clever Tools. Once deployed, you have immediate access to a management URL and temporary credentials to customize your instance:

$ clever addon create otoroshi myOtoroshi
Add-on created successfully!
ID: addon_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Real ID: otoroshi_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Name: myOtoroshi

Your Otoroshi with LLM is starting:
 - Access it: https://xxxxxxxxxxxxxxxxxxxx-otoroshi.services.clever-cloud.com
 - Manage it: https://console.clever-cloud.com/addon_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

An initial account has been created, change the password at first login (Security -> Administrators -> Edit user):
 - Admin user name: xxxxxxxxxxxxxxxxxxxxxxxx
 - Temporary password: xxxxxxxxxxxxxxxxxxxxxxxx

/!\ The otoroshi provider is in beta testing phase
Learn more about Otoroshi with LLM on Clever Cloud: https://developers.clever-cloud.com/doc/addons/otoroshi/

The add-on relies on a pre-configured Java application and a Redis® database to manage your flows. In just a few minutes, you'll be ready to harness the full power of Otoroshi and its LLM add-on.

Use case: unleash the power of your APIs

With Otoroshi with LLM, you can turn the management of your APIs and AI services into a real asset for your team. Imagine a centralized platform that lets you configure an AI agent to distribute access tokens in a secure and controlled way to your teams or customers. These tokens can be set up for specific uses, limiting access to certain features or resources according to your needs. This guarantees secure distribution tailored to the different people involved in your projects.

Then take advantage of moderation and prompt control tools. By ensuring that no sensitive or inappropriate data is transmitted in your queries, you not only protect your internal information, but also improve the quality and relevance of responses generated by AI models.

Leverage Otoroshi's auditing capabilities. Every interaction with your APIs is recorded in precise detail, with your account management/SSO, giving you a complete overview of usages. This transparency not only enables you to optimize your workflows, but also to meet any compliance requirements.

All this is available via a web interface, but also via the Otoroshi API, which is accessible and also preconfigured with your add-on. This will enable us to integrate this service directly into Clever Cloud.

Otoroshi with LLM in action: join us on Twitch on December 18

Want to see Otoroshi with LLM in action? We're hosting a live demonstration on our Twitch channel on December 18 at 1pm. Find out how to configure and use the add-on for your AI and API projects.

We'll also be giving a sneak peek at what we're up to with Cloud APIM around Otoroshi. Come and find out more about what we have cooked up for you in 2025.

A constantly evolving tool: your opinion counts!

Otoroshi with LLM perfectly illustrates our commitment to offering high-performance technological solutions, while integrating them into the heart of our ecosystem. Test it today, and get your teams ready to exploit the full potential of your APIs and AI services.

Currently in beta, Otoroshi with LLM is fully functional, but constantly being improved. Your feedback is essential to fine-tune the user experience and proposed functionalities. Join our GitHub community to share your suggestions and ask your questions.

Yet these ageing infrastructures pose constant challenges in terms of maintenance, evolution and cost.

SuperBOL: the solution that propels COBOL into the cloud era

SuperBOL is a solution that enables large companies to migrate their COBOL applications to cloud infrastructures without having to completely rewrite their existing systems. Developed by OCamlPro, and usable on Clever Cloud's public cloud, SuperBOL allows businesses to keep their COBOL systems while benefiting from the flexibility and scalability of the cloud. SuperBOL also offers a tool for transposing COBOL into C.

The challenges of COBOL in the modern era

After years of existence, COBOL today faces a number of challenges:

• Lack of qualified COBOL developers;
• High cost of mainframes and maintenance of legacy infrastructures;
• Difficulty of integration with modern technologies;
• Complexity of migration to new environments;
• These obstacles prevent many companies from evolving and keep them in costly, inflexible systems.

How does SuperBOL meet these challenges?

With SuperBOL, you can modernise your COBOL applications by migrating them to flexible cloud infrastructures, without having to rewrite all the code. Here are the key benefits:

• Simplified migration of COBOL infrastructures to a sovereign cloud environment;
• Reduced mainframe licence and maintenance costs;
• Optimisation of resources and reduction in the energy footprint of systems;
• Possible transpilation from COBOL to C, facilitating integration with other tools;
• Secure projects thanks to a scalable, high-performance infrastructure.

Come and discover SuperBOL during our live demo

On 15 October 2024 from 11:30 AM, during a webinar dedicated to SuperBOL, Fabrice Le Fessant, President of OCamlPro and Florent Perreux, Sales Director of Clever Cloud, will be giving a live demonstration of the solution, enabling you to find out how to deploy a COBOL application on Clever Cloud's public cloud.

Whether you're a CIO or a developer, come and find out more about SuperBOL at our webinar on 15 October.

They “push” their code, and we deploy it, while ensuring that the environment in which they operate is kept up to date and secure, with one clear objective: maintaining it in operational condition. Whatever the situation, their service responds.

Designing simple, robust and innovative services

We do this whilst minimizing the footprint on our servers, offering on-demand or automatic horizontal/vertical scaling. This means we can multiply instances or scale them up / down according to the load of your sites. This commitment to simplicity extends beyond applications, as we also offer a wide range of “as-a-service” database (DB) services, enabling you to deploy MongoDB, MySQL, PostgreSQL or Redis environments in a matter of seconds, with the same tools and guarantees.

However, over the past few years, we faced a number of recurring requests: not only did some of our customers wish to access other services, but they also regularly asked to take benefit of our infrastructure, spread over three datacenters, to obtain high-availability services. But when it comes to DB, this isn't always easy to implement while ensuring a high level of automation and data consistency. So we decided to develop our own range of products to achieve this.

The “Materia” project was born, based on the FoundationDB open-source transactional engine used, for example, by Apple for its iCloud services and by Snowflake. We're contributing to it and adapting it to our needs, while taking advantage of its distributed and resilient aspect, notably due to its significant simulation capacity. It allows us to imagine a whole universe of serverless services, very simple to use, invoiced on a pay-per-use basis, with compatibility layers we're developing to enable our customers to “talk” to it using existing protocols such as GraphQL or PostgreSQL, for example.

Materia KV available to all

We started with the Redis protocol to introduce Materia KV, currently in Alpha testing phase. It's a key-value database synchronously replicated across our three Paris datacenters. When our servers respond, your data has been written three times. Above all, it's very easy to use: go to our Console, create a Materia KV add-on, and you'll instantly obtain a token that can be used with any Redis client or by sending commands to our servers directly through the TCP protocol.

Thus, you can now benefit from a high-availability, key-value data storage solution, without having to configure a single instance, and with no minimum monthly fee: you simply pay for what you use. Above all, we provide this service with compatibility to existing protocols. Today Redis, tomorrow GraphQL. The list of supported commands is available here.

Launched at Devoxx France mid-April, Materia KV made a big splash on site and during our demonstrations since then. We've therefore decided to make it available to all, to enable our customers and the interested public to give us feedback on how it works for them, and what their needs are. While billing will be on a per-use basis starting with the Beta phase, right now it's free! So give it a try and let us know what you think.

Already built-in our tools and interfaces

Materia KV is of course available as an addon-provider in our API, Terraform (or OpenTofu, for example), but also in our CLI, Clever Tools. To create an access token, simply run the following command:

clever addon create kv NAME

This add-on can be linked directly to a Clever Cloud application, injecting its environment variables. But you can also use it from any third-party service, command-line client (CLI) or with graphical user interface (GUI).

While Materia KV and its various interfaces will be developed over time, we've started to think about integrating it into Clever Tools. A test branch, available as a binary and documented, offers a clever kv command.

With it, you can directly send requests to Materia KV by having the environment variable configured locally, or by specifying an ID in your commands:

# With Bash and Zsh
source <(clever addon env ADDON_ID --export)
# With Fish
clever addon env ADDON_ID --export | source

clever kv PING # PONG
clever kv set yourKey theValue
clever kv get yourKey

As this demo version doesn't handle all the commands managed by Materia KV, you can send a “raw” command and it will return the answer :

clever kv redis_raw 'hset key field1 value1 field2 value2' # 2
clever kv redis_raw 'hget key field2'                      # value2
clever kv redis_raw 'hgetall key'                          # the full hash

To demonstrate the possibilities of such integration, you also have the option of directly querying a JSON object stored in a key :

clever kv set simpleJson '{"key": "value"}' # the set data
clever kv getJson simpleJson key            # value
clever kv set jsonKey '[{"key": "value"}, {"bigKey": {"subKey1": "subValue1","subKey2": "subValue2"}}]'
clever kv getjson jsonKey bigKey.subKey2    # subValue1
clever kv getjson jsonKey ''                # the full JSON

To show just how simple such implementations can be, we've written a Materia KV client in Go using Go-Redis. If you'd rather understand how you can send commands and receive responses from Materia KV directly in TCP, you'll find examples in both V or Ruby.

Feel free to create your own and let us know ;)

A demonstration of Materia KV on Twitch, a community space

Want to find out more? Horacio González, our head of DevRel, will be giving a demonstration on Twitch on Tuesday June 18 at 13h15 (Paris Time). Pierre Zemb, creator of Materia at Clever Cloud, will also be discussing with our CTO Steven Le Roux in a video published at the end of June on Clever Cloud's YouTube channel.

And to share your views, questions and requirements, go to the Materia-dedicated section of our GitHub community space.

Your partner for efficient hosting

They can also benefit of our horizontal and vertical scaling capabilities to ensure that resources are allocated as closely as possible to their load, automatically if needed, billed per second.

All of this can be done from our own dense infrastructure in Paris or from our partners' datacenters such as OVHcloud and Scaleway. Thus, you can ensure that you reduce your need for IT ressources, by design. But some are looking for even more efficient solutions for their websites. In recent years, a trend has emerged to satisfy such demand: Static Site Generators (SSG).

Of course, you can deploy them on Clever Cloud!

Deploy any static website on Clever Cloud

They require very few ressources as they don’t rely on complexe software stack: no database nor server side calculations once deployed. In most cases, it’s pure HTML, CSS an client-side JavaScript, generated from Markdown content, with a theme/template applied.

There are lots of open source SSG on the market you can use for blogs, documentation or marketing websites for example. We can build them for you and then only deploy and serve the generated files on the Internet. No GitHub Actions or others external CI/CD is needed.

To help you in this journey, we’ve published tutorials with examples on how to deploy static website through Astro, Docusaurus, Eleventy (11ty), Hexo, Hugo, Lume (Deno), MkDocs, mdBook or Nuxt.

• Read our guides to deploy static websites on Clever Cloud

But others are also compatible! You want more guides or help on other SSG ? Just fill an issue: our documentation is open source, static, based on Hugo with Hextra theme. You can even contribute ;)

Devastating news for Wordpress haters: with a clean, secure, and modern file structure, you can easily migrate it to Clever Cloud. All of this is possible using the tools described in this post.

For those who have never used Git before, we will also cover how to deploy a WordPress installation on Clever Cloud in this post. If you want to give it a try, we'll walk you through the steps. If you choose not to, our platform does offer a GitHub integration.

Requirements:

• A Clever Cloud account
• Le Bedrock's Composer to deploy WordPress with Clever Cloud, that we have updated.
• A GitHub account if you deploy the code from it, or Git  installed on your computer, if you choose this method.

Deployment and WorpdPress configuration

Composer will deploy a WordPress site in a matter of minutes, creating a rapid, light, and secure framework for our new website.

Follow the instructions below:

1. Get the code

The code can be found in its  "WordPress + Bedrock" . public repository. It has a WordPress architecture that works with Composer. There are two ways to download it: directly from Git or GitHub (the easier choice if you don't feel comfortable using command lines).

Take this post as an opportunity to learn more about command lines on a Terminal and Git, even if you aren't accustomed to them. No worries, by following our directions, you will be able to use this method..

Option A : Using GitHub

If you really don't want to use Git, simply fork the code and deploy from GitHub on Clever Cloud. Creating a fork will duplicate the code in your own repository.

Open the Clever Cloud Console settings, clic on  "Profile" and link your GitHub account, if you haven't done it already. That's all, now go directly to step 2.

Option B: Using Git, step by step

The other option is to download the code to your computer (locally). If that's your first time, here are the instructions:

Set up

You must first grant permission for your computer to push code to Clever Cloud before you can proceed. You must create and add an SSH key to your console if you haven't already. Go directly to the next step if it has already been completed.

Open your Terminal and:

1. type ssh-keygen -t ed25519 -C "[votre@email.ici] the email must be the same you use to log into Clever Cloud.
2. When the Terminal asks you in which file you wish to add the key, juste press "Enter".
3. Add a password
4. Copy the key content using  pbcopy < ~/.ssh/id_[rsa].pub (replace [rsa] by your key id, of course))
5. Open the Clever Cloud Console and go to Profile>SSH keys>Add and paste your key's content.

Your machine is now connected to your Clever Cloud account and ready to push code.

Clone the code

1. Make a sites directory on your computer. It will contait your apps and your websites.
2. Open your terminal and type cd sites, this will open your "sites" directory.
3. Still in your terminal, copy-paste git clone git@github.com:CleverCloud/clever-wordpress.git'

The code has been downloaded to your computer, inside the sitesdirectory, you'll see a a new clever-wordpress directory. Open it (cd clever-wordpress) et type ls -a : you'll see all the files and directories it contains.

If you just used Git and your Terminal for the first time, you'll find more tutorials and explanations on the Internet. Our teammate David Legrand happens to publish great stuff I  greta stuff in French.

2. Declare the app on Clever Cloud

Click "Create" and "An application" from the Clever Cloud Console. After choosing your fork, you can create a new PHP app if you are using GitHub integration. All that remains is for the code to be pushed from GitHub. If you're using Git, the identical procedure can be carried out by entering a short command line.

The Console will ask if you need any add-on, choose a MySQL database and proceed.

Edit your PHP app environment variables in expert mode and past the salts generated on sur this page (don't forget to save  changes!)

6. Add 3 additional environment variables:
   • WP_ENV with value production
   • WP_HOME with value https://yourdomain.tld
   • WP_SITEURL with value https://your-domain.tld/wp

The Console will provide you with command lines to copy-paste in your Terminal in order to send your code to your new instance, unless you've decided to work with the GitHub integration. The deployment will begin once you've completed this.

While the deployment starts, create an Cellar addon and link it to your app (clic on your PHP app, then choose "Linked dependencies" to connect it).

From the Cellar set up page, create a bucket and give it a name.

Go back to your PHP app and add the following environment variable:

CELLAR_ADDON_BUCKET with the name of your bucket as value.

Tip : You can easily configure a custom domain for your bucket. Check  the doc.

Restart your app to incorporate last changes. Don't forget to set up your domain for the WP_HOME variable (or with a .cleveapps.io for testing purposes).

When you'll visit your website, the installation page from WordPress will then appear (you'll find de database credentials in the Console, either by clicking on the addon, either in your app's environment variables). Once you are logged into WordPress, go to your plugins page and activate S3 Uploads.

That's it. You now have a hosted WordPress on Clever Cloud. Your files and medias will be stored in the Cellar's bucket.

Add a plugin by a single command

The composer.json file reflects the WordPress themes and plugins directory; you just have to specify what it should reflect. You don't need to host the plugin directory in your app to add a new plugin to your site. You'll use Wpackagist to find and add the plugin's references to composer.json.

Find require , this is where the plugins are specified.

"require": 
//Here are your further plugins declarations. Add this line wherever you'd like (update the version if necessary)
"wpackagist-plugin/[plugin]": "[version]",

You'll find all your favorite plugins on Wpackagist to add them to the file. Commit changes (with Git : git add .  et git commit -m "un-message") and push the modified code to Clever Cloud (on GitHub, this action will be done automatically). Wait until your app has redeployed, then go top your WordPress dashboard and activate the plugins you just added.

Welcome aboard!!