Q
Qovery Blog
qovery.com · Company blog · on HN since 2019
Qovery's company blog covers its cloud deployment platform, Kubernetes tooling, and technical posts on Rust, including async streams and memory errors.
What HN saysHN links it for Rust guides and cloud deployment. Commenters mention Qovery as a French alternative host, and staff post job openings.
26HN people shared it
8linked it in comments
40stories submitted
207story points
6 months agolast shared
2019people per year2026
Most-shared posts
- 1Qovery – Deploy complex applications, seamlessly6 people · 1 points · first shared 2020 · discussion on HN
- 2How to Lose Stars on GitHub?4 people · 36 points · first shared 2021 · 49 comments on HN
- 3A Guided Tour of Streams in Rust4 people · 3 points · first shared 2022 · discussion on HN
- 4Pleco – the open-source Kubernetes and Cloud Services garbage collector2 people · 4 points · first shared 2022 · discussion on HN
- 5How we built Qovery2 people · 3 points · first shared 2022 · discussion on HN
- 6Why Rust Has a Bright Future in the Cloud2 people · 2 points · first shared 2020 · discussion on HN
- 7Feedback about Nixpacks – an alternative to Buildpacks2 people · 2 points · first shared 2022 · discussion on HN
- 8Rust: Investigating an Out of Memory Error1 people · 111 points · first shared 2025 · 29 comments on HN
- 9What are the alternatives to hiring a DevOps engineer?1 people · 5 points · first shared 2020 · discussion on HN
- 10I interviewed 200 CTOs from growing startups – here's what came up1 people · 4 points · first shared 2020 · discussion on HN
- 11A month after switching from Slack to Discord in a remote-first tech startup1 people · 3 points · first shared 2020 · discussion on HN
- 12React-Xtermjs – A React Library to Build Terminals1 people · 3 points · first shared 2024 · 1 comments on HN
- 13Qovery: Superpowers for Developer1 people · 3 points · first shared 2020 · discussion on HN
- 14How to Achieve Zero-Downtime Application with Kubernetes (2023)1 people · 2 points · first shared 2024 · discussion on HN
- 15Terraform vs. Pulumi: What to Use in 2022?1 people · 2 points · first shared 2022 · 3 comments on HN
What HN people wrote when they linked it
thibaut_barrere · 2022-04-27
A couple of French-based options that I've been using as replacements:
- https://www.clever-cloud.com
- https://scalingo.com
- https://www.qovery.com
evoxmusic · 2021-04-20
Well written article. This exactly with this spirit - of making AWS, GCP, Azure accessible to any developer that Qovery has been built. The idea of Qovery is to build the future of the Cloud - making developers to deploy their apps on AWS in just a few seconds. No joke. 2200+ developers from 110+ countries are deploying hundreds of apps per day. And this is only the beginning. Thanks again for sharing this article.
You can give a try to Qovery here: https://www.qovery.com
kkapelon · 2021-02-26
It is coming. Check https://www.qovery.com/ and https://www.hyscale.io/
(Not affiliated with either)
ev0xmusic · 2020-11-02
Qovery (https://www.qovery.com) | Container as a Service platform for developers | REMOTE EU / US
* Sr. Backend Engineer -> https://angel.co/company/qovery/jobs/673623-backend-software-engineer-…
* Dev Advocate -> https://angel.co/company/qovery/jobs/734995-evangelist-developer-advoc…
Join us on https://discord.qovery.com
erebe__ · 2023-12-13
The article share some common pitfalls people stumble upon when starting using Async in Rust.
If you know some others that are not listed, let's share it in comment :)
P.s: Other tuto article, if you are starting with Async https://www.qovery.com/blog/a-guided-tour-of-streams-in-rust
qoveryblog · 2023-12-13
The article share some common pitfalls people stumble upon when starting using Async in Rust.
If you know some others that are not listed, let's share it in comment :)
P.s: Other tuto article around Stream, if you are starting with Async https://www.qovery.com/blog/a-guided-tour-of-streams-in-rust
tonyx · 2023-04-11
Hey everyone, we were doing some repo admin and briefly changed the visibility of the repo from public -> private and back to public, then discovered in horror that we lost ALL the github stars and forks! Googling suggests that others have ran into this issue too and github is not able to restore it (see https://www.qovery.com/blog/we-lost-3800-stars-on-github-in-1-click).
Could you help us by starring our repo and perhaps spread the word? Would really mean a lot! https://github.com/useVenice/venice
PSA: Never change a public repo to private, not even for a moment, because doing so means you will irreversibly lose ALL your github stars and forks, there is no going back! :(
jeremy_k · 2022-12-28
https://releasehub.com/ (Disclaimer, first listed because I work here)
https://www.quali.com/
https://www.withcoherence.com/
https://webapp.io/
https://www.uffizzi.com/
https://www.qovery.com/
https://www.devzero.io/
These exist in the B2B space (and isn't an exhaustive list), there are a ton more in the B2C space