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…
1/ An AI agent with production access should run inside your cloud, next to the workloads it touches. 🔐
3/ The Qovery control plane only processes deployment metadata: configuration state, resource metrics and deploy events. We don't host your workloads, and on Enterprise you can self-host the control plane itself.
4/ Every run shows its trigger, duration and cost. Where do your agents run today, your cloud or a vendor's?
qovery.com/sovereignty
Qovery retweeted
the demo was the easy part 🫠
Second Opinion #2 is about everything after it: safety, prod access, and the token bill
Nov 12, Paris, with @avec_alan , @Qovery_ & @AWS
luma.com/4lhbur28
1/ During a Heroku exit, you pay Heroku and AWS at the same time for roughly 4 to 8 weeks. That overlap is what quietly drains the budget. 💸
3/ Activate is the startup path. MAP is the bigger pool for a migration, and an AWS Partner drives the request for you. Watch NAT Gateway and data transfer, the two charges that surprise people.
4/ Did your migration budget include the overlap?
qovery.com/blog/fund-heroku-…
3/ Romaric Philogène (CEO, Qovery) on "Who gives the agent access to production?": scope, check and contain, with a live demo of policy-based agent tokens.
4/ Also speaking: Thomas Humeau (Alan) and Charline Boulie (AWS). Seats are limited and registrations are reviewed: luma.com/4lhbur28
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-…
