Hey! If you’re looking to do it “properly” which of course scales much better should you ever need it, then yep that seems about right. I would suggest white labelling another Veeam Cloud Connect Service instead and then you can manage your sub tenants, you can centrally manage licensing for them too and effectively just resell a rental license to your customers.

See who’s available here: https://www.veeam.com/find-partner.html?type%5B%5D=VCSP

Hi Tom, you can find some info about VCC architecture here:

https://helpcenter.veeam.com/docs/backup/cloud/cloud_infrastructure.html?ver=120

https://vccbook.io/2.Architecture/2.1-veeam_backup_replication_server.html

I don’t know if you can install all services (VCC + CGW + VSPC) on a single host, in any case definitely not a best practice.

The other option, as Michael said, is that you lean on some other Veeam Cloud Service Provider and get listed as a reseller, leveraging its infrastructure to resell Veeam services to your customers:

https://helpcenter.veeam.com/docs/vac/reseller/about.html?ver=70

So, I have all running on one box right now as it’s really just been used for monitoring and some light management (more so as newer versions add additional features) although I’m starting to venture into using it for VCC backups (all direct to object right now) as well. 

With that said, I designed my configuration with the intent that it could scale out at some point if required.  I think @MicoolPaul is probably correct though….if you’re not really using it as a VCC and want it cloud-hosted, it might be a good idea to sign up as a reseller and utilize someone else’s console/VCC infrastructure as the console does have the capabilities to host resellers in between the console and the end users.

Thank y’all for the input.  I am taking it all under consideration and I have reached out to a few partners as well.