Payara Cloud is becoming part of Payara Qube family of Java application deployment runtimes. This move reflects how the two solutions have grown and expanded to address the same enterprise needs, such as quick, simplified deployment and compatibility with the different enterprise Java frameworks that are part of most companies’ tech stacks.
While nothing will change from a technical perspective for our users, let’s see what you’ll see changing over the next weeks as well as how to deploy your first application in minutes with Payara Qube.
Introducing the Payara Qube Family
We’re bringing Payara Cloud under the Payara Qube name to form one unified product family. From now on:
Payara Cloud will be referred to as Payara Qube Managed – The fully managed service. We host and operate everything so you can focus on building applications.
Payara Qube will be referred to as Payara Qube Self-Hosted – Install and run the platform on your own Kubernetes infrastructure for complete control.
This change reflects how both platforms have evolved to meet the same goal: simplifying how you deploy and manage enterprise Java applications. You’ll still get everything you love, such as smooth deployments, automatic scaling and deep visibility. Both options simplify deployment by automating infrastructure provisioning. No manual server management, no container wrangling, no Kubernetes cluster headaches.
What’s changing
The name. That’s it.
Your access, features and capabilities remain identical. If you’re using Payara Cloud today, you’ll see the new Payara Qube (Managed) branding roll out over the coming weeks.
What’s staying the same
Everything else:
Deploy WAR, JAR, and ZIP files through the Console or CLI
Automatic SSL/TLS, routing, logging, and monitoring
Support for Jakarta EE 8/10, Spring Boot, and Quarkus
Pay-as-you-go, Standard, and Premium subscription tiers
Horizontal scaling and custom domains
Why this matters
Recently, when customers asked us about the difference between Payara Cloud and Payara Qube, the answer was always about where it runs, not what it does. Both platforms solve the same problem: getting your Java applications deployed without drowning in infrastructure complexity.
The new naming makes that clear. Pick Managed if you want us to handle operations. Pick Self-Hosted if you need full infrastructure control. Either way, you get automated deployments, built-in monitoring, and time back in your day.
Getting started
New to Payara Qube (Managed)? Get started today through the following steps:
Step 1. Develop an Enterprise Java Application
You can create a new enterprise Java application using your preferred tools. As the latest version of Payara Qube (both Managed and Self-Hosted) supports Jakarta EE, Spring and Quarkus frameworks, you can use a broader variety of tools, such as Payara Starter, Spring Initializr, or any standard project setup that produces a .war/.jar file.
Already have an enterprise Java project? Package it and get ready to deploy directly.
No application yet? If you prefer to use an existing application but don’ have one, feel free to use this sample application based on Jakarta EE to explore Payara Qube Managed.
Step 2. Log into Payara Qube Managed
Head to Payara Qube Managed console and log in with your account. If you used Payara Cloud before, your credentials and setup still work.
Step 3. Upload a New Application
You need to add your application to your Payara Qube Managed space. Here’s how to do it:
After logging in, you should see your namespace. Enter it
If no namespace is available, create one
Once in the namespace, click the hamburger menu (Namespace Actions) on the namespace page (top right)
Select “Upload Application” from the dropdown menu
Navigate to where you saved your application file and select it
Click on ‘More options’ drop down and enter a descriptive name related to your application in the “Application Name” field
Leave the “Deploy Immediately” checkbox unchecked
Click the “Upload” button
Step 4. Configure Your Application
After uploading, you’ll be taken to the application management page. In the Top bar, the application status will display as “Pending” and the “Application URL” will show “Not yet available” since the application hasn’t been deployed yet.
Click the hamburger menu (Namespace Actions) on the application page
Select “Edit Configuration”
For this project, let’s leave the ‘Rolling upgrade’ Scalability type selected and let’s not change any of the other default values. Scroll down to find the “Context Root Path” field
Change the value to match the application name you entered earlier but leave the / in front
Click the “Save” button
Step 5. Deploy Your Application
Now, it’s time to deploy your application. Deployment on Payara Qube Managed is fast and fully automated, meaning there is no need to handle servers or containers manually. Once you upload your build, the platform handles the rest for you.
Back on the application management page, click the hamburger menu (Namespace Actions)
Select “Deploy Changes”
Payara Cloud will begin deploying your application. Within moments, your app will be live. Once the deployment is completed, the page will reload, showing show the application URL and runtime size. Also, the top bar will update to display the Status as “Running” in green.
That’s it! No time-consuming Kubernetes cluster setup and configuration! You can now monitor your application and/or move on to other development tasks!
What’s Next
Our goal is to help you simplify, making the deployment of Java applications effortless. If you’ve tried Payara Cloud in the past, now’s the perfect time to return, check the updated experience and see what’s new in Payara Qube Managed.
Payara Qube
Payara Qube empowers enterprises to modernize, deploy, and manage Java applications across any cloud—without Kubernetes complexity or vendor lock-in. It’s designed for teams who want the scalability, resilience, and automation of a Kubernetes platform with the simplicity and performance of a fully managed runtime.
6 minutes
