Cloudflare Access vs Cloudflare Gateway

Cloudflare Access controls access to self-hosted apps, SaaS applications, and infrastructure by checking identity, device posture, and other context on each request. Policies can grant access at the individual resource level, and applications deny access unless a user matches an Allow policy. It supports SAML- and OIDC-compliant identity providers, including enterprise and social providers, as well as Cloudflare as an identity provider. Contractors, partners, and people using unmanaged devices can connect through a browser with social sign-in or a one-time PIN. Access can replace or supplement a legacy VPN by limiting access to specific applications, and its controls also cover infrastructure such as SSH and RDP. Administrators can manage policies centrally and scale them through APIs and Terraform. Publishing a self-hosted public application requires an active Cloudflare domain with full or partial CNAME setup. The free plan is for fewer than 50 users; paid service starts at $7/user/mo (annual).

Cloudflare Gateway has no write-up on Specifiction yet; its figures are above.