Enterprise
The same platform, on infrastructure that fits your rules. Larger teams and regulated businesses get a cluster of their own, Basable in their own data centre, and ISO 27001 certification where procurement requires it. Tell us what you need at enterprise@basable.com.
Dedicated cluster
On the standard platform each environment runs in a virtual cluster of its own on servers Basable shares between customers, sandboxed at the kernel level. A dedicated cluster puts your organisation's environments on hardware that is yours alone: dedicated servers in a European data centre, running nobody else's workloads.
- Your own Kubernetes cluster, sized for your workloads, with capacity reserved for you.
- A region of your choice: Germany, Finland, France or the United Kingdom.
- No shared hardware and no neighbours, for the audits that ask about it.
- Everything else as on the standard platform: preview and live environments, your
own domains, a kubeconfig and
kubectl.
Bring your own cluster
When the code and the data may not leave your perimeter, Basable deploys into a Kubernetes cluster you run: in your own data centre, or in your own cloud account. The AI still writes the code into your repository and your CI still builds it. What changes is where it runs.
- Your cluster, your network, your storage and your backups.
- Access your security team agrees to: a scoped credential for deploying, which you can inspect and revoke.
- Your existing controls stay in force: network policies, admission policies, logging and monitoring.
ISO 27001 certification
If your procurement requires an ISO 27001 certified supplier, or your own certification scope must cover where your applications run, this is an enterprise option. The scope is written around your setup. Tell us what your auditors need when you write.
- A certification scope written around your setup: a dedicated cluster or your own cluster, and the processes that run it.
- Your security questionnaire answered by the engineers who built the platform, with a call to go through it.
- The data flows written down: where the code, the application data, the backups and the logs live, and who can reach them.
What stays the same
An enterprise setup changes where your projects run, not how they are built. The AI
writes ordinary code into a git repository you own, on your own git host, and your own
CI builds it. There is no proprietary format and no export step. Every project gets a
preview and a live environment, your own domains with certificates handled for you, and
admin access to each environment with kubectl. Your team works in the same
editor, or with its own AI agent over MCP.
How an enterprise agreement works
-
Write to us
One mail to enterprise@basable.com: what you are building, how many people will work on it, where it must run and what your auditors need.
-
We scope it together
A call with the engineers, not a sales deck: sizing, region, the access model and the controls you need. You hear what works today and what we would build for you.
-
One agreement
A written agreement for the setup, the processing of your data and the price, invoiced monthly. The Terms of Service already carry the processor terms the GDPR requires; the agreement adds what your organisation needs.
-
Build as everyone does
Same editor, same MCP, same repositories. The enterprise setup is where it runs, and you have a direct line to the people who run it.
Frequently asked questions
Is there a minimum size or term?
An enterprise setup is agreed per organisation, so this page names no minimum. A dedicated cluster reserves whole servers, which costs more than the standard platform's per-second billing does for a small team. Tell us your size and we quote it.
Can we start on the standard platform and move later?
Yes. A project is a repository with its Kubernetes manifests in it, so it moves to a dedicated cluster or your own cluster by deploying there. The repository does not change, and neither does the way your team works.
Where are the servers?
Basable's own infrastructure is in Europe: Germany and Finland on Hetzner, France and the United Kingdom on OVHcloud. A dedicated cluster is in the region you choose. Your own cluster is wherever you run it.
Who can see our code and our data?
Your code lives in your repository on your git host. Basable reaches it through the git connection you grant, which you can revoke from your git provider at any time. Your application's data lives in its environment's cluster and storage; in your own cluster, it never leaves your network.
Do you sign a data processing agreement?
Our Terms of Service include the processor terms Article 28 of the GDPR requires, and the Privacy Policy lists our sub-processors. An enterprise agreement can add to them.
Talk to us
Describe what you need and where it must run. You get an answer from an engineer.