Aptible Deploy (formerly Aptible Enclave) is a container orchestration platform built for developers that automates security best practices and controls needed for deploying and scaling Dockerized apps in regulated industries. Aptible Deploy is ISO 27001-certified and can be used to support requirements for HIPAA, ISO 27001, SOC 2, NIST 800-53, and other frameworks.
N/A
Forcepoint CASB
Score 7.4 out of 10
N/A
Forcepoint CASB delivers comprehensive security for SaaS and Generative AI applications by combining API integration with real-time inline controls, ensuring sensitive data stays protected without compromising performance or user experience.
N/A
Red Hat OpenShift
Score 9.2 out of 10
N/A
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.
I would recommend Aptible Deploy to my colleagues because of its responsiveness and efficiency for environment and application provisioning. The product is extremely useful for creating health applications due to its built-in security and compliance protocols for HIPAA and HITRUST. The automated database backups were also a nice touch for failover scenarios, as is the included horizontal scaling. The horizontal scaling automatically defaults toward high availability as well.
It is appropriate for medium to large-scale enterprises, especially the ones that have remote employees. The live-monitoring feature is extremely useful in this case. However, the implementation and initial processing are headache-inducing so you definitely need a dedicated IT team. Be warned though, that not only is their interface quite complex, their customer service is also extremely unhelpful so you won't be able to implement this or tackle any issues without a skilled team. But if that isn't an issue, this is definitely worth a try!
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.
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.
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
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
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 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.
Aptible makes managing HIPAA/HITRUST compliance simpler when compared to Microsoft Azure. Passing audits is technically easier when using Aptible. Aptible provides a log drain to deliver logs via Syslog or HTTPS for long-term log storage. Microsoft Azure does not have a portal specifying when controls are in place, something which Aptible does.
The interface of both the softwares is complex, but Forcepoint is certainly more complicated. But once you get past that, it is quite smooth and offers a lot of amazing features. It is one of the best options for remote security, although I would love to see more features - like encryption. The one place where it truly lacks is customer service, and since it has such an intricate implementation procedure, this one carries a lot of weight and needs to be improved to make this software even more accessible.
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.
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
Less time in configuring servers. This is essentially a server-less platform.
Cost savings by using usage-based cloud
CLI can be scripted to provide full automation, even though a deployment takes about 20 minutes; that time can be even further reduced and spent elsewhere
We are working on strategies to understand what to do with the information that CASB gave to us, it would be good if Forcepoint gives us a few key points but they haven't.
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.
