Hacker News new | ask | show | jobs
by itay-maman 139 days ago
My policy as a CTO is to always prefer things which are capped, so I'd go with 50 hours/month.
1 comments

Yep, agreed — BYOS is great for folks who already have a box, but “managed” removes the biggest friction for trying it. Managed is on the roadmap. For that, I’m leaning toward on-demand containers (Azure Container Apps / Fly.io-style) with: - ephemeral compute (spin up, work, tear down) - encrypted workspace (ideally user-controlled keys) - optional bring-your-own repo/storage so CloudForge never needs plaintext access to your code

Curious: would “managed” feel acceptable if it were BYOC (runs in your cloud account), vs CloudForge-managed infra? And what matters most: one-click setup, predictable monthly cap, or sessions surviving network switches/sleep?

I've implemented Managed Server!