This looks really promising. I understand the rationale behind BYOS, but I think there's a segment of builders who'd prefer a managed service over provisioning/securing their own machine.
Managed hosting is actually on the roadmap. The plan is
to offer on-demand containers (likely Azure Container Apps
or Fly.io) where users can spin up an environment without
provisioning their own server.
For privacy-conscious users, even the managed option would
use encrypted volumes with user-controlled keys - so we
(CloudForge) couldn't access their code either.
BYOS came first because that's what I personally needed,
but managed is definitely coming for those who prefer
the convenience.
Would you prefer pay-per-hour or a monthly allocation
(like "50 hours/month included")?
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?
Managed hosting is actually on the roadmap. The plan is to offer on-demand containers (likely Azure Container Apps or Fly.io) where users can spin up an environment without provisioning their own server.
For privacy-conscious users, even the managed option would use encrypted volumes with user-controlled keys - so we (CloudForge) couldn't access their code either.
BYOS came first because that's what I personally needed, but managed is definitely coming for those who prefer the convenience.
Would you prefer pay-per-hour or a monthly allocation (like "50 hours/month included")?