Infrastructure control plane for your coding agents. Agents deploy, you stay in control.
New York 🇺🇸 / Paris 🇫🇷
Joined October 2019
- Tweets2.7K
- Following955
- Followers3.1K
- Likes2.4K
Pinned Tweet
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…
1/ Live in 30 minutes: the migration takes 2 weeks, deciding to do it takes 6 months. 🕔
5pm Paris / 11am ET, with Guillaume Da Silva.
2/ On the agenda: where migration time really goes, the human constraints that stall the decision, and which preparation steps AI agents can automate today.
3/ Bring the migration that has sat on your roadmap for more than a quarter. Is it stuck on the workloads, or on the decision?
linkedin.com/events/75120464…
1/ Vercel Ship SF: 2,700+ builders at the Palace of Fine Arts, and our co-founders Romaric and Morgan were in the room 🚢
3 takeaways for platform teams 👇
ALT Romaric Philogene and Morgan Perry, Qovery co-founders, standing in front of two stacked black shipping containers branded Ship SF at Vercel Ship 2026 in San Francisco.
4/ Bring Your Own Cloud on AWS is GA.
Per Vercel's docs, Node.js and Python functions run as Lambda in your account. TLS still terminates at Vercel's CDN, requests pass through Vercel, containers and Services are excluded. AWS only.
ALT Qovery card on a dark violet background: Vercel Ship 2026. Bring your own cloud should mean the whole stack. Vercel BYOC runs functions in your AWS account. TLS still terminates at Vercel's CDN.
5/ So the demand for running in your own cloud is validated. The open question is scope: functions only, or the whole stack, data and agents included?
Our full breakdown, with the docs quotes:
qovery.com/blog/vercel-ship-…
It's still a pilot. We haven't measured the time saved yet, and we're still looking for the right schedule, because a finding can turn urgent between two runs.
Would you run it daily, or trigger it on every new finding?
Tuesday at 5pm Paris / 11am ET: why a 2-week migration takes 6 months to decide, with Guillaume Da Silva and Romaric Philogène.
One migration estimated at 3 months by hand took 16 hours with Qovery and agents. We'll show where the time went.
qovery.com/events/migration-…
Talkspace used to see a sprint's releases slip by up to two weeks when a large feature blocked the pipeline. With Qovery, they've shipped 20 consecutive on-time deployments 📦
qovery.com/case-studies/talk…
3/ In 1.0, a refresh reads the real state from the API. A Console change shows up in terraform plan and the next apply reverts it. An attribute you leave out plans the Qovery default. There's also a new qovery_blueprint resource for catalog services.
4/ It's a major version with breaking changes, so read the upgrade guide and run a plan before you bump.
Should Console edits on Terraform-managed resources be reverted, or blocked outright?
qovery.com/changelog/2026-10…
