Deployment

One question decides the deployment — who runs the environment?

Apyrn One Cloud runs on infrastructure Apyrn operates. Apyrn One Enterprise runs inside your own environment, including sites with no outbound connectivity. Both publish the same API products; identity, data boundaries, networking, operations, recovery, and responsibility are confirmed for each installation.

Request a Cloud workspace Talk to us about Enterprise

Select a profile to inspect its approval questions.

Request and constraints

Approval focus: Product and managed boundary

Active scenario

Cloud

Managed cloud profile

Confirm product support, identity, data, network, evidence, support, recovery, and shared responsibility for the managed environment.

Result and contract

Availability: Confirmed per edition; Confirmed

Two editions

The same API products, operated by whichever party should operate them.

Nothing about the contracts you publish changes between the editions. What changes is who patches the gateway, who holds the encryption keys, and who decides when an upgrade happens.

Apyrn One Cloud

Apyrn runs the gateway, the connectors, and the scheduled synchronization, and keeps them patched. Your team configures connected systems, workspaces, API products, and agent access. Identity integration, audit export, and per-workspace scope are available to your administrators.

Apyrn operates the environment

Apyrn One Enterprise

Apyrn One installs into your own cluster with Helm and upgrades on your schedule. Encryption keys stay in your custody. The data path does not leave your boundary, and offline licences let disconnected and air-gapped sites run the same software.

You operate the environment

What the Enterprise edition can do

Hybrid and disconnected operation are Enterprise options, not separate editions.

Hybrid

Run some sites connected and others disconnected against the same published API products, with the split recorded per installation rather than assumed.

Offline and air-gapped

Offline licences validate without calling out, so a plant network or a restricted site runs the same build as the rest of the estate.

Customer-managed keys

Encryption keys stay with you. Apyrn does not hold them.

Upgrade control

Helm installation means your team chooses when a version lands, which is what change-controlled environments require.

Runtime architecture layer

Apyrn Runtime describes shared technical execution concerns, not another product.

Where the Runtime sits depends on the edition. In Cloud it runs inside the environment Apyrn operates; in Enterprise it runs inside yours. Its topology and responsibility boundary are recorded for each installation.

Before activation

Confirm the operating boundary.

01
Edition and topology
Decide which edition runs where, and for Enterprise, which sites are connected and which run offline.
02
Identity, data, and network
Document identity authority, organizational and tenant boundaries, data movement, source access, credentials, and connectivity.
03
Operations and evidence
Define monitoring, audit evidence, retention, support, change control, recovery, rollback, and incident responsibilities.
04
Key custody
For Enterprise, record who holds the encryption keys and how they are rotated and recovered.

Bring your deployment constraints into the architecture conversation.

The systems, network boundaries, identity model, operating responsibilities, key custody, and recovery requirements all shape which edition fits.