Services · Payara

Payara Server & Payara Micro

Run your Jakarta EE applications on a supported, open-source platform, without Oracle WebLogic licence costs or lock-in to IBM WebSphere or JBoss EAP. As a certified Payara partner, reseller and distributor, Svapna supplies Payara Enterprise subscriptions and designs, deploys, migrates and supports Payara Server and Payara Micro environments.

Back to all services

Why companies move to Payara

Lower total cost

Payara is open source with commercial support. You pay for support, not for per-core licences.

Standards, not lock-in

Payara implements Jakarta EE and MicroProfile, so your code stays portable.

A short hop from GlassFish

Payara Server is derived from GlassFish. GlassFish applications usually move with little change.

Enterprise support

Patches, security fixes and SLAs for production, on a defined release lifecycle.

Cloud-ready

Payara Micro runs the same APIs in a small runtime built for Docker and Kubernetes.

One JVM-to-app stack

With Azul, the Java runtime and the application server now come from the same vendor.

December 2025

Payara is now part of Azul

Azul, the enterprise Java runtime company, acquired Payara in December 2025. For teams running or evaluating Payara, this matters:

What it means with Svapna

One partner for the full stack: Payara on an Azul JVM, sized, deployed and supported together. We can also help you move off Oracle Java SE subscriptions while you leave WebLogic.

Azul Core, Prime, Intelligence Cloud and Java security →

Source: Azul — Payara acquisition FAQ

  1. One vendor, whole stack

    Application server (Payara) and Java runtime (Azul's OpenJDK builds), with one support path from the JVM to your application.

  2. A proven combination

    Azul's Java runtime has been embedded in Payara Server Enterprise since 2018: nearly eight years of joint work.

  3. A clear route off WebLogic and JBoss

    Azul and Payara are targeting migrations from Oracle WebLogic and IBM/Red Hat JBoss, plus commercial support for GlassFish and WildFly.

  4. Continuity

    Azul states that existing Payara support, pricing and SLAs continue unchanged, with any changes announced well in advance. The Payara brand stays.

  5. More investment

    Azul has said it will expand the Payara roadmap.

What we do

Deployment & Operations

Production-grade Payara environments

Installation and hardening of Payara Server for production: clustering with Deployment Groups, high availability, load balancing, SSL/TLS, connection pooling, JVM and throughput tuning, and zero-downtime rolling deployments with health checks. On-premises, private or public cloud, with infrastructure as code and CI/CD so every environment is reproducible.

Migration

Migration from legacy Java EE servers

Moving applications from Oracle WebLogic, IBM WebSphere, JBoss EAP/WildFly or GlassFish to Payara: assessment, compatibility testing, javax → jakarta namespace upgrades where needed, deployment descriptor changes and cutover planning with rollback at every step.

Microservices

Payara Micro for cloud-native Java

Breaking monolithic Java EE applications into MicroProfile services (Config, Health, Metrics, Fault Tolerance, JWT, OpenAPI) on Payara Micro. Containerised with Docker, orchestrated with Kubernetes, with health checks and observability built in.

Java runtime

Azul JVM alongside Payara

Moving from Oracle Java SE to Azul's supported OpenJDK builds, sizing the JVM for your workload, and keeping runtime and application server on one supported lifecycle.

Azul Java services

Support

Ongoing support and maintenance

Managed support for Payara environments: patch and CVE management, version upgrades, performance tuning, thread-dump and heap analysis, security reviews and incident response. Available as retainer or per incident.

Payara projects we have delivered

Java applications we built on Payara Server for these clients.

How an engagement works

01

Assess

Inventory of applications, servers, JDK versions and dependencies. Risks and effort estimate.

02

Plan

Target architecture, migration order, test strategy and a cost comparison with your current licences.

03

Pilot

One representative application migrated and running in staging.

04

Roll out

Remaining applications in waves, with parallel runs and rollback plans.

05

Run

Monitoring, patching and support under an agreed SLA.

Who this is for

Frequently asked questions

Can we buy Payara Enterprise through Svapna?

Yes. Svapna is a Payara partner, reseller and distributor: we quote and supply Payara Enterprise subscriptions together with our deployment, migration and support services.

Does the Azul acquisition change my Payara support contract?

According to Azul, no. Existing support, pricing and SLAs continue unchanged, and any changes will be announced in advance.

Will my GlassFish application run on Payara?

Payara Server is derived from GlassFish, so most applications move with little or no code change. We confirm this during the assessment.

How long does a WebLogic to Payara migration take?

It depends mostly on how much WebLogic-specific API your code uses. After the assessment we give you a firm estimate, starting with a pilot application.

Payara Server or Payara Micro?

Payara Server for traditional, centrally managed deployments and clusters. Payara Micro for containerised microservices. Many teams use both.

Do you support Payara Community?

Yes. For production we usually recommend Payara Enterprise for its patch lifecycle and vendor SLAs.

Do you work outside Italy?

Yes. We are based near Padua and work in English and Italian.

Tell us your server, Java version and deadline.

An engineer will review your setup and propose next steps.