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")?
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.
Thanks! You're absolutely right.
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")?
My policy as a CTO is to always prefer things which are capped, so I'd go with 50 hours/month.