Your cloud. Your keys. Your data.
vermadev is the data platform for teams who cannot hand their records to someone else’s cloud. We install it in an account you own, on Amazon Web Services, Microsoft Azure, or Google Cloud. We operate it. You can take that access back.
Your records stay in your account
The platform runs in a cloud account that belongs to you. You choose Amazon Web Services, Microsoft Azure, or Google Cloud, and you choose the region. The records, the files, and the address your team opens all live there.
We do not keep a copy. We do not take custody of a deployment in your account, and we do not keep a backup of those records on our systems. What we hold for the contract is smaller: names, business contact details, how you sign in, billing status, and the messages you send us.
An environment we host so you can try the product is a different arrangement. It is not the deployment in your account, and we can close it.
Your account is the line
We sit outside the account. The only way in is access you granted, and you can remove it. Your records sit behind that line. Your team reaches the product through the front door. The records do not.
We sit outside the account. The only way in is access you granted, and you can remove it. Your records sit behind that line. Your team reaches the product through the front door. The records do not.
Your cloud account
Your account and your keys
A private network
Your records
The address your team uses
Access you can take back
You give us access so we can install the platform, update it, and keep it running. The terms call that an Operational Grant. It lives in your cloud account, under your control.
What we use it for
- Install vermadev in your account.
- Ship updates.
- Keep the platform running.
- Read the settings an update needs.
How wide it is
The grant is for operating vermadev. It is not a copy of your records, and it is not a second home for them. You decide that access in your own cloud account.
How you end it
Remove our access in your cloud account. There is no extra step inside the product. Once that access is gone, we cannot ship another update or operate the platform for you.
What keeps running
The platform that is already running stays up. Removing our access does not delete your records. You keep the account, and you keep what is in it.
One product, updated in order
Every customer gets the same vermadev. What differs is the account: which cloud, which region, which domain, which integrations. We do not keep a private copy of the product for one customer.
Built as one stack
The network, the database, the application, the address your team uses, and the certificates are created together in your account.
Updates wait their turn
A release is tested, then applied to each customer in order. A step that fails does not start the step that depends on it.
A failed update leaves the current version in place
If an update cannot finish safely, the version your team is already using stays.
One line of releases
There is one vermadev. The next release follows the last one we shipped to everyone.
You can see what we shipped
A review should be able to point at a release, not at a promise.
Each release has a name
Every update we put in your account is a specific version of vermadev. You can ask which version is running.
The history stays with the account
What was deployed is part of that account’s history and of our release history. Ask, and we will walk a reviewer through it.
Locked on the way in, held in your account
People reach vermadev over an encrypted connection.
Records and files are stored in your cloud account, under the protection of that account. The keys belong to the account you own.
The secrets the platform needs in order to run are created in your account and stay there.
The model meets the data where the data lives
You choose the model. The work is meant to happen with the deployment in your account, not by sending your records to us.
We do not use your records to train models for other customers.
People and agents in your account act under the permissions you set, and a reviewer can see what they did.
You choose the region
The region is a choice in your own account. A team that needs its records in São Paulo, or in a region in the European Union, selects that region on Amazon Web Services, Microsoft Azure, or Google Cloud.
That is how residency works with vermadev. You place the account where your obligations say the records should be.
Who does what
The terms draw this line. This page follows them.
| Topic | vermadev | You |
|---|---|---|
| Cloud account | We operate through the access you gave. We do not pay the cloud bill. | You own the account, the cloud, the region, and every cloud charge. |
| Records | We do not take custody, and we do not keep a backup on our systems. | You own the data and decide what is stored. |
| Backups and recovery | We are not your backup, and we are not your disaster recovery. | You own backups, snapshots, and recovery. |
| Access | We use it to run the platform, and we stop when you remove it. | You grant it, and you can revoke it. |
| The account itself | We take care with the access we have. | You take care of the account, the devices, and the keys you hold. |
| People in the product | The software follows the roles you set. | You create the accounts and remove people who leave. |
| AI | We provide the feature. We do not train other customers’ models on your records. | You choose the models and review the output before you rely on it. |
| Fees | If fees go unpaid we may pause updates and our operation. We do not delete the records in your account. | You pay our fees, and you pay your own cloud bill. |
Stop paying us and the platform keeps running
If fees go unpaid we may pause updates and our operation. We do not delete the records in your account, and the terms do not require us to keep operating the platform for you.
What you keep is the account, the platform in it, and the data. The last version we shipped can keep serving your team, at your cost and at your risk. What you lose is our updates, our support, and the access we withdraw on the way out.
We operate. You own.
Report a vulnerability
Use the button. It opens a note to our security contact, already started for you.
Name the part of the product and what you saw. Leave secrets, customer records, and a working exploit out of the first note.
Questions a review usually asks
Which clouds does vermadev run on?
Amazon Web Services, Microsoft Azure, and Google Cloud. You choose the account and the region. The platform is installed there, and the records stay there.
Do you keep a copy of our database?
No. A deployment in your account stays in your account. We do not take custody of those records, and we do not keep a backup of them on our systems.
What happens if we remove your access?
We cannot ship another update, and we cannot operate the platform for you. The records stay. The version that is already running stays up.
Where do the keys live?
In the cloud account you own. We do not hold a separate copy of your records.
Do you train models on our records?
No. We do not use your records to train models for other customers. You choose the model, and the work is meant to happen with the deployment in your account.
What if an update fails?
The version your team is already using stays in place. A failed step does not replace it.
What do we lose if we stop paying?
Our updates and our operation. The account, the platform, and the records stay where they are. The cloud bill remains yours, because it was never ours.
How do we report a security issue?
The button on this page, and the same action inside vermadev settings. Tell us where in the product and what you saw. Leave secrets and customer records out of the first note.