> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cnap.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise

> Custom limits, dedicated support, and compliance for organizations with larger requirements

Enterprise is not a fixed plan — it is a custom arrangement for organizations that need more than Pro provides. There is no self-serve Enterprise tier in the dashboard.

<CardGroup cols={2}>
  <Card title="Schedule a call" icon="calendar" href="https://cal.com/marcus-klingler/cnap">
    Talk to us about your requirements, pricing, and migration plan
  </Card>

  <Card title="Enterprise overview" icon="building" href="https://cnap.tech/enterprise">
    See the full enterprise pitch with video walkthrough
  </Card>
</CardGroup>

## What Enterprise provides

### Custom resource limits

Pro has fixed limits (3 machines, 8 CPU, 16 GB). Enterprise workspaces get custom limits set per-workspace or per-user — 50 machines, 200 CPU cores, 1 TB memory, whatever the workload requires.

Technically, this works through **quota overrides** — the same quota system, but with a per-workspace override that takes precedence over the tier defaults:

```
Resolution chain: quota override → Pro tier default → Free tier default
```

Overrides are set by the CNAP team. They are not self-serve.

### Dedicated support

* Direct access to the engineering team
* Custom onboarding and migration assistance
* Priority issue resolution
* Architecture review for your deployment

### Compliance and security

Enterprise customers often require:

* **Data residency** — workloads stay in specific regions (EU, US, or custom)
* **ISO 27001** and **SOC 2** certification (planned)
* **GDPR** compliance documentation
* **Dedicated infrastructure** — isolated control planes, no shared resources
* **Security reviews** — we participate in your vendor assessment process

### Flexible billing

* Annual contracts with volume discounts
* Usage-based billing for compute (pay for what you use beyond included allocation)
* Consolidated invoicing across multiple workspaces
* Custom payment terms

## How Enterprise differs from Pro

|                    | Pro                      | Enterprise                       |
| ------------------ | ------------------------ | -------------------------------- |
| **Price**          | €20/month fixed          | Custom (annual contract)         |
| **Limits**         | 3 machines, 8 CPU, 16 GB | Custom per workspace             |
| **Instance types** | All provider types       | All + reserved capacity          |
| **Support**        | Standard                 | Dedicated engineering contact    |
| **Compliance**     | Shared infrastructure    | Dedicated option, certifications |
| **Billing**        | Monthly self-serve       | Annual, usage-based, invoiced    |
| **Onboarding**     | Self-serve docs          | Hands-on migration support       |

## How tier resolution works with Enterprise

Enterprise does not add a third tier to the code. Instead, it uses **quota overrides** on Pro workspaces:

1. Enterprise workspace is on the Pro Stripe subscription
2. CNAP team sets quota overrides (e.g., `compute/machines: 50`)
3. When the quota system checks limits, it finds the override first and uses it instead of the Pro default

This means:

* All Pro features work (no TTL, all instance types, auto-scaling)
* Limits are higher than Pro defaults
* The override is workspace-scoped (different enterprise workspaces can have different limits)
* The override survives plan changes — if the workspace downgrades and re-upgrades, the override persists

## Bring your own key + Enterprise

Most enterprise customers use BYOM (bring your own machine) with their own cloud accounts. This is the recommended path and the core of our enterprise pitch:

<Tip>
  **Zero infrastructure markup.** You bring your Hetzner (or any supported provider) account. You pay Hetzner at Hetzner's published prices. CNAP charges only for the management subscription — never a percentage on top of your infrastructure costs.
</Tip>

This combination provides:

* **No CNAP compute costs** — customer pays their provider directly at provider prices
* **No quota limits** — BYOM bypasses all machine quotas regardless of plan
* **Full provider choice** — any instance type, any region, any account
* **CNAP manages Kubernetes** — cluster lifecycle, auto-scaling, monitoring, suspend/resume
* **Enterprise support** — dedicated engineering contact for the management layer
* **Transparent costs** — your cloud bill is between you and your provider, visible in their console

This is the most cost-effective path for organizations with existing cloud accounts. You get enterprise Kubernetes management without paying a platform tax on compute.

## Getting started

Enterprise arrangements are handled directly. Contact us to discuss:

* Your workload requirements (machines, CPU, memory, regions)
* Compliance needs (certifications, data residency)
* Billing preferences (annual, usage-based, invoiced)
* Migration timeline (existing infrastructure to CNAP)

<Card title="Schedule a strategy call" icon="calendar" href="https://cal.com/marcus-klingler/cnap">
  30-minute call to discuss your requirements, pricing, and migration timeline
</Card>