←
Qovery2,780 posts
Qovery avatar

Qovery

@Qovery_

Infrastructure control plane for your coding agents. Agents deploy, you stay in control.

◷ Joined October 2019▧ 370 Photos and videos
Qovery avatar
Qovery@Qovery_·Sep 25

You missed our “Heroku to AWS in One Command” live session yesterday - no problem. Here’s the summary and recording: qovery.com/blog/heroku-to-aw…

Qovery avatar
Qovery@Qovery_·8h

4/ Pre-production runs on AWS spot instances that Qovery manages with Karpenter. How long is your team's deploy feedback loop? qovery.com/case-studies/kelv…

Qovery avatar
Qovery@Qovery_·8h

3/ No one on the small team wanted to become the DevOps engineer, and Heroku wouldn't let them use their AWS credits. On Qovery they run production and pre-production clusters, and a merge to develop deploys to pre-production.

Qovery avatar
Qovery@Qovery_·8h

2/ kelvin turns open data and machine learning into energy renovation plans for buildings. It started on a manually managed ECS setup with a single production environment and no staging, so every feature went straight to production.

Qovery avatar
Qovery@Qovery_·8h

1/ kelvin cut deploy time from up to 30 minutes to 5. 🚀

Post attachment
byron love avatar
⟳ Qovery retweeted
byron love@byronlove111·Nov 2

HACKATHON ALAN X QOVERY X AWS les garsssss j’avais participé à la premiere version de ce hackathon y’a quelques mois donc j’suis graave content de co-organiser la 2ème édition de AI Health Hack 6.000€ à gagner, avec déjeuner et diner offert pour tout le monde Dans les locaux d’@avec_alan à Paris le 28 Novembre prochain Lien en dessous pour s’inscrire! huge thanks to @Qovery_ @AWS 💜

Post attachment

Si ca vous intéresse de rejoindre Alan (que ce soit en stage ou CDI) Je vous conseille de vraiment venir a nos hackathons c’est comme ca que je me suis fais repéré et c’est le moyen le plus simple pour candidater je trouve j’vais essayer d’en organiser un avec ma team d’ici décembre j’vous tiens au courant 🙌

Post attachment
Qovery avatar
Qovery@Qovery_·Nov 17

4/ Across all customer builds, p90 went from 573 to 235 seconds and p95 from 689 to 367. Nothing to change on your side. What's your median build time today? qovery.com/blog/qovery-build…

Qovery avatar
Qovery@Qovery_·Nov 17

3/ Four fixes in October: builders went from 8 GB to 16 GB of RAM, builder nodes moved to local NVMe disks, images and build cache use zstd instead of gzip, and the engine skips the repo clone when the image already exists.

Qovery avatar
Qovery@Qovery_·Nov 17

2/ Customers compared our builds with GitHub Actions, and we were slower: 1.4x to 3.6x longer on a public benchmark in September. A few moved their image builds to GitHub Actions and used Qovery only to deploy.

Qovery avatar
Qovery@Qovery_·Nov 17

1/ The median Qovery build went from 183 to 84 seconds in six weeks. ⚡

Post attachment
Qovery avatar
Qovery@Qovery_·Nov 17

3/ Guillaume Da Silva and Romaric Philogène show an agent reading a legacy Terraform estate, including what it makes up, then run the move live: EKS cluster provisioned, workload moved, static egress IP kept.

Qovery avatar
Qovery@Qovery_·Nov 17

2/ Moving the containers is the easy part. ECS to EKS migrations stall on the static egress IPs partners allowlisted, IAM, secrets, service discovery, and Terraform modules nobody on the current team wrote.

Qovery avatar
Qovery@Qovery_·Nov 17

1/ Today at 5pm Paris / 11am ET: ECS to EKS without freezing the roadmap for a quarter. 🗓️

Post attachment
Qovery avatar
Qovery@Qovery_·Nov 16

4/ Control comes from the platform: scope each agent with a policy token, log every action, allowed or denied, and test the policy before you hand over the token.