Frequently Asked Questions

Dibbla is a platform for deploying, sharing and managing applications built with code assistants.

Dibbla 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 your application with the code assistant you prefer and then ask the assistant to deploy it to Dibbla. A few minutes later, the application is available online and ready to share with customers, colleagues or friends.

You do not need to know how to program or manage IT operations yourself. You deploy and manage the application by chatting with your code assistant. Dibbla takes care of everything around it: code review, user documentation, hosting, databases, security and who is allowed to use the application.

We are a group of developers, management consultants and AI specialists who saw the potential of code assistants and other AI assistants early on.

We have many years of experience working with both large and small companies. 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 and reliably.

We saw platforms such as Lovable, Replit and Microsoft Power Apps begin to solve parts of this problem. But they also require you to build and work in their way. We wanted to create a platform where you can use Claude, Codex, Gemini, OpenCode or any other code assistant together with the language models and technologies you prefer.

We are passionate about giving individuals more freedom with their AI assistants while giving companies a safe and simple way to make what they build available to customers, colleagues and suppliers.

Programming has become dramatically easier with coding agents, code assistants and agentic coding. But we have also seen how difficult it is to put everything around the application in place. A code assistant such as Claude Code, Codex or Gemini can build an application, 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 designed to create applications quickly and easily, but they are also quite prescriptive. They lock you into their own code assistant, their technology choices and their way of hosting and managing applications. You should not have to use Lovable simply because you enjoy building with AI.

Dibbla enables individuals and companies to build applications, AI agents and workflows with the code assistants they prefer, then deploy and manage everything in one place. You get the speed of working with code assistants without giving up control over how and where your applications run.

Dibbla is for both the person building an application and the person responsible for the company's IT. They are often two different people with different needs.

The builder wants to work in Claude Cowork, Claude Code, Codex or another code assistant and then make what they have built available to customers, colleagues or friends with as little friction as possible. This might be an individual sharing something built at home or an employee who has created a new tool for their work.

The other person is often a CIO, Head of IT or CTO who wants visibility and control over all the applications being created across the company. What applications do we have? Who can use them? How many resources do they consume? How is AI being used and what does it cost? Dibbla brings these answers together without dictating which code assistant employees must use.

Dibbla also gives builders guardrails that reduce the risk of mistakes in security-sensitive IT environments. Examples include code review before deployment, user documentation, control over resource usage and access control—who is allowed to use the application. A company can also choose to route an application's AI usage through Dibbla to monitor usage and control costs. This is optional.

You may already use an AI assistant in your daily work and ask it to build applications for you, but not know how to make them available to customers, suppliers, colleagues or friends in a simple and secure way. That is where Dibbla comes in.

Deploying and managing one application is not a major problem. Neither are a handful. But once the use of AI takes off, we do not believe a company will have only one or two applications. It will have hundreds of applications, databases, AI agents, workflows, MCP servers and user interfaces. Managing all of them will require considerably more work than building them.

That is where Dibbla comes in: as the home for everything you build with code assistants.

You build the application with whichever code assistant you prefer. When you are happy with it, you ask the code assistant to deploy it through Dibbla.

The code assistant prepares the application, reviews the code, writes a handbook for its users and handles the deployment. When everything is ready, the application receives a link that you can share with customers, colleagues or friends.

When you later want to fix a bug, add a feature or change how the application works, you simply continue chatting with your code assistant. The assistant makes the change and updates the application through Dibbla.

Yes, but the GitHub integration is optional. Every application gets a repository on Dibbla's own Git server, so it is version-controlled even if it is not hosted on GitHub or another external Git service. An important principle for Dibbla is that the platform should be able to operate independently of external services.

Every deployment is saved as a separate commit. This gives you a complete version history of the application: you can see what changed in a particular deployment and roll back to an earlier version if something goes wrong.

If you use GitHub, the application can also be synchronized there. You can continue using GitHub as usual, while Dibbla ensures that there is always a version history of the application that was actually deployed.

No. You should be able to build, deploy and manage an application by chatting with your code assistant.

You describe what you want to build or change. The code assistant takes care of the code and the technical instructions. Dibbla takes care of hosting, databases, security and everything needed to make the application available to others.

