NGINX vs. SafeDNS

[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.

Incentivized

Without reinventing the wheel, SafeDNS is effective in preventing employees and customers from using our information material in an inappropriate way and this, by user group, because of course, we do not have the same needs from one department to another. I recommend it to any serious company that wants to limit access to certain types of websites that may be inappropriate or offensive. The application is not limited to that, but in our case, that's what we were interested in

Incentivized

• Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
• Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
• SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
• Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.

Incentivized

• Protecting sensitive data: By monitoring and controlling the internet activity on the back-end systems, the startup can protect sensitive data such as customer information, financial transactions, and other sensitive data.
• By using SafeDNS to monitor and control employee internet activity, a headless e-commerce startup can ensure compliance with regulatory requirements related to internet usage, such as data privacy and security laws.
• SafeDNS can be configured to block unwanted traffic, this can help to keep the server and the network resources in optimal state, and also it will help in preventing DDoS attacks

Incentivized

• Customer support can be strangely condescending, perhaps it's a language issue?
• I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
• It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
• It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
• I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.

• providing insight or suggestion on type of website that could be blocked
• providing more alerts and dashboard when you have huge teams to manage

Incentivized

Great value for the product

Incentivized

This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers

Incentivized

Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.

Incentivized

All of those are paid solutions with very good features, but they also offer dedicated scenarios for web application hosting. If you run applications on on-premises web servers and don't have a Microsoft licence agreement, Nginx is a very good and reliable option, based on Linux distributions and available as freeware.

Incentivized

One key difference between the two products is that SafeDNS is a cloud-based service, while WebTitan offers both cloud-based and on-premises options. This means that SafeDNS is typically easier to set up and manage, and can be accessed from anywhere with an internet connection, while WebTitan's on-premises option gives organizations more control over the deployment, configuration, and management of the service.Another difference is that WebTitan also provides features such as advanced threat detection, which can detect and block zero-day threats, and a feature that monitors and report on the user's activity, while SafeDNS primary focus is on internet filtering.In terms of pricing, SafeDNS's pricing model is subscription-based, whereas WebTitan offers a mix of subscription, perpetual and pay-as-you-go license options.

Incentivized

• Our websites are noticeably faster, causing an increase in customer satisfaction.
• Nginx has such a low memory/resource footprint that we save money from not needing multiple large, expensive servers.
• Ability to load balance traffic, have server-redundancy, and have high-availability allows for 100% uptime and provides cost-effective solutions to alternatives that can cost a lot.

Incentivized

• With an affordable cost it has a positive impact on our ROI.