Understanding Community Edition License with Hub

Our nonprofit is looking at using Certify the Web for our internal servers. Are we ok to stay with the Community edition with this usage? - 4 total servers including the hub, each with 3 or less certificates. If we upgrade to a license will this be counted as 4 servers - since one is the hub?

What we have set up so far is one server running the hub and it also generated the ssl cert for the Hub and a test for IIS and a wildcard cert - 3 certs total.

One IIS server running CCM joined to the hub. It has one certificate for IIS.

One ArcGIS server running CCM joined to the hub. It has one cert used for IIS and the same used for the ArcGIS services

One Remote desktop gateway server which we would like to join. It currently uses one certificate.

Hi,

Funded organizations are expected to be licensed and that counts for all instance of the app and hub. If you are licensed for one instance you are expected to be licensed for all instances. Instances are licensed per install,not based on how many certificates you are looking after.

You can mix and match license bundles (e.g. Professional for your instances and 1 Starter for your hub). Another alternative is to use Cloud Licensing via Azure marketplace, then you can dynamically set how many installs you want to cover.

If you are looking to conserve license activation you could consider using CCS in IIS (with the deploy to CCS task from the hub), that way the IIS cert is just deployed via a file share and can be done from the hub.

You can of course evaluate the software for free, and there is currently no time limit on that.