Draft is an open-source tool originally released by Microsoft that helps developers streamline the processes of developing container-based applications running on Kubernetes clusters.
N/A
SUSE Rancher
Score 9.2 out of 10
N/A
Developed by Rancher Labs and now from SUSE, Rancher is open-source software that enables organizations to deploy and manage Kubernetes at scale, on any infrastructure across the data center, cloud, branch offices, and the network edge. Rancher centrally manages Kubernetes clusters across the organization in order to ensure security and accelerate transformation. Rancher is also available hosted. Hosted Rancher is a fully managed Rancher control plane - presented as the fastest, most cost…
$7,594.99
per year up to 500 nodes
Pricing
Draft (open source)
SUSE Rancher
Editions & Modules
No answers on this topic
Subscription license
7,594.99
per year up to 500 nodes
Standard Subscription
11,234.99
per year 10 nodes
Priority Subscription
30,514.99
per year 10 nodes
Management Server Priority Subscription
41,830.99
per year 1 instance
Offerings
Pricing Offerings
Draft (open source)
SUSE Rancher
Free Trial
No
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Free and open source under an MIT license.
—
More Pricing Information
Community Pulse
Draft (open source)
SUSE Rancher
Considered Both Products
Draft (open source)
No answer on this topic
SUSE Rancher
Verified User
Anonymous
Chose SUSE Rancher
SUSE Rancher is an excellent choice for managing multiple Kubernetes clusters, especially when catering to different teams with distinct access rights and requirements. It allows us to deploy these clusters on-premises across various sites or in the cloud. However, if you’re …
We started using SUSE Rancher in the early days and spent a large amount of time getting to know and love it. This was before the days of some of the likes of Amazon Web Services who may now provide a cheaper but less feature-rich alternative to SUSE Rancher, however we have …
DevOps Architect for Containerization Platforms and Microservices
Chose SUSE Rancher
That is the one of the greatest values of Rancher. You can choose to add new features and functionalities to your environment by implementing other projects from SUSE, but you not forced to. You can use Longhorn as Persistent Storage, but you can use any other i.e. VMware CSI, …
As we use only AWS EKS Clusters originally we were using the AWS Console and CLI but that is too limited in scope. Also, we were using AWS IAM roles to provide access to users but that was lots of extra work to have them integrated into SSO while on Rancher we have just …
I find SUSE Rancher easier to use and configure with the features I want to really use. I'm finding more people in the community to help in getting support for the product. The other competitors seem to lock you too much into their own ecosystems and keep many needed details …
lens installs locally and needs access (network) to the kube_api of the clusters. With Rancher, you need access to the rancher front end (UI / 443), and your clusters Kube API does not need to be exposed (even over a VPN or whitelisted ips). For security reasons, the rancher …
We were looking for an open-source solution for simply deploying and managing K8s on bare metal in both big and small environments. SUSE Rancher was the easiest to install. Rancher Kubernetes Engine (2) and K3s will give you just a plain simple Kubernetes environment. The …
SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.
No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
You cannot detach the Rancher-created Kubernetes clusters from Rancher management.
Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.
The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.
SUSE Rancher is an excellent choice for managing multiple Kubernetes clusters, especially when catering to different teams with distinct access rights and requirements. It allows us to deploy these clusters on-premises across various sites or in the cloud. However, if you’re dealing with only one or a few Kubernetes clusters, using SUSE Rancher might introduce unnecessary complexity. This is where EKS wins, as its native cloud based abilities are better suited to scale, support higher complexity and larger demand.
Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications