Apyrn One installs and upgrades through Helm, so the version that runs and the moment it lands are both your team's decision.
Result and contract
- Upgrade timing
- Chosen by your team
- Controlled
Apyrn One Enterprise
Run Apyrn One inside your own environment.
Apyrn One turns your ERP, CRM, and database systems into governed APIs and agent tools. Enterprise installs it in your infrastructure with Helm, keeps the encryption keys with you, and runs on an offline licence where sites have no outbound connectivity.
A manufacturer runs the control plane inside a plant network with no outbound connectivity, on an offline licence, with its own keys.
Apyrn One Enterprise
See what stays inside your boundary
Four things change when you operate the environment yourself — where it installs, who holds the keys, which sites can run disconnected, and who reviews a change before it lands.
Select a concern to see where the responsibility sits.
Customer-managed keys mean Apyrn does not hold them, which is what key-custody requirements usually turn on.
Result and contract
- Key custody
- Customer-managed
- Held by you
Offline licences validate without calling out, so a plant network or a restricted site runs the same software as the connected estate.
Result and contract
- Licence
- Offline, validated locally
- Active
The estate and context graph records systems, dependencies, and the impact of a proposed change, so a decision is made on evidence and stays auditable afterwards.
Result and contract
- Impact
- Consumers and contracts affected
- For review
Guided explanation
The customer problem
The customer problem
Regulated, disconnected, and air-gapped enterprises need the control plane inside their own boundary, with their own key custody and their own upgrade process.
The better operating model
The better operating model
Apyrn One Enterprise installs into the customer environment with Helm, uses customer-managed keys, and supports offline licensing for sites with no outbound connectivity.
The solution approach
The solution approach
Map the estate, review the impact of a proposed change, record the decision, then install and operate inside your own boundary.
Conceptual architecture
- 01
Installs into the customer environment with Helm; the customer controls upgrade timing.
- 02
Customer-managed keys, so encryption keys stay in the customer's custody.
- 03
Offline licences support disconnected and air-gapped installations.
- 04
The estate and context graph records systems, dependencies, and the impact of a proposed change for review.
Enterprise examples
A manufacturer runs the control plane inside a plant network with no outbound connectivity.
An architecture team reviews the impact of retiring a system before approving the change.
A group compares two estates while integrating an acquisition.
What this enables
Keep the control plane, its data path, and its keys inside your own environment.
Review the impact of a modernization decision before committing to it.
Operate the same API products and Business APIs as the hosted edition.
Scope and qualification
Deployment topology, identity path, and operational responsibility are confirmed for each installation.
The customer operates the environment; Apyrn provides the software, upgrades, and support.
Where it runs
The data path, the keys, and the upgrade timing stay inside your boundary.
Apyrn One Enterprise installs into your own environment. Apyrn provides the software, the upgrades, and support; your team operates the environment, holds the encryption keys, and decides when an upgrade happens.
Installation and custody
Built for environments that cannot call out.
Helm installation
Install and upgrade through Helm into your own cluster, on your schedule rather than ours.
Customer-managed keys
Encryption keys stay in your custody. Apyrn does not hold them.
Offline licences
Licences that validate without calling out, so disconnected and air-gapped sites can run the same software.
Hybrid operation
Run connected and disconnected sites against the same published API products, with the topology confirmed for each installation.
Understanding the estate
Decide what should change before changing it.
Estate and context graph
Record the systems in the estate, what depends on what, and the business meaning attached to each, as reviewed evidence rather than a guess.
Change impact
See what a proposed change touches — which consumers, which contracts, which downstream systems — before approving it.
Decision gate
Record the modernization decision, who approved it, and on what evidence, so the decision is auditable later.
Estate comparison
Compare two estates side by side, which is what an acquisition or a group consolidation actually requires.
How it fits together
The same plane, operated by you.
One plane, two editions
Apyrn One carries both editions. The difference is which side of your boundary the environment sits on, who holds the encryption keys, and who decides when an upgrade happens. App Studio attaches to either one.
Operating foundations
Govern, secure, and observe the environment you run.
Governance
Define ownership, lifecycle, version, policy, approval, and consumer boundaries for every API product.
Security
Design least-privilege source access, consumer authorization, data boundaries, and policy enforcement into API products.
Observability
See API product health, source dependencies, consumer usage, policy outcomes, provenance, and change impact.
The capabilities and Business APIs are the same in both editions.
The five Apyrn One capabilities, the six Business API accelerators, and the solution journeys apply whichever edition you run.
Talk to us about running Apyrn One in your environment.
The conversation starts with your deployment topology, your identity path, your key custody requirements, and whether any site needs to run offline.