The clients mainly were using Proofpoint for email security, which is the primary use case.
We have used Proofpoint for email security.
External reviews
8 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Significant email security benefits combined with efficient spam filtering, yet cost hinders long-term use
What is our primary use case?
What is most valuable?
Spam filtering from our partner perspective was very efficient; we were very happy with the functionality, as only relevant emails were allowed for mailboxes.
We used the Sandbox feature, and it was very beneficial concerning the Advanced Threat Protection feature.
From a business perspective, it was very helpful; it sped up our business flow and increased email delivery, and from a technical perspective, it was very effective.
What needs improvement?
Pricing might be a topic to consider regarding improvements.
I may advise Proofpoint to adjust marketing solutions based on each country itself.
For how long have I used the solution?
I had experience with Proofpoint for more than 5 or 6 years.
What was my experience with deployment of the solution?
Everything was very nice from a technical perspective, and we were very happy, especially since we used it for more than 5 or 6 years.
Everything was fully functional, and I cannot think of advanced features; all existing features were very suitable for our business flow.
What do I think about the stability of the solution?
It was very stable, so I would rate it as excellent.
It was very fast, and we did not experience any interruptions.
What do I think about the scalability of the solution?
The scalability of Proofpoint was excellent and very scalable.
How are customer service and support?
Technical support from Proofpoint was absolutely excellent.
We were very satisfied with the performance and efficiency of the product.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We are still using Microsoft Exchange, but left Proofpoint.
We stopped using this product last year, approximately ten months ago.
How was the initial setup?
The product was very straightforward to install; it was very easy because we used the web interface, and simple settings definitions on the ISP site were enough for the whole setup.
What about the implementation team?
At the very beginning we were working directly with the UK, but then we were redirected to a local partner, and we worked almost one year with the local partner.
We used to get a business partner in my country.
What's my experience with pricing, setup cost, and licensing?
The pricing deserves a high rating for consideration.
Cost was the reason we stopped using it.
Pricing was the issue as it becomes very expensive due to the nature of local circumstances.
What other advice do I have?
The integration with our on-prem Exchange was very straightforward; the only thing we did was redirect all email traffic over Proofpoint, so Proofpoint did everything independently, and we were very happy.
I am still receiving emails from Proofpoint's site.
Not using it at the moment, but in the short term we will be tackling that portion of the product as well.
We cannot provide feedback regarding Dynamics because we are not experienced enough at the moment; we have initiatives going on but did not get enough feedback from end users.
Based on my overall experience with Proofpoint, considering the cost perspective, I would rate it a 7 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Deploy and manage API solutions efficiently with centralized hybrid systems
What is our primary use case?
I use Kong Konnect as an API Gateway or API management solution. I have several use cases, including securing internal APIs within Siemens network by deploying Kong Gateway on Amazon EKS. This acts as an API management layer to expose other internal services such as logging and Jira APIs. Additionally, I utilize it for external use cases by deploying an API Gateway for consumers accessing services from the internet. My aim is to create a federated API management platform where various business units can still use their preferred choice of gateways while maintaining a central federation layer to control security and logging policies.
What is most valuable?
Kong Konnect is a SaaS version of Kong Gateway, and it offers a hybrid deployment. The configuration can be controlled centrally via the SaaS offering, and each team can manage their own gateway or runtime part. It is lightweight, suitable for smaller use cases without heavy initial costs, and comes in various flavors such as open source and enterprise. The documentation is excellent, and it includes a developer portal, which helps create a common distribution channel for APIs within and outside the enterprise.
What needs improvement?
Kong Konnect's RBAC needs to evolve more, as they currently offer only one or two levels of RBAC in terms of organization and teams. Additionally, the licensing model could be simplified, especially in how they charge and track usage. There are also some technical restrictions around exposing GRPC APIs, but I have not explored this yet.
For how long have I used the solution?
I have been working with Kong Konnect for the last six or seven months.
What was my experience with deployment of the solution?
The deployment is straightforward because it's a hybrid model. The control plane is a SaaS offering, so there's not much difficulty there.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The platform is fully scalable, providing various ways to manage data planes or runtimes. They offer managed runtimes, but it's preferred that consumers manage their own runtime, which can be deployed in a containerized manner.
How are customer service and support?
The technical support from Kong is satisfactory.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I was previously using Azure Logic Apps but moved to Kong API Gateway. This decision was influenced by the need to create a service around Kong API Gateway with a federated API management platform.
How was the initial setup?
The initial setup is very straightforward due to its hybrid deployment model, with the configuration and control plane managed as a SaaS offering.
What was our ROI?
I have not yet seen a return on investment because the project is still in its early stages.
What's my experience with pricing, setup cost, and licensing?
While the pricing model isn't very clear on how usage is tracked, the initial cost and setup for using Kong Konnect are reasonable.
What other advice do I have?
The knowledge base provided by Kong is excellent, offering various learning paths not just for the technical aspects of Kong Konnect, but also for innovation within the application. It's a highly customizable platform. I would rate Kong Konnect an eight overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
A fast API managent solution
What do you like best about the product?
It is a very easy and with a vast range of features tool, and it could be integrated with many cloud environments, and on premises as well.
What do you dislike about the product?
There are some wrong documentation, a high dependency of some beta plugins, and quite high costs.
What problems is the product solving and how is that benefiting you?
Rate limiting, microservices orchestration, api security, integration of apps.
1 person found this helpful
Konnect - Kongs SaaS Offering
What do you like best about the product?
Quick and Easy to start deploying APIs.
Provides different deployment options Hybrid and SaaS.
Provides different deployment options Hybrid and SaaS.
What do you dislike about the product?
Lack of monetization feature within the Developer Portal.
What problems is the product solving and how is that benefiting you?
Konnect helped in setting up a full fledged API gateway in minutes.
Kong Konnect API Management with the power of cloud
What do you like best about the product?
Can have our API deployed and live within a few minutes with dedicated cloud gateway.
Integration with third party application like amazon cognito and okta.
Integration with third party application like amazon cognito and okta.
What do you dislike about the product?
Low transparency of data kong is storing for our APIs.
What problems is the product solving and how is that benefiting you?
Prebuilt developer portal allowed us to easily publish APIs to the outside world.
A powerfull and fully featured API orchestrator
What do you like best about the product?
A very powerful orchestrator to manage lots of API products and leveraging the full power of API Gateway, Service Mesh, Kubernetes and other related tools, easily m,anaged from a nice web UI. You can count with Kong support to make sure your API products will be successfull.
What do you dislike about the product?
Almost nothing, but the documentation could be a little more intuitive.
What problems is the product solving and how is that benefiting you?
Kong Konnect allows you to easily manage sophisticated and complex API programs, involving multiple components necessary for modern microservices architectures.
Easy and Fast
What do you like best about the product?
Its very easy to configure. plenty of option available to run the data planes right from VMs to EKS etc.
What do you dislike about the product?
Nothing to dislike so far. its a new product and takes away a lot of complexies from on-prem Kong mesh/gateway platform.
What problems is the product solving and how is that benefiting you?
We use Kong konnect for API Management. It very easy chose from a large number of ootb policies to protect and govern our APIs.
Most of our policies are around security i.e. Authentication and Authorization and QoS.
Most of our policies are around security i.e. Authentication and Authorization and QoS.
Kong Konnect
What do you like best about the product?
Simple, open, automated and standards based. plug-in based modular
What do you dislike about the product?
Steeper learning curve when learning the more technical features
What problems is the product solving and how is that benefiting you?
Secure and services discovery
Kong Konnect- Get Up and Running Immediately
What do you like best about the product?
Very clean, simple interface, easy to spin up the API via service version, publish to the portal with swagger and can install runtime in your cloud account or on premises!
What do you dislike about the product?
Not so easy to ascertain the gateway address in UI, and the RBAC is a bit confusing
What problems is the product solving and how is that benefiting you?
service oriented architecture
showing 1 - 9