Public
For catalogs intentionally published to the open web. The browser fetches JSON and labels the deployment-selected source.
- Open HTTPS endpoint
- Cross-origin access enabled
- No browser credentials
The Portal Registry
One bazaar.
Many sovereign skies.
AX is not bound to one storefront. A deployment chooses its catalog sources, AX presents each listing, and package or host operations remain separate.
Public · Private · Intranet
Choose the boundary
before the catalog.
The interface is shared. Network reach, catalog selection, and persistence belong to the deployment around it.
Private
Requires a dedicated deployment
For organization collections and private GitHub repositories. Credentials stay in a host-owned gateway, co-hosted boundary, or Core-owned broker.
- Organization-owned host
- No token-bearing browser URLs
- Catalog details remain descriptive
Intranet
Requires a dedicated deployment
For military, SDE, clinical, enterprise, or disconnected systems whose private inventory never belongs on the public Pages deployment.
- Dedicated origin and network
- Local catalog
- Private inventory stays private
The portal keeper’s rules
What crosses the gate and what never should.
- 01
Configuration chooses the source.
Built-in, private, and custom source labels come from the deployment that selected the catalog.
- 02
Catalog content stays inert.
Names, descriptions, categories, and links render as plain text. Remote scripts, markup, styles, icons, and screenshots do not enter the bazaar.
- 03
Secrets never ride in URLs.
Do not enter tokens, passwords, or other credentials in public catalog URLs. Private access belongs to the deployment host.
- 04
Discovery is not delivery.
Listings do not install, launch, update, or grant permissions. Those operations remain outside this marketplace view.
For SDE, military, clinical, and enterprise systems
Build a private market,
not a public leak.
Keep nonpublic app names, catalog snapshots, customer data, intranet hostnames, and credentials out of this repository and its Pages artifact. Deploy AX on a dedicated origin beside the network controls your mission already governs.