๐ BIG ANNOUNCEMENT: ZCP is live!
A cloud dev platform where your coding agent works alongside you in the same workspace.
Bring your own agent and subscription, run a full MCP-native dev loop, and keep production clean as you build.
Details below.
You donโt have to choose between broken and exposed. Constrain each key at the provider instead of disabling it: spend cap, IP allowlist, deny policy.
Same effect as revoking for an attacker, zero effect on your users.
(May we suggest you also check Zerops?! You mind find a nice, affordable alternative)
@jackedAJ Third option: leave the keys in place and restrict them at the provider.
Spend limit, IP allowlist, or a deny policy on the key. The thief gets nothing, your app stays up, and you rotate for real when deploys return.
(Or checkout Zerops, you might find something new!)
Rotating needs a deploy, so skip rotating for now and constrain instead.
Spend caps and IP allowlists at the provider kill the stolen keyโs usefulness while your old value keeps working. Rotate properly once builds are back.
(Or check out Zerops, so you won't have these kinds of issues!)
@kwesann@hijacker_mills Zerops is the closest shape: push to deploy, managed Postgres in the same project, billed per minute.
Render and Fly are the other two worth pricing. Whichever you pick, rotate at the provider first rather than waiting on a redeploy.
@AlokTom19637918 If you decide to move, we are happy to welcome you to Zerops. Check us out; we're very affordable and have a vibrant Discord community too, to answer any of your questions!
@0xRickHerr@0xQuit If you decide to move, we are happy to welcome you to Zerops. Check us out, we're very affordable and have a vibrant Discord community too, to answer any of your questions!
Your team, plus extra hands.
Zerops Mate is an AI engineer hired into an environment of its own. Its work comes back as a pull request, and goes through review like everyone elseโs.
A person still decides what ships.
Coming soon โ https://t.co/c9wOkvJZ6p
@louislikelouis Hope the migration goes smoothly, and worth checking whatever you pick actually publishes a status page and postmortems.
(If you ever want to change again, check Zerops.)
@Playoffcity Worth deciding on the database first, itโs what makes these migrations slow. If it moves with the app into one project you keep the Railway workflow without the single-vendor risk.
Have a look at Zerops too, we run in our on bare metal with 15y of experience.
@dhruvalgolakiya Only if everything you run is request-shaped. If any of it is a long-lived process or needs a real database, Workers will be a rewrite rather than a move. So we suggest Zerops :)
@daniel_rich Closest shape to Railway is Zerops: push to deploy, managed Postgres in the same project, billed per minute on resources.
Render and Fly are the other two worth a look depending on whether you want regions or simplicity.