Enterprise

# The self-hosted platform for AI-built apps. _Nothing leaves your network._

Your teams build with Claude and the code assistants they prefer. Dibbla runs what they build inside your own cloud or datacenter, with the access control, audit logging and cost attribution your security and compliance functions expect.

[Talk to sales](/#intro)[Get the security overview](#documents)

Deployment

## Two ways to run it. Both inside your perimeter.

### Your VPC

Dibbla is installed into your own cloud account — AWS, Azure or GCP — as a Kubernetes workload deployed with Helm. You keep the network boundary, the encryption keys and the cloud bill.

-   Deployed with Helm into your cluster
-   Your VPC, your subnets, your egress rules
-   Databases provisioned in your account
-   Upgrades on your schedule

### On-premises

For organizations whose data cannot touch a public cloud at all. The same platform, installed in your own datacenter, with no outbound dependency required to keep applications running.

-   Runs on your own Kubernetes
-   Air-gap friendly: no call-home to operate
-   Self-hosted models supported alongside hosted providers
-   Your operations team owns the runtime

Security

## The controls a security review actually asks about.

### Runs in your network

Kubernetes + Helm inside your own VPC or datacenter. Apps, databases and services never leave the perimeter you already defend.

### SSO via Google & Microsoft Entra

Your existing identity provider decides who gets in. Roles map to owner, admin, developer and viewer.

### Role-based access control

Per-app and per-database permissions. The right people reach the right apps and data, nothing more.

### Audit-grade logging

Every deploy, access change, model change and secret rotation recorded with who, what and when.

### Secrets and key management

Encrypted at rest, injected at runtime, rotated without redeploying the application.

### EU data residency

For the managed service, data stays in the EU. Self-hosted, it stays wherever you put it.

Governance

## Guardrails that hold without slowing anyone down.

### Code review on every deploy

No application reaches production without its code being reviewed and its user documentation generated. This is on by default and cannot be switched off per deploy.

### AI usage attribution

Every AI call logged per app, department and model, with budgets and rules you set centrally.

### Policy guardrails per environment

Which models an app may call, which egress it may make, which data it may reach.

### Application register with owners

Every app in the organization with a named owner, a status and a review date.

### Data retention controls

You decide whether Dibbla collects an application's logs and what they contain — which matters for GDPR and for what you can promise your own auditors.

Procurement

## The paperwork, ready before you ask.

[

### Security overview

Architecture, threat model and controls, written for a security review.

Request →](#)[

### Data processing agreement

Standard DPA with sub-processor list and EU transfer terms.

Request →](#)[

### Architecture diagram

Reference deployment for VPC and on-premises installs.

Request →](#)[

### Standard questionnaire answers

Pre-filled responses to the questions procurement always asks.

Request →](#)

Onboarding

## From first conversation to first application in production.

1

### Scoping and security review

We walk your security team through the architecture and answer the questionnaire before anything is installed.

2

### Install in your environment

Helm chart into your cluster, identity wired to your Entra or Google tenant, first environment up.

3

### First applications in production

Our Forward Deployed Engineers build the first real use case with your team, on your platform.

4

### Handover and scale-out

Your team runs it. We stay available for the next wave of applications.

In production today across

Gaming & iGamingWholesale & distributionRegulated industriesPublic sectorHealthcare & life science

## Bring your security team to the first meeting.

We would rather answer the hard questions early than discover them in procurement.

[Talk to sales](/#intro)