NGINX vs. Salt Security API Protection Platform

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
NGINX
Score 9.1 out of 10
Mid-Size Companies (51-1,000 employees)
NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…N/A
Salt Security API Protection Platform
Score 8.5 out of 10
Enterprise companies (1,001+ employees)
For API-driven organizations, Salt Security is an API security platform that protects internal, external, and third-party APIs. The Salt C-3A Context-based API Analysis Architecture combines coverage and AI-powered big data to discover APIs and exposed sensitive data - continuous and automatic discovery stop attackers in their tracks - block attackers by integrating with inline devices provide remediation insights - for developers to improve API security…N/A
Pricing
NGINXSalt Security API Protection Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
NGINXSalt Security API Protection Platform
Free Trial
YesNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
YesNo
Entry-level Setup FeeOptionalNo setup fee
Additional Details
More Pricing Information
Community Pulse
NGINXSalt Security API Protection Platform
Top Pros
Top Cons
Features
NGINXSalt Security API Protection Platform
Application Servers
Comparison of Application Servers features of Product A and Product B
NGINX
8.2
21 Ratings
3% above category average
Salt Security API Protection Platform
-
Ratings
IDE support7.310 Ratings00 Ratings
Security management8.018 Ratings00 Ratings
Administration and management8.018 Ratings00 Ratings
Application server performance8.618 Ratings00 Ratings
Installation9.418 Ratings00 Ratings
Open-source standards compliance7.916 Ratings00 Ratings
Best Alternatives
NGINXSalt Security API Protection Platform
Small Businesses
Apache HTTP Server
Apache HTTP Server
Score 8.2 out of 10

No answers on this topic

Medium-sized Companies
Apache Tomcat
Apache Tomcat
Score 8.8 out of 10
Postman
Postman
Score 8.8 out of 10
Enterprises
Apache Tomcat
Apache Tomcat
Score 8.8 out of 10
Akamai App & API Protector
Akamai App & API Protector
Score 8.6 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
NGINXSalt Security API Protection Platform
Likelihood to Recommend
8.9
(48 ratings)
8.5
(6 ratings)
Likelihood to Renew
9.1
(1 ratings)
-
(0 ratings)
Usability
9.0
(1 ratings)
-
(0 ratings)
Support Rating
8.1
(4 ratings)
-
(0 ratings)
User Testimonials
NGINXSalt Security API Protection Platform
Likelihood to Recommend
F5
[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.
Read full review
Salt Security
Salt is highly recommended for anyone who wants to discover, monitor and protect their APIs against various types of attacks. Salt should not be used as a SIEM.
Read full review
Pros
F5
  • Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
  • Great at serving static content.
  • Scales very well. Easy to host multiple Nginx servers to promote high availability.
  • Open-Source (no cost)!
Read full review
Salt Security
  • PII identification in API traffic.
  • Divergence between API traffic and documentation (swagger files).
  • Potential attacks with information to take counter measures.
Read full review
Cons
F5
  • 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.
Read full review
Salt Security
  • The platform could have more options for exporting detailed data from attackers' dashboards.
  • The Attackers dashboard could also have more options of filters in order to support the investigations of the attack.
  • The OAS analysis could present a more detailed view of the found issues.
Read full review
Likelihood to Renew
F5
Great value for the product
Read full review
Salt Security
No answers on this topic
Usability
F5
Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application. Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective. Also, Nginx doesn't delay any request because of internal performance issues.
Read full review
Salt Security
No answers on this topic
Support Rating
F5
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.
Read full review
Salt Security
No answers on this topic
Alternatives Considered
F5
We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because
  • we have a large number of services and we can manage a single Nginx instance for all of them
  • we have high impact services and Nginx never breaks a sweat under load
  • individual services have special considerations and Nginx lets us configure each one uniquely
Read full review
Salt Security
We tried controls offered by the IaaS providers but these were hard to manage and did not provide the visibility we wanted. We also protected APIs with a normal WAF but this was only helpful for assets we knew about and API attacks were not caught by the WAF.
Read full review
Return on Investment
F5
  • Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache.
  • Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy").
  • Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly.
Read full review
Salt Security
  • Salt Security API Protection Platform has provided detailed information that is helping us to identify and investigate attacks in our environment
Read full review
ScreenShots

NGINX Screenshots

Screenshot of Overview of the NGINX Application PlatformScreenshot of NGINX Controller - MonitoringScreenshot of NGINX Controller - Configuration