macOS
Homebrewverified · 100%
brew install payaralocal Homebrew formula metadata
brew / rank 6709
Install payara with Homebrew
Java EE application server forked from GlassFish. Version 7.2026.10 via Homebrew; verified 2026-10-14.
install
Additional install commands
overview
Package summary
Java EE application server forked from GlassFish
Project links
Commands and aliases
- letsencrypt.py
history
Project history and usage
Payara Server is an open-source Jakarta EE and MicroProfile application server derived from GlassFish and developed for reliable development and deployment across on-premises, cloud, and hybrid environments.
Project history
Payara Server began in 2014, derived from GlassFish 4.1 after commercial support for GlassFish changed. It was developed as a compatible application server with continued fixes, features, and production support.
The project subsequently evolved with newer GlassFish generations and the Java EE-to-Jakarta EE transition. Payara Server now describes itself as an open-source middleware platform for Jakarta EE and MicroProfile applications deployed on premises, in cloud environments, or in hybrid environments.
Payara Micro complements the full server with a lightweight runtime for command-line, containerized, and embedded deployments, while Payara Server retains domain administration and full application-server workflows.
Adoption history
Payara Server was positioned as a supported, production-oriented successor for GlassFish users while retaining familiar Java EE administration and deployment concepts.
Its scope broadened with Jakarta EE, MicroProfile, cloud, container, and hybrid deployment support. The project is available as a community edition, while Payara also provides commercially supported enterprise distributions.
For application teams, its GlassFish lineage reduced migration friction; for operators, Payara added a maintained release and support model around the familiar domain-based server architecture.
How it is used
Developers deploy WAR and EAR applications to Payara Server, administer domains with `asadmin` or the administration console, and configure resources in the domain model.
Operators use `domain.xml` as the central domain configuration, with adjacent logging and environment configuration files. Clusters, instances, data sources, security settings, and application deployments are managed through the server's administration facilities.
Payara Micro is used when the same ecosystem is needed in a smaller command-line or container-oriented runtime.
Why package nerds care
Payara is notable because it packages a large standards-driven Java runtime whose behavior is shaped by Jakarta EE compatibility, MicroProfile support, domain configuration, Maven artifacts, container images, and the GlassFish code lineage.
Its packaging history also captures the enterprise-Java transition from Java EE to Jakarta EE and the practical difference between an upstream reference implementation and a production-focused downstream distribution.
Timeline
- 2014: Payara Server began as a project derived from GlassFish 4.1.
- 2015: The early Payara 4 line followed GlassFish-style versioning and compatibility.
- 2018: Payara Server 5 adopted the GlassFish 5 and Java EE 8 generation.
- Jakarta EE era: Payara evolved its platform around Jakarta EE, MicroProfile, containers, and cloud deployment.
Related projects
- Eclipse GlassFish is the upstream lineage and closest migration reference point.
- Jakarta EE and Eclipse MicroProfile define the principal application-platform APIs implemented by Payara.
- Payara Micro is the lightweight runtime in the broader Payara Platform.
Sources
security posture
Risk level: orange
formula declares a Homebrew service.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- formula declares a Homebrew service
Signals
- metadata:service
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Formula metadata declares a service or daemon block.
- Homebrew bottle metadata is available for 1 platform targets.
- Installs with 1 runtime dependencies.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
domain-dir/config/domain.xmlas-install/lib/templates/domain.xml
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
domain-dir/master-passwordas_install/nodes/<node-name>/agent/master-password
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
letsencrypt.py | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-11-04
manager version7.2026.10
manager updated2026-10-14
local dataok
upstreamnot checked
latest detectednot detected
- infoRelease/tag comparison is only available for GitHub repositories.https://www.payara.fishnone confidence
install metadata
Package metadata
| Package key | brew:payara |
|---|---|
| Version | 7.2026.10 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/payara |
| Homepage | https://www.payara.fish |
| Upstream docs | https://www.payara.fish |
| License | CDDL-1.1 OR (GPL-2.0-only WITH Classpath-exception-2.0) |
| Source archive | https://search.maven.org/remotecontent?filepath=fish/payara/distributions/payara/7.2026.10/payara-7.2026.10.zip |
| Last updated | 2026-10-14T13:06:56Z |
| Pulse | updated |
| Dependencies | openjdk |
| Bottle | available (on all) |
| Homebrew post-install | not defined |
| Service | declared |
| Caveats | You may want to add the following to your .bash_profile: export GLASSFISH_HOME=$HOMEBREW_PREFIX/opt/payara/libexec/glassfish export PATH=${PATH}:${GLASSFISH_HOME}/bin |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | payara |
| Version Scheme | 0 |
| Revision | 0 |
| Conflicts With |
|
| Requirements |
|
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment
- pkg.so package database
- pkgdb category and tag curation