Drydock · Korifi on Kubernetes

cf push your way
to production.

Managed Cloud Foundry on Kubernetes. Push source code, get a routed and TLS-secured app. Buildpacks handle the rest. Built on Korifi (CNCF), operated by Orion.

Request a free POC See how it works ↓

// What it is

The Cloud Foundry developer experience,
without the PCF tax.

Cloud Foundry's cf push workflow is the closest thing we have to a universal "deploy a web app" verb. Push source code, get a running, routed, TLS-secured app. Buildpacks detect the language, compile, and launch — no Dockerfiles, no YAML.

Drydock runs that workflow on Kubernetes using Korifi, the CNCF project that implements Cloud Foundry semantics on top of K8s. You get cf push, cf logs, org/space RBAC, service binding via VCAP_SERVICES — all the things teams using PCF already know — backed by real Kubernetes primitives we operate for you.

Start with a free lightweight tier for POC and dev work. Graduate to a production tier when the workload is ready. No PCF license, no Broadcom tax, no vendor lock-in — Korifi is Apache 2.0 and you can self-host the day you want to.

// How it compares

Three ways to run
Cloud Foundry semantics today.

Capability

Drydock

PCF / Tanzu

Self-managed Korifi

cf push workflow

✓ Yes

Runs on Kubernetes

✓ Yes

Different model (Diego)

✓ Yes

Open-source foundation (CNCF)

✓ Yes

✗ No

✓ Yes

Operator-on-call included

✓ Yes

✗ No

Free POC tier

✓ Yes

✗ No

You run it

License fee

None

Per-app + per-environment

None

Time to first deploy

Minutes

Weeks

Days to set up

// How it works

From zero to `cf push`
in three steps and one conversation.

The POC starts free. Provisioning the environment is on us. Your team owns the apps you push to it.

Scope

A 30-minute call to understand the workload — language, runtime needs, data services. We tell you whether Drydock fits.

Provision

We spin up a dedicated Drydock environment with Korifi pre-installed, configured, and TLS-secured. Your CF CLI gets credentials.

Push

cf push your app. Buildpacks detect, compile, deploy. Service bindings injected automatically. Free for POC and dev.

Graduate

When the workload is production-bound, we move it to a managed production tier: multi-AZ, managed data services, WAF, monitoring, SLA.

// Questions worth asking

Honest answers,
before the contract.

What does Drydock cost?

Lightweight tier is free for POC, prototyping, and dev/test — always. Production tier is custom-priced against your workload, team size, and SLA. We will put numbers in writing on the first call.

Is there vendor lock-in?

No. Drydock runs Korifi (CNCF), which is Apache 2.0. You can self-host the same stack on any Kubernetes cluster. We are the operations layer, not the runtime — take it over whenever you want.

Do I need Kubernetes knowledge?

No. The whole point of cf push is to abstract that. You can develop and deploy without knowing what a pod or a deployment is. We handle the K8s side.

Which buildpacks?

Paketo buildpacks by default — Java, Node.js, Go, Python, .NET, Ruby, PHP, static sites. We can wire custom buildpacks for the production tier if your stack needs it.

How is data handled?

Production tier includes managed databases (RDS, ElastiCache, etc.) and managed object storage. Credentials inject automatically via VCAP_SERVICES. Encrypted at rest and in transit. Backup and DR included.

Government use cases?

Yes. Orion is WOSB-certified and AWS Select Partner, eligible for federal set-aside contracts and government procurement. Drydock can be deployed into GovCloud environments on request.

// Dive deeper