Introducing Qovery NFTs
But first, a quick reminder about what an NFT is. From Investopedia:
"Non-fungible tokens (NFTs) are cryptographic assets on a blockchain with unique identification codes and metadata that distinguish them from each other. Unlike cryptocurrencies, they cannot be traded or exchanged at equivalency. This differs from fungible tokens like cryptocurrencies, which are identical to each other and, therefore, can serve as a medium for commercial transactions."
It means that an NFT is a unique token you can associate to any object, like an artwork of a monkey, a physical thing or even … A particular CI/CD pipeline execution.
See this thread for an idea of what the NFT phenomenon is all about.
Qovery NFTs
Many developers claim that "programming is a form of art." And in a sense, it's true. Ever heard someone say, "this is a beautiful piece of code." It goes beyond science and engineering. That's how the idea of Qovery NFTs came to us. If code is art, why not give the ability to a developer to own the instance when her masterpiece went live for everyone to contemplate?
From now on, you will be able to activate the NFT feature in any environment. When a commit gets deployed to the environment, a token will be generated and attributed to the developer having pushed the commit.
Why does it matter?
We firmly believe that individual developers deserve to be credited for the value they bring to a product. Every popular product released a legendary feature at some point. The No-Code YouTube game recently went crazy when Notion released its simple tables feature. What if the developer who has pushed that feature could claim ownership of it and even sell it.
It opens doors to a new collectibles market. Collectors worldwide will now be able to collect and own significant releases of the mainstream web applications. If it sounds ridiculous, think again. People initially thought owning a monkey PNG was ludicrous, yet the market is booming.
We are opening the gate to a whole new economy while empowering individual developers and giving them more credit for their hard work.
The future
For now, we are using the Ethereum blockchain. But we have already started working on our own. Later this year, we'll launch the Qovery coin, the new way of crediting your account for your deployments.
We are building the future of the cloud.
Stay tuned 🐟 !
Happy 1st April :)
.svg)
.svg)
.svg)
Suggested articles
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)