DOCS
How it works, written down.
Twelve reference pages, for when you want the answer rather than the walkthrough. What the platform is and is not, what arrives with every system, where the data physically sits, what building costs, and which obligations stay with you. The tutorials teach; these pages tell you where the edges are.
WHAT ARE YOU TRYING TO BUILD?
Type what you are trying to do and we will point at the page that answers it — across the documentation, the tutorials and the twenty sector templates.
01 Platform basics
What the thing is, who the account belongs to, and what counts as one system.
What CodiVibes is and is not: a chat studio that writes real software for your business, hosted in Frankfurt, changed by describing the change rather than raising a ticket.
How a CodiVibes account works: email and password or Google, one owner per account, company details for invoicing, and where users of the system you build actually sign in.
What a system is on CodiVibes, what the four questions when you start one actually set, why the region cannot be changed later, and when to split work into a second system.
02 Building
How a description becomes software, what arrives with every system, and where the studio stops.
The five-step loop behind every build and every change on CodiVibes, what the studio asks back, and how to phrase a request so you get what you meant.
The nine things included in every system built on CodiVibes: database, web address, mobile screens, scheduled jobs, email, file storage, AI inside the system, live updates and EU hosting.
What CodiVibes cannot or will not build: mobile apps in the stores, messy migrations, design work, prohibited AI uses, and processes nobody in the company can describe.
03 Running it
Where the data physically sits, how to get a copy out, and the one piece of setup that is yours.
Where CodiVibes data is physically stored and processed: EU hosting in Frankfurt, encryption in transit, per-customer isolation, and the one processing step that may happen outside the EEA.
How backups work on CodiVibes, how to get an export of your own data, what pausing a plan does, and exactly what is kept after an account is closed.
How to put a CodiVibes system on your own domain, what has to happen at your registrar, and why sending email from your own domain is a second step.
04 Commercial & compliance
What it costs, what a supplier questionnaire will ask, and whose problem each AI Act duty is.
How CodiVibes credits work: the four plans, what a credit is consumed by, top-ups that do not expire, the free week, and what happens when the allowance runs out.
A quick-reference summary of CodiVibes security: hosting region, encryption, password storage, isolation, sub-processors, retention periods and breach notification.
How the EU AI Act applies to CodiVibes and to what you build with it: the current deadlines after the Digital Omnibus, the provider and deployer split, and what the platform gives you.
DOCS
If a figure here disagrees with the pricing, security or AI Act page, that page is right and this one needs fixing — those three are where the numbers actually live.
Looking for step-by-step instructions instead? The tutorials walk through the same ground in the order you will need it. Tutorials →