Your software
behind the customer firewall

Q: "Is this the same as BYOC / On-Premises on the platform page?"

"No. [BYOC / On-Premises](/platform/) means you provide infrastructure and **ayedo operates** the Software Delivery Platform. Enablement here means **you** (or your buyer) operate the package we built. Managed on this page is operations of *your* application on the buyer’s Kubernetes.\n"

Q: "Why discuss enablement and managed together?"

"With few deployments and no Kubernetes operations team, managed is often the faster path to first production. A productised package pays off when you will run many buyer sites yourself. The two can be sequenced.\n"

Q: "Do you build the buyer’s Kubernetes cluster?"

"Not by default. The buyer provides the API. We check the cluster contract and can add primitive blocks. Building the control plane is an optional extension.\n"

Q: "Where is the technical how-to?"

"In the docs, without product marketing: [Software on a provided cluster](https://docs.ayedo.de/delivery/provided-cluster/) and [Air-gap delivery](https://docs.ayedo.de/delivery/air-gap/).\n"

Enterprise buyers provide Kubernetes – often air-gapped. We build the reusable delivery package (workspace, primitives, runbooks, update trains) or operate the instance for you. One dual runtime, two operating paths.

Book a conversation Learn more

ISO 27001 ISO 9001 GDPR compliant DORA Compliant

Two paths, one codebase

You build the product. We standardise how it lands in the ayedo Cloud , Dedicated, or the end customer’s data centre – including air-gap. That is the dual-runtime principle .

Enablement

You operate the package

✓ Versioned Polycrate workspace: core package plus a small site overlay
✓ Platform primitives (for example Cilium) planned in – even when the buyer provides Kubernetes
✓ Air-gap bundle, private registry, rollback via pinned tags
✓ Architecture, runbooks, three update trains: primitives, dependencies, your software
✓ Knowledge transfer to your engineering team – no ongoing operations by us

Request enablement

Managed

ayedo operates the instance

✓ The buyer provides Kubernetes; ayedo runs Day-2 for the app and agreed primitives
✓ The same building blocks as the Software Delivery Platform
✓ Fits few sites or teams without Kubernetes operations
✓ Public anchors: App Hosting from €599.95/month, SaaS Hosting BYOC custom
✓ Manage the first sites, enable later – easier than the reverse

Request managed

Workshop

Training only, not a package

✓ Platform Building stays consulting plus hands-on (typically 3–10 days)
✓ Not a substitute for a productised delivery kit
✓ Fits teams that will keep building the platform themselves

Workshops

What the package contains

Enablement delivers artefacts and processes. Technical depth lives in the docs .

Workspace template

One core, many sites. Site-specific remain kubeconfig, ingress, StorageClass, registry, and secrets.

Polycrate Overlay

Primitives

Cilium, ingress, cert-manager, policy baseline – ship them, install only if the cluster owner agrees.

Cilium Kyverno

Air-gap

Signed bundle, Harbor import, registry proxy. Install and rollback without internet.

Harbor Offline

Update trains

Version and roll back primitives, dependencies, and your software separately.

Day-2 Rollback

Free Consultation

Frequently asked questions

Is this the same as BYOC / On-Premises on the platform page?

No. BYOC / On-Premises means you provide infrastructure and ayedo operates the Software Delivery Platform. Enablement here means you (or your buyer) operate the package we built. Managed on this page is operations of your application on the buyer’s Kubernetes.

Why discuss enablement and managed together?

With few deployments and no Kubernetes operations team, managed is often the faster path to first production. A productised package pays off when you will run many buyer sites yourself. The two can be sequenced.

Do you build the buyer’s Kubernetes cluster?

Not by default. The buyer provides the API. We check the cluster contract and can add primitive blocks. Building the control plane is an optional extension.

Where is the technical how-to?

In the docs, without product marketing: Software on a provided cluster and Air-gap delivery .

Jetzt beraten lassen

Your software behind the customer firewall