Above 250 people
Armor Enterprise
For organisations past the limits of the standard plans: more than 250 staff, regulated data, subsidiaries and multiple domains, or a posture that has to survive an audit. We scope it, design it, and only then price it.
At your size the pricing page stops being the right conversation
We scope before we price, and we don’t apologise for it. Anyone giving you a number for an estate this size before looking at it is either guessing or planning to revise it later.
You have constraints a standard plan can’t answer: a regulator, a procurement process, subsidiaries with their own IT, and an auditor who wants documentation rather than assurances:
01 Procurement needs a signed SLA
With named contacts, response commitments and consequences. Not a web page with a support email on it.
02 The auditor wants evidence
Written policy, access records, log retention and a demonstrable control framework - produced on request, not reconstructed in a panic.
03 Nobody owns the whole estate
Different subsidiaries, different vendors, different standards, and no single view of where the exposure actually is.
| What an Enterprise engagement includes | |
|---|---|
| Everything below is included at one price. No setup fee, no per-incident invoice, no surprise line items. | |
| Discovery across every domain, system and office you run | phase one |
| Written architecture your board and your auditors can read | phase one |
| Unlimited sites and staff under one tenancy | ongoing |
| Custom contract, SLA and support hours | ongoing |
| Migration in phases, planned around your operations | phase two |
| Log export into your own SIEM | ongoing |
| Policy documentation mapped to what your regulator asks for | phase two |
| Training for your IT team so they aren't dependent on us | phase three |
| Named engineer and quarterly business review | ongoing |
| Incident response retainer, if you want one | optional |
| It costs less than buying it direct | ||
|---|---|---|
| Enterprise agreements are negotiated, not listed — with Cloudflare directly and with us. The difference is who sits across the table and how long the procurement takes. | ||
| What you want | Direct price | Tremhost |
| Contract | annual, negotiated overseas | annual, negotiated in Harare |
| Billing | USD, international | USD, local invoice and payment rails |
| Named engineer | account team, remote | an engineer who can come to your office |
| Onboarding | your project team | run by us, phased |
| Discovery cost | consultancy rates | credited against your first invoice |
| Locally accountable | Same global network, same tier of protection, negotiated and supported by a company you can drive to, with invoices your finance team can actually pay. | |
| Cloudflare list prices from cloudflare.com/plans. We are a Cloudflare partner and buy at wholesale across thousands of accounts, that is the whole reason we can charge less than you would pay going direct. | ||
Questions people actually ask
1. How much does Cloudflare Enterprise cost?
Cloudflare does not publish a price for Enterprise — its own plans page lists it as a custom contract. The number depends on how many domains you protect, your traffic, and which add-ons you need, such as API Gateway, advanced bot management or log delivery. Send us your domains and we will come back with a scoped quote rather than a guess.
2. Can I buy Cloudflare Enterprise in Zimbabwe?
Yes, through Tremhost. We are a Cloudflare partner based in Harare and provision Enterprise zones through our partner tenant, so you contract, pay and get support locally — in US dollars, on local payment rails, from engineers in your time zone.
3. What is the difference between Cloudflare Business and Enterprise?
Business adds PCI DSS 4.0, SOC 2 Type II, custom SSL and a 100% uptime SLA with 1× service credits. Enterprise keeps all of that and adds advanced WAF and rate limiting, advanced DDoS protection, API Gateway, enterprise bot management, log delivery, Customer Success support, up to 1,000 WAF rules instead of 100, and service credits of 10× — or 25× on Premium.
4. Is there an uptime SLA on Cloudflare Enterprise?
Yes. Cloudflare Enterprise carries a 100% uptime SLA with 10× service credits on the standard contract and 25× on Premium, according to Cloudflare's published plan comparison. We will walk you through exactly how credits apply to your contract during scoping.
5. Why buy through Tremhost instead of directly from Cloudflare?
Same product, same network. What changes is who you deal with: a Harare team that runs the onboarding, handles first- and second-line support, invoices you locally and can sit in your boardroom — with escalation to Cloudflare behind us when something needs it. For most African organisations that is the difference between a stalled procurement and a live deployment.
6. Can we test it before we sign?
Yes. We run proofs of concept in our not-for-resale Cloudflare environment, so you can see it working against your own application before any contract is in place.
7. How long does onboarding take?
A single well-documented domain can be live within days. A bank or ministry with dozens of domains, internal applications and a change-control board is a phased project over several weeks. The scoping call gives you a dated plan, not an estimate.
8. Do we need Enterprise, or is Business enough?
Many organisations are well served by Business. You likely need Enterprise if you expose APIs to partners or mobile apps, fight persistent bot abuse on login or checkout, need log export for a regulator or SOC, or have uptime commitments to your own customers. Use the checklist on this page — we will also tell you honestly if a smaller plan fits.
9. Which organisations do you work with?
Banks and microfinance institutions, insurers, telecoms and ISPs, government ministries and parastatals, universities, mining houses, NGOs, e-commerce and fintech — anyone whose website, APIs or staff access carry real money or regulated data.
