At a glance.
| Apexly | Cloudflare for SaaS | |
|---|---|---|
| Starting price | ✓Free for 3 domains; $39/mo for 50. Launch: 20 domains free | ✓100 hostnames included, then $0.10 each |
| 300 live domains | $129/mo (Growth) | $20/mo (plus your Cloudflare plan) |
| Apex domains (acme.com) | ✓Yes: an A record and a TXT token, on every plan | ~Enterprise add-on (apex proxying or BYOIP); otherwise only if the customer's DNS flattens CNAMEs |
| Setup page for your customer | ✓Hosted connect page that detects 46 DNS providers | ✕None; you build the instructions |
| Status webhooks | ✓8 signed events, retried 7 times over about two days | ~Certificate events through Cloudflare Notifications |
| Host your app anywhere | ✓Yes | ✓Yes, with a fallback or custom origin |
| Your DNS stays where it is | ✓Yes | ✕Your SaaS zone must be on Cloudflare |
| CDN, WAF, caching | ✕No: we route and secure, we don't cache | ✓Yes, the full Cloudflare platform |
Which one is right for you.
Choose Cloudflare for SaaS if
- You already run your zone on Cloudflare and want its CDN, WAF and caching in front of customer domains.
- You have thousands of hostnames and the lowest per-hostname price matters most.
- You have engineers to build the customer instructions page, status handling and support flow.
- You're on Cloudflare Enterprise and need apex proxying anyway.
Choose Apexly if
- Your customers use apex domains and you're not on Enterprise.
- You don't want to move your DNS zone or put a proxy in front of your main app.
- You want a ready connect page and plain-language fixes your support team can forward.
- You want one domain state with one reason, instead of hostname and certificate validation tracked separately.
Compared on 18 October 2026 from public docs and pricing pages: Plans and pricing · Apex proxying · Getting started · Webhook definitions. Prices change; if something here is out of date, tell us at support@apexly.dev and we'll fix it. Product names are trademarks of their owners.