Choose CloudFront when each customer needs meaningful infrastructure-level differences; choose Cloudflare Pages when a straightforward Angular build-and-deploy workflow and its domain limits fit your tenant model. Both can deliver a client-rendered Angular app, but neither removes the need to configure client-side route fallbacks. The key architectural difference is that AWS documents a shared CloudFront distribution template with separate distribution tenants, while Pages organizes deployments as projects with custom domains.
How do the tenant models differ?
CloudFront: shared configuration, separate tenant entry points
A CloudFront multi-tenant distribution is a reusable configuration blueprint, not the hostname that serves customer traffic. It holds shared origin, cache, and security settings. Each distribution tenant is a viewer-facing entry point that inherits those settings and is associated with a connection group. DNS for a tenant’s domain points to the connection group’s CloudFront routing endpoint.
As an Amazon Associate I earn from qualifying purchases.
AWS documents tenant-specific controls that can include origin and origin-path parameters, WAF web ACLs, geographic restrictions, invalidation paths, supplemental TLS certificates, and domain names. That makes this model relevant when customer sites share an application but need selected differences in origin or security policy. AWS also lists features that multi-tenant distributions do not support, including continuous deployment; its documentation specifies Origin Access Control (OAC) rather than Origin Access Identity (OAI). Check the current unsupported-feature list and quotas against your design before committing to this model.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsCloudflare Pages: projects and custom domains
Pages provides a documented Angular build workflow, Git-triggered deployments, pull-request previews, and custom domains. Its documented scale model is based on Pages projects and the number of custom domains attached to each project, rather than an equivalent shared distribution-tenant resource. That can suit a team whose tenants mainly need domain mapping to a deployed application, but domain and project ceilings become part of the architecture.
#1 Best Overall
How do you deploy an Angular app to Cloudflare Pages?
- Create or connect the application. Cloudflare’s Angular guide documents bootstrapping with its C3 command or connecting a GitHub or GitLab repository. Connecting Git enables deployment on pushes and preview URLs for pull requests. Git integration cannot be added to an existing Pages application; create a new Pages application if that workflow is needed.
- Set the build command and output directory. The guide gives
npm run buildanddist/cloudflareas settings, while noting that some Angular versions neednpx ng build --output-path dist/cloudflareand the output directorydist/cloudflare/browser. Confirm the actual generated directory in your project rather than assuming one path works for every Angular version. - Deploy and verify the built site. Use a pull-request preview to review changes, then check the production deployment. Test both the root page and direct navigation to routes in the deployed app; a successful build alone does not prove that Angular deep links will load on refresh.
- Associate each customer hostname in Pages. Add custom domains through the Pages dashboard flow before routing traffic. For a subdomain, configure a CNAME to the project’s
pages.devhostname. A manually created CNAME without adding the domain in the Pages dashboard can fail with a 522 error.
How do CloudFront customer domains and certificates fit together?
For a CloudFront multi-tenant deployment, configure the domain at the distribution-tenant level and route DNS to the connection group’s routing endpoint. Do not treat this as identical to adding an alternate domain to a standard CloudFront distribution.
For the standard distribution workflow, AWS documents adding the alternate domain name, attaching or creating a valid ACM certificate, validating domain ownership through DNS, waiting for the distribution to deploy, and then routing DNS to it. The console workflow references ACM certificates in us-east-1. A Route 53 alias record can serve an apex domain, where an ordinary CNAME cannot be created. In either model, establish who controls the tenant’s DNS and certificate validation before choosing an onboarding process.
Will Angular routes work after a refresh?
Angular’s client-side router cannot handle a direct browser request until the server returns the application’s host page. Angular’s deployment guidance says to configure the server to return index.html when asked for a file it does not have. Without that fallback, a route may work when reached by clicking inside the app but fail when opened directly or refreshed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Cloudflare Pages supports file-based redirects in a plain-text _redirects file in the static asset directory. Those rules apply to static asset responses, not requests served by Pages Functions. Do not assume that adding a redirect automatically supplies the correct Angular app-shell fallback in every Pages setup. Test copied deep links and refreshes on the deployed site, including any routes handled by Functions.
Rank #3
What Pages limits matter when planning tenant scale?
Cloudflare’s limits documentation, last updated September 5, 2026, lists the following Pages limits. They are current documented limits, not permanent guarantees; recheck them before sizing a deployment.
| Plan | Projects per account | Custom domains per project | Builds per month | Concurrent builds |
|---|---|---|---|---|
| Free | 100 | 100 | 500 | 1 |
| Pro | 100 | 250 | 5,000 | 5 |
| Business and Enterprise | 100 | 500 | 20,000 | 20 |
Pages builds time out after 20 minutes. The same limits documentation allows up to 20,000 files on Free sites and up to 100,000 on paid plans when using a Wrangler environment setting; an individual asset is limited to 25 MiB. Cloudflare directs users with more than 100 sites toward Workers for Platforms or Workers Static Assets.
Map your tenant model before interpreting these ceilings: one tenant might mean one Pages project, one custom domain on a shared project, or a combination. The 100-project account ceiling and per-project domain cap constrain those designs differently. CloudFront also has quotas and unsupported features for its multi-tenant model, so a domain-count comparison alone is not enough to choose between the services.
Which hosting design fits your team?
- Prefer CloudFront’s multi-tenant model if tenants need selected differences such as origin paths, WAF policies, geographic restrictions, or tenant-level certificates, and your team can operate the AWS configuration and deployment pipeline.
- Prefer Pages if its Angular build workflow, Git-based previews, and domain association process suit your team, and your project and custom-domain needs fit the documented ceilings.
- Resolve DNS ownership early. Pages apex domains require the domain to be a Cloudflare zone with Cloudflare nameservers. Pages subdomains can use CNAME records. CloudFront custom domains require a covering TLS certificate and DNS routing; the apex can use a Route 53 alias.
- Test the deployment behavior that matters. Confirm a tenant’s hostname resolves to the correct app, direct Angular routes survive refresh, and any application-specific security or routing configuration works in the chosen provider.
Neither platform is inherently the better CDN for this use case on the available documentation: no comparative performance or cost testing establishes that. The practical decision is whether tenant-specific infrastructure controls or a managed Pages build-and-domain workflow better matches your operations, DNS arrangements, and expected scale.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
