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

New York 🇺🇸 / Paris 🇫🇷
Joined October 2019
Qovery retweeted
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. 💸
1
1
65
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
1
58
Qovery retweeted
1/ Nov 12, Paris: "Agents in production: beyond the demo". Alan, AWS and Qovery host an evening of talks on running AI agents in production. 🧵
1
2
84
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. 💸
1
1
65
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.
2
10
1/ Nov 12, Paris: "Agents in production: beyond the demo". Alan, AWS and Qovery host an evening of talks on running AI agents in production. 🧵
1
2
84
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.
1
15
1/ Tip: Debug production without opening a shell inside the live pod. 🐚
1
70
3/ Handy for database migrations, one-off scripts or checking config. Need more room for a heavy data job? Add --memory 2Gi --cpu 1.
1
12
Wonderful
Rebuilt the @Qovery_ onboarding this week, with a few small details like the transition between steps
1
163
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
72
2/ 18 tracks and 68 lessons for software engineers, DevOps, platform and security teams, from Basics to Expert. Migration tracks too: Heroku, Vercel and Cloudflare to AWS.
1
33