OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
The Salesforce Platform is designed for building and deploying scalable cloud applications with managed hardware provisioning and app stacks. Lightning Web Components are used by developers to build reusable UI components.
$25
Per User Per Month
Survicate
Score 8.5 out of 10
N/A
Survicate is survey software for getting continuous customer insights at scale. It can be used to measure customer satisfaction (CSAT), track an organization's Net Promoter Score (NPS), get website feedback, or test product-market fit. Survicate supports any use case related to collecting and managing customer feedback. Survicate can be used to: • Create customized surveys and start getting customer feedback within minutes • Run surveys where they are needed: via email…
Additional fees apply for additional users and domains. The price of the Scale plan is negotiated individually and depends on the number of monthly responses needed and possible custom needs, including integrations.
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
If you have a large customer base and a large amount of data on each of your customers, it is really strong in creating personalized content that your salespeople can use in their pitch meetings—and then setting up workflows for automated for lifecycle journey creations to automatically go out to customers.
Survicate is well suited for very basic intercept polls and is less suited for more complex surveying tasks (e.g., anything more than basic skip-logic or surveying niche cohorts) and longitudinal surveying (e.g., comparing responses from the same or similar cohorts year over year).
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
I wouldn't necessarily say there is look everyday technology transform. I can see a trend wherein Red Hat OpenShift is adopting all the new technology trends and helping their customers align with their priorities and the emerging technology trends. I wouldn't call out various scope for development every day. There is scope for development. It is all how the organizations adopt it and how they deliver it to their customers. I don't want to call out there is scope for development. It's happening. It is a never ending process.
At the moment, I don't have anything to call out. We are experiencing Red Hat OpenShift and we can see every day they're coming up with new features as and when they come up with new features, we want to experience it more and more. We are looking for opportunities wherein this can be leveraged to help our users and partners.
In my opinion, inconsistent and visually unappealing survey visuals (e.g., NPS and cSAT questions look completely different from each other, creating a disjointed visual experience)
Poor customer service (in my experience, issue resolution can take weeks)
Lack of clarity around API & other technical capabilities requiring engineering assistance
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
We use Survicate for now, over 7 years, and the tool is being constantly improved. New features and products has been introduced over the years. The team listens to our feedback we sometimes share, and improve the product based on that. We really appreciate being supported by the Customer Success, all the insights and help we got from them. And even though they introduced many new features over the years, the tool still remained super easy to use, even from new employees that join our team
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
It's very good, but it's still living in a little bit in an older design aspect, but I think a lot of it is about to come out, just hasn't quite gotten there yet. Still a little clunky from a you have to know it to know it or you know it to use it. It takes a little bit of training to get into it. It's not quite the, anybody can come in and start using it immediately, type feel.
It's rare to use products that offer wide range of features, and yet are really ease to use. Over the years, the product has changed a lot, they introduced numerous new features, but the product remained really simple to use. We know it, because new employees who join our team, have no problem in starting to use Survicate on their own, without and dedicated training. The UI is really clear.
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
I am not an administrator so there may very well be outstanding Support and I am just not privy to it. On a user level it's hard to gauge the effectiveness and responsiveness of Support because nearly everything has to go through an administrator
We had a lot of issues during implementation that required help from Survicate's engineers. In my experience, it took us over 4 weeks to be fully up and running due to lag times in communication.
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
Setup was simple. One-time installation for our website and inside the product. We used Google Tag Manager to implement Survicate. So within 2 hours, we were able to run surveys, and also all attributes and events were passed to Survicate, so that we were able to use them to trigger surveys
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
We were previously using an older version prior to it becoming Salesforce Lightning Platform so we were well adverse on the advantages of using a CRM, to begin with. It made sense to convert to Salesforce Lightning Platform after we were given a free trial of the platform. Certain reps were chosen to experiment with it and from there a decision was made to move forward. We've been customers ever since.
Considering the simplicity of the need, and the cost of such solution (~600$/yr), I don't think there was very deep research for any alternatives. The main alternative was embedding a feedback tool "organically" into our site, that option was taken off the table, for strategic considerations.
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
All of the above. Red Hat OpenShift going into a developer-type setting can be stood up very quickly. There's a very short period to have developers onboard to it and they're able to become productive much faster than a grow your own type solution.
We had a business need - to collect feedback on our support knowledge base content. Feedback Lite fulfills this need, with simple, easy to use, solution.
