Infrastructure control plane for your coding agents. Agents deploy, you stay in control.
New York 🇺🇸 / Paris 🇫🇷
Joined October 2019
- Tweets2.7K
- Following956
- 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…
3/ Handy for database migrations, one-off scripts or checking config. Need more room for a heavy data job? Add --memory 2Gi --cpu 1.
4/ What's the riskiest command you've run inside a live pod?
qovery.com/changelog/2026-07…
Qovery retweeted
To get the railway experience on aws - gcp or azure - checkout qovery.com / @Qovery_ - I’m the cofounder. 200+ companies using it (zoom, Alan, Talkspace…)
3/ You describe your stack first (clouds, frameworks, databases, queues) and the sandbox is generated from it. A Rails team practices on Rails services with Sidekiq workers.
4/ Who on your team still asks "where are the logs?" in Slack?
qovery.com/blog/introducing-…
1/ Qovery Training is live for every Qovery customer. It's a sandbox copy of the Console on fake data, so you can deploy, roll back or delete an environment and nothing reaches your cloud account. 🎓
1/ Heroku database upgrades could take Getsafe offline for up to eight hours. 🛡️
Getsafe is one of Europe's leading digital neo-insurers, and people use its app daily.
3/ With no dedicated DevOps team, they moved to AWS with Qovery on top. Downtime during critical upgrades went away, and a data engineer who isn't a backend developer built and deployed an ML service in one day.
4/ How long was your last planned maintenance window, and who had to stay up for it?
qovery.com/case-studies/gets…
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-…
