The code is 100% yours
No license fee on the software we build, no vendor lock-in. Ownership passes to you milestone after milestone, as each milestone is paid. Unless agreed otherwise, we retain the moral rights of authorship over the software.
Trust Center the answers before the questions
Who owns the code, where the data sits, who touches it and what happens if one day you change supplier. Written down here, not asked for in a call.
The same questions come up in every serious evaluation of a software supplier, and they nearly always arrive late, halfway through a technical call.
By then a proposal is already on the table, and the person who has to sign off was often not in the earlier meetings. They are fair questions and the answers do not change depending on who is asking, so they may as well be written down. Here is how we treat code, data, artificial intelligence on the processes that matter, and the way out of a supplier relationship.
The fixed points
Commitments that hold, not concessions negotiated at random
Your data does not train models
We select enterprise cloud services that exclude it contractually, in line with GDPR and with SOC 2 attestations. Where more is needed, a private AI infrastructure or Zero Data Retention services are considered.
AI does not decide on its own
An LLM is never wired straight to a database. Guardrails, strict schema validation and human approval (human-in-the-loop, HITL) on write operations and on high-risk ones.
Every decision can leave a trace
We always recommend AI observability tools, switched on at your decision: for every agent operation you keep the context read, the data extracted, the steps followed and the token cost. Reconstructing an error becomes a query, not an investigation.
Standard technologies, never proprietary
No in-house frameworks with closed licenses and future costs, that only we know how to maintain. Documented, widely used stacks, because another team has to be able to take over without rewriting.
WCAG 2.2 AA accessibility
Contrast, keyboard navigation, roles and states exposed to assistive technologies. Not a badge at the end of a project: a design and engineering constraint from the start. Where needed it goes up to level AAA.
What we hand over, and what happens if we leave
Code ownership counts for little if you cannot use it. That is why handover includes the repository with its full history, the API documentation in Swagger/OAS format, access to the services and the handoff to your team or to whoever takes over from it.
The uncomfortable question is the next one: what happens if Volcanic Minds is no longer around tomorrow, or if you decide to change supplier. The answer cannot be reassurance, it has to be a consequence of the architecture. The code becomes yours milestone after milestone; it runs on technologies any competent team knows; the data sits in standard databases you can export without our permission; and the business logic is not tied to a single AI model vendor, so that part stays replaceable too.
This is possible because we feel every project as our own, and we will do the impossible to build you a tangible competitive advantage.
A project done well is a project you can walk away from. If leaving us required a rewrite, the fault would be ours.
The evaluation questions: the short answer here, the full one in the frequently asked questions
Contract and continuity
What we do not claim
A Trust Center is worth little if it only lists what goes well. Volcanic Minds is a company founded in September 2022: we are not yet ISO 9001 and 27001 certified, and we do not claim certifications we do not hold.
We design following recognized practices and well-built standards, and we rely on cloud providers that do hold those certifications, but that is a different thing and it should be said. We are willing to start certification programs for projects and clients that genuinely need them.
If your procurement process requires a formal certification, it is better to know at the first call than at due diligence. If instead it requires understanding how we actually work, this page is the starting point and specific questions are welcome.
Ask the question that is missing.
Questions are the best way to get to know us: your project becomes our objective, and to hit it we have to be aligned from the starting line.
- You won't talk to a salesperson
- NDA before we get into the details
- The code stays yours