# Build with Claude. Deploy with Dibbla. _Stay in control._ Dibbla runs the apps and agents you build with Claude and several other code assistants, with the access control, audit logging and cost tracking your organization requires. Enterprise runs entirely in your own cloud or on‑premises. [Start free](https://console.dibbla.com) Deploy your first app in minutes. ## Pricing ### Free trial €0 / $0 30 days free - 3 apps, 2 databases - Every deploy gets a code review - Ready-made templates [Start free](https://console.dibbla.com) Most popular ### Business €100 / $100 per month - 15 apps, 10 databases - SSO via Google or Microsoft Entra - Roles: owner, admin, developer, viewer - AI Usage cost tracking - Built-in support tickets [Start now](https://console.dibbla.com) ### Enterprise Custom for regulated and large organizations - Self-hosted: your cloud or on-prem - EU data residency guarantees - Security review support - Dedicated onboarding [Talk to sales](/enterprise) ![Developer building an app with an AI coding agent, deployed and governed in the Dibbla console](/images/dibbla-hero-foto-21x7-1280.jpg) ![](/brand/dibbla-logo-green.svg) ConsolePowered by Dibbla AppsAI UsageWorkflows ### Apps Deploy **14 apps running** in your organization compliance-testsOpen ↗ Legal & Compliance Running insight-assistantOpen ↗ Insights & Analytics Running product-enrichmentOpen ↗ Operations Running invoice-triageOpen ↗ Finance Deploying AI Usage · August €11,200across 14 apps Every AI call logged — per app, department and model. Trusted by teams at ![FDJ United](/brand/customers/fdj-united.png) ![Fatshark](/brand/customers/fatshark.png) ![Ungdomsbarometern](/brand/customers/ungdomsbarometern.png) ![Pacing](/brand/customers/pacing.svg) ![Paxport](/brand/customers/paxport.png) ![](/brand/customers/fdj-united.png) ![](/brand/customers/fatshark.png) ![](/brand/customers/ungdomsbarometern.png) ![](/brand/customers/pacing.svg) ![](/brand/customers/paxport.png) ![](/brand/customers/fdj-united.png) ![](/brand/customers/fatshark.png) ![](/brand/customers/ungdomsbarometern.png) ![](/brand/customers/pacing.svg) ![](/brand/customers/paxport.png) ![](/brand/customers/fdj-united.png) ![](/brand/customers/fatshark.png) ![](/brand/customers/ungdomsbarometern.png) ![](/brand/customers/pacing.svg) ![](/brand/customers/paxport.png) How it works ## From Claude prototype to governed production in three steps. 1 ### Build with Claude Your teams build apps and agents with Claude — or any model. Start from ready-made templates for common business cases. 2 ### Deploy in one step One command or one click. Every deploy gets a code review before it ships, and runs with access control, logging and monitoring included. 3 ### Govern everything Every app, user and AI call visible in one console. Audit logs, cost tracking and guardrails from day one. In production today ## Real deliveries, not demos. Compliance at scale ### Every regulatory requirement, tied to a test that proves it In a transaction-intensive business under heavy regulation, agents read the requirements, work out which test cases each one demands, generate the test code and link it back to the clause it satisfies. The evidence an audit needs is produced by the pipeline instead of assembled after the fact. Product data ### A catalogue enriched on its way into a new PIM A product database had to arrive in a new PIM carrying attributes the old system never held. Agents read supplier documentation, fill the gaps against the target schema and flag what a human has to decide, so the migration stops waiting on manual data entry. Small team, full stack ### One builder, the whole delivery chain A small company builds with the code assistant it prefers and ships through Dibbla. Git, database, deployment, access control and AI cost tracking sit in one place, with no separate toolchain to keep running. Governance is a property of the platform rather than a project someone has to staff. Forward Deployed Engineers ## You don't have to build alone. Dibbla's consulting team of Forward Deployed Engineers builds your first agentic applications with you, on the platform, in your environment. They specialize in agentic development, and in understanding where the value is and which ways of working need to change. [Talk to us about a first project](#intro) ### Start with a real use case A first application in production, not a slide deck. The use cases above were built this way. ### Learn by building together Your team works alongside our engineers and owns the application from day one. ### Industry experience Gaming, wholesale and highly regulated businesses, from iGaming compliance to product data at scale. Built for scrutiny ## When someone asks "who did what, and what did it cost" — you have the answer. Audit log Recent changes recorded in the audit log Event Subject When app deployed compliance-tests · v14 Today 09:12 access granted Finance · 3 users Today 08:47 model changed insight-assistant Yesterday secret rotated product-enrichment Yesterday Every change logged with who, what and when. AI Usage by department AI spend per department this month Department Spend Share Operations €5,400 ▮▮▮▮▮ Legal & Compliance €2,700 ▮▮▮ Insights €2,000 ▮▮ Finance €1,100 ▮ Costs attributed per app, department and model. No more surprise invoices. Why leadership chooses Dibbla ## AI adoption stalls on uncertainty. Remove it. Your teams are already building with AI. The question is whether it happens in one governed place — or in a hundred ungoverned ones. ### See everything Every AI app in your organization in one register, with an owner and a status. ### Control access SSO and role-based access. The right people reach the right apps and data, nothing more. ### Prove compliance Audit-grade logging and EU data residency, ready for GDPR reviews and security questionnaires. ### Control costs AI spend attributed per app and department. Budget with real numbers, not estimates. Claude-first. Works with every major model provider. ClaudeOpenAIAzure OpenAISelf-hosted models FAQ ## The things people ask us first. What Dibbla is What is Dibbla? Dibbla is a platform for deploying, sharing and managing applications built with code assistants. It is the home for all the applications, AI agents, workflows, MCP servers, user interfaces, databases and other services that you or your colleagues create with code assistants. Dibbla is not a competitor to code assistants such as Claude Code, Claude Cowork, Codex, Gemini CLI and OpenCode. It complements them: you build with the assistant you prefer and ask it to deploy to Dibbla. A few minutes later the application is online and ready to share. Dibbla takes care of everything around it: code review, user documentation, hosting, databases, security and who is allowed to use the application. Who is behind Dibbla? We are a group of developers, management consultants and AI specialists who saw the potential of code assistants early on. We have seen that building the application itself is often the easy part; the hard part is deploying it, making it available to others and managing it safely. We saw platforms such as Lovable, Replit and Microsoft Power Apps begin to solve parts of this problem, but they require you to work their way. We wanted a platform where you can use Claude, Codex, Gemini, OpenCode or any other assistant together with the models and technologies you prefer. Why did we build Dibbla? Programming has become dramatically easier with coding agents, but the application still needs somewhere to run, a way to reach its users and a way to be managed over time. Alternatives such as Lovable and Replit are quick, but prescriptive: they lock you into their own assistant, technology choices and hosting. Dibbla lets individuals and companies build with the code assistants they prefer, then deploy and manage everything in one place, keeping control over how and where applications run. Who is Dibbla for? Both the person building an application and the person responsible for the company's IT. The builder wants to make what they have built available with as little friction as possible. The CIO, Head of IT or CTO wants visibility and control: what applications do we have, who can use them, what resources do they consume, how is AI used and what does it cost? Dibbla brings these answers together without dictating which code assistant employees must use, and gives builders guardrails such as code review before deployment, user documentation, resource control and access control. A company can also route AI usage through Dibbla to monitor and control costs; this is optional. Why should I start using Dibbla? You may already ask an AI assistant to build applications, but not know how to make them available to customers, suppliers or colleagues in a simple, secure way. Deploying one application is not a major problem. But once AI use takes off, a company will not have one or two applications: it will have hundreds of apps, databases, AI agents, workflows and interfaces. Managing them will require considerably more work than building them. That is where Dibbla comes in: the home for everything you build with code assistants. Working with Dibbla How does Dibbla work with my code assistant? You build the application with whichever code assistant you prefer. When you are happy, you ask the assistant to deploy it through Dibbla. The assistant prepares the application, reviews the code, writes a handbook for its users and handles the deployment. The application receives a link you can share. When you later want to fix a bug or add a feature, you simply continue chatting with your assistant. Does Dibbla integrate with GitHub? Yes, but it is optional. Every application gets a repository on Dibbla's own Git server, so it is version-controlled even without an external Git service; every deployment is saved as a separate commit, and you can roll back if something goes wrong. If you use GitHub, the application can also be synchronized there. Do I need to know how to program or manage IT operations? No. You describe what you want to build or change; the code assistant takes care of the code, and Dibbla takes care of hosting, databases, security and everything needed to make the application available to others. How is Dibbla different from Lovable or Replit? Lovable and Replit have their own AI assistants that build applications for you. Dibbla does not have its own agent for building apps: you build with the assistant you prefer and deploy through Dibbla. You are not locked into a particular assistant or technology stack, and Dibbla can be installed in a company's own IT environment, while Lovable and Replit run in their providers' environments. Dibbla also reviews the application before deployment and ensures documentation exists. Think of it as a combination of an app store and a control and security center for everything a company's employees create with code assistants. Platform & capabilities Does Dibbla have its own language models? No. Dibbla does not build its own models or require a particular provider. You choose which models and assistants to work with. Dibbla provides a shared gateway to models from different providers: keys, usage and rules are managed in one place, which also makes it easier to switch or combine providers without rebuilding everything around them. Where do the applications run? Can Dibbla run in our own environment? Applications can run in Dibbla's environment or in a company's own IT environment; you choose where the applications and their data reside. Companies with strict security requirements can install Dibbla in their own environment and follow their own rules and technical standards. The applications, databases and other services then remain in an environment controlled by the company. Can I control who is allowed to use an application? Yes. An application can be open to everyone or require sign-in, and you decide whether everyone in the company or only selected users can use it. Dibbla works for public services, applications shared with customers and suppliers, and internal tools. I need a database for my application. Can Dibbla help? Yes. Dibbla sets up the database, and the code assistant connects the application and handles the configuration. The database can also be made available to other tools. Everything belonging to an application lives in one place: its code, database and services, which makes it easier to operate, scale and manage many applications consistently. I am looking for a visual, agentic workflow editor like n8n. Does Dibbla offer one? Yes. Dibbla Workflows is a tool for building, running and monitoring agentic workflows. As in n8n you assemble the steps visually, but steps are not limited to prebuilt connectors: an AI assistant can build each step around what you actually need, directly against a system's API if no connector exists, and limited to the specific information and actions the workflow requires. You get both a visual overview and traceability when it runs. Security & control I care about security and traceability, both within the application and in how AI is used. How does Dibbla help? Before an application is deployed, its code is reviewed and documentation is created. Dibbla can require sign-in and control who may use the application. Traceability does not have to mean logging everything: you decide whether Dibbla collects the application's logs and what they contain, which matters for GDPR and other requirements. If you route AI usage through Dibbla you can track which application uses AI, which models, how much and at what cost, and set budgets and rules. Companies that want full control can run all of Dibbla in their own IT environment. Company & support I have heard that Dibbla also has a consulting business. Is that true? Yes. Dibbla has a consulting business made up of specialists known as Forward Deployed Engineers. They specialize in building agentic applications, and in understanding the value to be created and which ways of working need to change. Our consultants help companies get started by building their first agentic applications with Dibbla. We work across several industries, including gaming, wholesale and highly regulated businesses. I have a question, found a bug or want to learn more. Where should I go? Visit community.dibbla.com to ask questions, report bugs and share feedback with the Dibbla team and other users. Guides and documentation are available at docs.dibbla.com. You can also email us directly. The full FAQ is also served as machine-readable Markdown for AI assistants at [dibbla.com/faq](/faq). ## See your organization's AI in one place. [Book a demo](#intro) ## See how Dibbla fits your landscape and AI roadmap. 30 minutes to map your current setup and where Dibbla would plug in. Leave your details — we'll reach out within one business day. Name Work email Talk to Dibbla We only use your details to reach back out. No spam, no lists. Something went wrong. Please try again, or email us directly at contact@dibbla.com. Thanks. We'll be in touch within one business day to book your intro.