01What happens if a key person is unavailable?
The project does not rely on word of mouth: versioned code, infrastructure described as code, documented decisions, standard Google Cloud services. Another engineer can take over from the repository.
02Who owns what is built?
You do. The code is delivered in your repository and the system runs in your cloud project, under your accounts. Your teams or another provider can take it over.
03Where is our data, and who can access it?
In your own cloud account, in the region you choose: Switzerland or the European Union. Access is named and limited to what is needed.
04How do you get through our security review?
We are used to the security and architecture reviews of large groups: architecture file, data flow analysis, least-privilege access, logging. We prepare the file and defend it with you.
05What if the AI gets it wrong?
It proposes, it does not decide. Anything that writes, sends or pays goes through an approval or a rule written without AI. Every answer cites its source, and every call is logged.
06What does it cost to run?
Each agent has a capped budget and its consumption is tracked. You see the cost per use, and an overrun triggers an alert, then a shutdown.
07Are you tied to one vendor?
For infrastructure, by choice: we are Google Cloud specialists, certified, with a region in Zurich. For AI models, no: Anthropic, OpenAI, Google or Mistral, or open-source models you host yourself. And our connectors use MCP, an open standard: they reach your systems wherever they run, including on AWS or Azure.