sslbrain or GlobalSign?
GlobalSign suits teams using their own ACME clients; TLS Connect Standard does not automate deployment outside ACME.sources
Checked 25-10-2026 · compared: TLS Connect Standard
Automated deployment to F5
sslbrain: The F5 integration installs certificates through push from the appliance.
GlobalSign: TLS Connect Standard deploys manually; scheduled F5 deployment requires Premium.sources
With Standard, you must start deployment to F5 yourself after each renewal.
Servers on separate networks
sslbrain: Professional/Enterprise: service-agent through sslbrain Cloud (EU), without VPN.
GlobalSign: TLS Connect Premium needs hub access or a separate installation for each network.sources
With TLS Connect, each branch needs access to the hub or its own licensed installation.
Where the platform is hosted
sslbrain: Your customer data and sslbrain Cloud (EU) operations stay in the EU.
GlobalSign: Atlas is hosted in the UK; no EU region is stated.sources
The documented Atlas location does not meet a requirement for EU hosting.
GlobalSign is a better fit when
- You use your own ACME clients and want certificates from Atlas.sources
- You want up to 100 certificates managed from one TLS Connect installation on your server.sources
- Available through FairSSL. Price on request: Write to us
sslbrain is a better fit when
- You want certificates installed on both F5 and FortiGate through push from the appliance.
- You require the vendor to keep customer data and operations in the EU.
- You want branches connected through sslbrain Cloud (EU) without VPN using Professional or Enterprise.
Price for your size
Available through FairSSL. Price on request: Write to us
20 servers
GlobalSign · TLS Connect Standard699 USD per year (approx. €620)sources
sslbrainBasic: €2.990 per year
50 servers
GlobalSign · TLS Connect Standard699 USD per year (approx. €620)sources
sslbrainBasic: €2.990 per year
250 servers
GlobalSign · TLS Connect Standard2,097 USD per year (approx. €1.900)sources
sslbrainProfessional: €12.990 per year
Annual list prices excluding VAT. GlobalSign in the vendor’s own currency. Amounts in brackets are converted at the ECB reference rate of 23-10-2026.
Comparison
Standard is selected for manual deployment outside ACME; calculations assume one certificate per server.
Price and licence
Annual price
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Installation
How certificates are installed
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Network devices
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Windows servers
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Linux servers
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Cloud
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Security
Private keys
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Network and ports
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Sites and separate networks
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Vendor
Vendor
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
Data and hosting
sslbrain
GlobalSign · Atlas ACMEGlobalSign · TLS Connect StandardGlobalSign · TLS Connect Premium
All 69 facts about GlobalSign
Price per year and per month
- Atlas ACME
- Not public, requires a sales conversationsource
- TLS Connect Standard
- 699 USD per year; Unit: licence for one TLS Connect installation (machine-bound licence key), up to 100 certificates, list price excl. VAT; Minimum: 1 licencesources
- TLS Connect Premium
- 3,000 USD per year; Unit: licence for one TLS Connect installation (machine-bound licence key), up to 100 certificates, list price excl. VAT; Minimum: 1 licencesources
How the certificate gets there
- Atlas ACME
- ACME/SCEP only: the customer's own ACME client connects via External Account Binding to the Atlas account and retrieves certificates from GlobalSign's ACME server; no GlobalSign agent or pushsources
- TLS Connect Standard
- ACME/SCEP only: automatic renewal occurs only through TLS Connect's ACME solution (simple-acme on the same server); other issuance and deployment to endpoints is manual in Standardsources
- TLS Connect Premium
- Both integrations/push and ACME: Automation Service on the TLS Connect server renews and deploys on a schedule to servers with a TLS Connect agent and to integrated cloud platforms and network devices (push); also ACME via simple-acmesources
Without a direct integration
- Atlas ACME
- The customer's own ACME client; GlobalSign has confirmed Certbot, win-acme, simple-acme, dehydrated, Certify The Web, acme.sh, Lego and Acmebot. Domains that cannot be validated via ACME can be validated by email in the Atlas portalsource
- TLS Connect Standard
- Manual deployment from TLS Connect, export of the certificate (PFX, PEM or JKS) or a custom script run after issuance in the ACME flow; automation with an agent and agentless scripts requires Premiumsources
- TLS Connect Premium
- Agentless script (curl or PowerShell) that the customer runs and schedules on the target server, also for network equipment and load balancers that can run curl/PowerShell; PowerShell for other destinationssources
Push with no software on the destination
- Atlas ACME
- Not stated
- TLS Connect Standard
- F5 BIG-IP (manual deployment from TLS Connect with the device's credentials; no scheduled automation in Standard)sources
- TLS Connect Standard
- AWS (manual deployment from TLS Connect via the cloud account's credentials; the service is not named)sources
- TLS Connect Standard
- Microsoft Azure Key Vault (manual deployment from TLS Connect via the integration)sources
- TLS Connect Standard
- Google Cloud (manual deployment via the integration; the service is not named)sources
- TLS Connect Premium
- F5 BIG-IP (an automation task on the TLS Connect server deploys with saved credentials)sources
- TLS Connect Premium
- AWS (automation task; the service is not named)sources
- TLS Connect Premium
- Microsoft Azure Key Vault (automation task on the TLS Connect server via the integration)sources
- TLS Connect Premium
- Google Cloud (automation task; the service is not named)sources
FortiGate
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
F5 BIG-IP
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard
- Partial (manual deployment only; scheduled deployment requires Premium)sources
- TLS Connect Premium
- Yes (BIG-IP integration; an automation task on the TLS Connect server deploys)sources
NetScaler
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
SonicWall
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
Palo Alto
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
Check Point
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
Kemp LoadMaster
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
Cisco
- Atlas ACME
- No (not in GlobalSign's integration list, 25-10-2026)source
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026)source
IIS
- Atlas ACME
- Yes (the customer's ACME client; GlobalSign's Japanese guide: simple-acme installs and renews on IIS 10)source
- TLS Connect Standard
- Yes (ACME via simple-acme with "Install to IIS automatically" on the TLS Connect server; otherwise manual binding)source
- TLS Connect Premium
- Yes (ACME with IIS installation, a TLS Connect agent, or an agentless PFX script that imports into Windows certificate store; the IIS binding is set manually the first time)sources
Exchange
- Atlas ACME
- No (not in GlobalSign's documentation, 25-10-2026; the ACME documentation has a client list and guides for Apache, nginx, IIS and Azure Key Vault, not Exchange)sources
- TLS Connect Standard and TLS Connect Premium
- No (not in GlobalSign's integration list, 25-10-2026; the TLS Connect documentation mentions IIS but not Exchange)sources
nginx and Apache
- Atlas ACME
- Yes (the customer's ACME client Certbot with --nginx or --apache; GlobalSign guides for Apache and nginx)source
- TLS Connect Premium
- Yes (agentless PEM script on the server, scheduled with cron, retrieves renewed server.pem and server.key and reloads nginx; initial configuration is manual)source
- TLS Connect Standard
- Partly (manual export from TLS Connect only; automatic delivery with the agent or an agentless script requires Premium)sources
Tomcat (JKS)
- TLS Connect Premium
- Yes (agentless JKS script, scheduled with cron or Scheduled Task, retrieves a new keystore.jks and restarts Tomcat)source
- Atlas ACME
- No (not in GlobalSign's documentation, 25-10-2026; the ACME documentation has a client list and guides for Apache, nginx, IIS and Azure Key Vault, not Tomcat/JKS)sources
- TLS Connect Standard
- Partly (manual export in JKS format only; automatic delivery with the agentless JKS script requires Premium)sources
Azure Key Vault
- Atlas ACME
- Yes (the customer's ACME client: Acmebot or az-acme CLI; GlobalSign has a Japanese guide for az-acme)sources
- TLS Connect Standard
- Yes (Azure Key Vault integration; manual deployment or "Store in Azure Key Vault" in the ACME flow via a simple-acme plugin)sources
- TLS Connect Premium
- Yes (Azure Key Vault integration; automation task or the ACME flow)sources
AWS Certificate Manager
- All editions
- Not stated
Where the private key is kept
- Atlas ACME
- the destinationsources
- TLS Connect Standard and TLS Connect Premium
- on-premises at the customersource
Servers with a service agent or ACME
- Atlas ACME
- The customer's ACME client connects outbound to GlobalSign's ACME server (HTTPS URL; port not stated). For http-01, the ACME server retrieves a token over HTTP from the web server (inbound from the internet); dns-01 requires no inbound connectionsources
- TLS Connect Standard
- The TLS Connect server (Windows) must have outbound internet access, and its IP address must be manually allowlisted by GlobalSign; ACME with http-01 requires the IIS site to be publicly accessible. Ports are not statedsources
- TLS Connect Premium
- As in Standard; the agents and agentless scripts also poll the TLS Connect hub on the internal network (port 5086), so the TLS Connect server must be able to receive inbound connections from endpoints. The agent checks every 3 seconds by defaultsources
Equipment without a service agent
- Atlas ACME
- Not stated
- TLS Connect Standard and TLS Connect Premium
- The TLS Connect server on the customer's network deploys to F5 and cloud accounts using the credentials stored in TLS Connect; protocol, ports and connection direction are not stated. Servers without an agent retrieve the certificate from the TLS Connect hub themselves (port 5086)sources
Windows
- Atlas ACME
- The customer's ACME client on Windows (e.g. simple-acme, win-acme, Certify The Web); GlobalSign's Japanese guide shows installation and automatic renewal on IIS 10 with simple-acmesources
- TLS Connect Standard
- TLS Connect runs on Windows; The ACME flow can install in an IIS site on the server, otherwise the certificate is manually bound to local IIS sites or manually deployed with "Deploy Remote"sources
- TLS Connect Premium
- As in Standard; also a TLS Connect agent (agent.exe as a Windows service) or an agentless PowerShell script with Scheduled Task, which retrieves PFX to C:\certs\server.pfx and imports into the Windows certificate storesource
Linux
- Atlas ACME
- The customer's ACME client (Certbot, acme.sh, dehydrated, Lego); Certbot can install in Apache and nginxsource
- TLS Connect Standard
- Manual export from TLS Connect (e.g. PEM or JKS) and copying to the server; automatic Linux deployment (agent, agentless) is under Automation, which requires Premiumsources
- TLS Connect Premium
- TLS Connect agent on Linux or an agentless curl script with cron, which retrieves server.pem and server.key (or JKS for Tomcat) and reloads the web serversource
Remote sites and branch offices
- Atlas ACME
- Not stated
- TLS Connect Standard
- One TLS Connect installation per machine with its own licence key; multiple installations are permitted. Requirements for sites without a direct connection are not statedsource
- TLS Connect Premium
- The agent's target server must be on the same network as the TLS Connect server; other sites require their own TLS Connect installation with their own licence key or network access to the hub (VPN is not mentioned)sources
Vendor
- All editions
- GMO GlobalSign K.K., Tokyo, Japan (GMO GlobalSign Holdings K.K.; GMO Internet Group). Offices and regional companies in Belgium, the United Kingdom and the USA, among others. GMO GlobalSign Holdings K.K. is listed on the Tokyo Stock Exchange Prime Market, and its largest shareholder is GMO Internet Group, Inc. with 52% of the votes (31-12-2025); ultimate owner: GMO Internet Group, Inc., Japansources
Hosting and the EU
- Atlas ACME
- Atlas: AWS in the United Kingdom (UK). GlobalSign's data centres: Japan (Tokyo), Singapore and the United Kingdom (London). Atlas portal login (Okta): Germany and Ireland; hosting firm: Amazon Web Services, USAsources
- TLS Connect Standard and TLS Connect Premium
- TLS Connect runs on-premises at the customer; the Atlas platform runs on AWS in the United Kingdom (UK). When GCC is used, GCC's hosting country is not stated; hosting firm for Atlas: Amazon Web Services, USAsources
Sources (25)
docs.globalsign.com
- 1. ACME · checked 11-10-2026
- 3. TLS Connect FAQs · checked 11-10-2026
- 4. TLS Connect License Key Management with Product Packages · checked 11-10-2026
- 5. TLS Connect Software Installation · checked 11-10-2026
- 7. TLS Connect Automation · checked 11-10-2026
- 8. TLS Connect Integrations · checked 11-10-2026
- 9. TLS Connect Agent/Agentless Deployment · checked 11-10-2026
- 14. TLS Connect Certificate Management · checked 11-10-2026
- 15. TLS Connect · checked 11-10-2026
- 19. Atlas Integrations · checked 25-10-2026
- 20. IIS + simple-acme · checked 11-10-2026
- 21. ACME FAQs · checked 11-10-2026
- 22. ACMEについて · checked 25-10-2026
- 23. ACME Certificate Management · checked 11-10-2026
- 24. Azure Key Vault + AZ ACME · checked 11-10-2026
- 25. ACME Getting Started · checked 11-10-2026
globalsign.com
- 2. ACME - Automatic Certificate Management Environment · checked 11-10-2026
- 10. GlobalSign Subprocessor List and Processing Locations v2.4 · checked 25-10-2026
- 11. GlobalSign Data Processing Addendum, revideret 30-05-2022 · checked 25-10-2026
- 16. EasyDMARC and GMO GlobalSign Partner, oktober 2026 · checked 25-10-2026
- 17. Regional Offices · checked 25-10-2026
support.globalsign.com
- 6. TLS Connect: Network Application & Cloud Provider Integrations · checked 25-10-2026
aws.amazon.com
- 12. AWS Customer Agreement · checked 25-10-2026
storage.pardot.com
- 13. TLS Connect Datasheet · checked 11-10-2026
gmogshd.com
- 18. GMO GlobalSign Holdings K.K.: Stock Status pr. 31-12-2025 · checked 11-10-2026