Deployment
How it lands in your cloud A cloud project, a deploy-time key, and the key comes back to you.
What you open
A cloud project in your name, your billing, a European region. That is all that's asked of you up front.
What we stamp
The stack is stamped into your project, pinned to a signed version. An update is a new version you approve — not a hand that stays inside.
What is handed back
The deploy key comes back. The project, the data and the record are yours — they never left.
What happens when you stop
You revoke the access yourselves. What was built in your project stays there, the full log included.
The three clocks.Including the one we don't hold.
The stamp itself — minutes of machine work.
A client-ready system — working days: conversion, calibration, and acceptance runs on your documents.
And what actually sets the date: the model quota your cloud provider grants your project. That one isn't in our hands — and we say so up front.