Cloudflare One (SASE) vs. Google Cloud DNS

I wanted to securely connect to my servers without getting tracked by malicious attackers, even though I was on public Wi-Fi. Security was my top priority, and I also wanted a setup that was easy and quick to start and provided great network performance. Cloudflare's Zero trust matches my criteria for becoming my first choice.

Incentivized

Google cloud is well suited to access and collaborate on documents where more than 2 people are required to contribute and in instances where feedback from individuals is captured on the document itself. If a team is working on an end of year report for funders, a few key members may need to finalise a report by offering suggestions that can be viewed and resolved by other team members. Housing documents on Google Cloud is the most appropriate platform I have ever used for tasks like these. If minimal collaboration needs engagement from just 2 individuals, it may be easier to simply email the information between each other, rather than using time to create a folder, ensure access control and upload the information to Google Cloud for collaborative input

Incentivized

• Block access to known bad, risky, or unwanted destinations at the DNS or HTTP level.
• Excellent protection for remote users.
• Best in class browser isolation techniques.

Incentivized

• Interface is user friendly
• It is safe , Secure and reliable
• It has lower pricing plans
• They have good customer support
• They do have good documentation to have fair ideas on their offerings

Incentivized

• Cloudflare still need to improve CASB direction to complete set of SASE tools.
• More integrations with the third-party agents to check device posture in the Zero Trust framework.
• More granularity in firewall rules for full replacement of on-premise solutions.

Incentivized

• It is hard for first time user to get used to it.
• Support is restricted for 3rd party services who uses it
• Sometimes the support people take more than 24hrs to reply to our queries, But it is not for all issues.
• Search function could have been made easy to search records

Incentivized

Within a few hours, new engineers are trained in basic tasks and are quite happy they are able to resolve issues independently. After SSO is configured, onboarding is as simple as signing into m365 via a web browser popup.

Incentivized

This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.

Good chat support from the portal for basic questions and minor issues. The enterprise support line is provided as well.

In the event that you are utilizing Google Cloud Platform as your cloud supplier, Google Cloud DNS is unquestionably the DNS supplier to utilize.

I haven't required help for it yet, notwithstanding, in my experience, Google Support is incredible.

Cloudflare was both the most feature-rich and cost-effective of comparisons. Presales engagement understood our challenges and was keen to solve them.

Incentivized

Amazon Route 53 offers almost equal or slightly more features than Google Cloud DNS; we selected Google Cloud DNS because the rest of our projects use Google Cloud Platform.

Also, since AWS is a bigger service provider, their pricing is also higher; since Google Cloud DNS pricing is better, we went for it.

Incentivized

• The cost of Cloudflare Zero trust is much lower, hence reducing spending on infrastructure security.
• The Network performance is improved thanks to Warp protocol.
• Requires less maintenance and hence saves time.

Incentivized

• We use GCP for all our projects so Google Cloud DNS fits perfectly
• It is proving to scale well so good for us since we are a growing company
• It is easy to use and doesn't require a separate team to maintain

Incentivized