Lovable and Replit have their own AI assistants that build applications for you. Dibbla does not have its own agent for building apps. Instead, you build with the code assistant you prefer, such as Claude, Codex, Gemini or OpenCode, and then deploy the application through Dibbla.

As with Lovable, you receive a link that you can share with others. The difference is that you are not locked into a particular code assistant or the technologies chosen by a particular platform. Dibbla can also be installed in a company's own IT environment, while Lovable and Replit are services that run in their respective providers' environments.

Dibbla also reviews the application before deployment and ensures that documentation is available for the people who will use it.

You can think of Dibbla as a combination of an app store and a control and security center for all the applications, AI agents, workflows, MCP servers, user interfaces and databases that a company's employees have created with code assistants.

No. Dibbla does not build its own language models or require you to use a particular provider. You choose which language models and code assistants you want to work with.

Dibbla provides a shared gateway to models from different providers. Keys, usage and rules can be managed in one place instead of each application having to solve this separately. It also makes it easier to switch or combine model providers without rebuilding everything around them.

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.

Yes. An application can be open to everyone or require users to sign in. You can decide whether everyone in the company or only selected users should be allowed to use it.

This means that Dibbla can be used for public services, applications shared with customers and suppliers, and internal tools that only certain employees should be able to access.

Yes. Dibbla can set up the database the application needs. The code assistant can then connect the application to the database and handle the technical configuration for you.

The database can also be made available to other tools if, for example, you need to use it from your own computer or from a service running elsewhere on the internet.

An important principle in Dibbla is that everything belonging to an application should be able to live in one place: its code, database and the other services it needs. This means you do not have to keep the application with one provider and its database with another. It makes it easier to operate, scale and manage many applications consistently.

Before an application is deployed through Dibbla, its code is reviewed and documentation is created for the people who will use it. Dibbla can also require users to sign in and control who is allowed to use the application.

Traceability does not have to mean logging everything. You decide whether Dibbla should collect the application's logs and what information they should contain. An application that handles personal data or other sensitive information may need to limit logging to comply with GDPR or other legal requirements. In other applications, more detailed logging can make it easier to understand errors and investigate what happened.

If you choose to route the application's AI usage through Dibbla, you can also track which application is using AI, which models it calls, how much it uses and what it costs. You can set budgets and other rules for this usage as well. This gives you traceability and cost control without every application having its own keys and its own separate setup that nobody has visibility into. Using this part of Dibbla is optional.

Companies that want full control can run all of Dibbla in their own IT environment. The applications, databases, logs and AI settings then remain wherever the company has chosen to keep them.

Yes. Dibbla Workflows is a tool for building, running and monitoring agentic workflows.

As in n8n, you assemble the steps of a workflow in a visual editor. The difference is that the steps do not have to be limited to a set of prebuilt connectors. You can ask an AI assistant such as Claude or Codex to build each step around what you actually need to do.

For example, a step could retrieve a case from an internal system, look up information in another system or write a result back. If no ready-made connector exists, the AI assistant can build the step directly against the system's API. The step can also be limited to the specific information and actions required by that workflow, rather than receiving broader access than necessary. This allows security to be tailored to what the workflow actually needs to do.

You can work in the visual editor, but you can also ask your AI assistant to create or modify the entire workflow for you. Dibbla Workflows gives you both a visual overview of the process and traceability when it runs.

Yes. Dibbla has a consulting business made up of specialists known as Forward Deployed Engineers. They specialize in building agentic applications, but also in understanding the value that needs to be created, how the business operates and which ways of working need to change.

Our consultants help companies get started by building their first agentic applications with Dibbla. Together with the customer, they also establish the ways of working and teams needed to realize the potential of an AI-centric approach.

We work across several industries, including gaming, wholesale and highly regulated businesses.

Visit community.dibbla.com. You can ask questions about the platform, report bugs and submit improvement ideas or other feedback. You can also chat with the Dibbla team and other users, share experiences and see how others use the platform.

Guides and documentation on using Dibbla are available at docs.dibbla.com.

If you would rather contact us directly, email [email protected].