From marketplace purchase to your first login, in an account you own.
The listing isn't published yet.
Cloud-Vex can't be bought today — marketplace listings are in progress. This page describes the flow as it is built, so you can review it, check it against your own change process, and know exactly what you'd be signing up for. Join the waitlist and we'll write when it's live.
You buy Cloud-Vex through your cloud provider's marketplace, on the bill you already have. There's no new vendor to onboard, no procurement record to open with us, and on AWS the spend can count toward a committed-spend agreement.
Pick a term — monthly, annual, two-year or three-year — or start on the 30-day trial, which is acquired the same way and costs nothing. Terms and prices are on the pricing page; the trial runs full functionality for 30 days, capped at one account, one region and one scan.
The marketplace hands you straight to a short form, with your purchase already verified at the top of it. Three fields: your organisation, your name, and the email the licence key should go to.
The link that carries you here is good for 30 minutes and is tied to the subscription it was issued for. If you leave it too long, start again from your marketplace subscriptions page rather than reloading.
Submit the form and your key arrives by email, addressed to whatever you typed in the field above. Treat it like a password — it authorises your deployment.
On AWS, you don't have to wait for the email to deploy. The same screen offers a deploy button, and your key is carried into it without ever being displayed on the page — the link hands it straight to your own AWS console. So the email is your copy to keep, not a step you are blocked on.
On Azure, the key is shown on screen. Azure's deploy link has no way to carry a parameter into the portal, so you copy the key from this page and paste it into the template's licence field yourself once the portal opens. The same fallback applies on any marketplace if the email fails to send — the page shows the key so you have a copy either way.
It goes live when the marketplace confirms the purchase. That confirmation is a separate message from your cloud provider and usually lands within a few minutes — often before you finish typing. You can start the next step immediately; the key activates on its own.
On AWS, that button opens the CloudFormation console with the current template loaded and every parameter filled in — your licence key, the released application image, the region you picked on this page, and a short prefix taken from your organisation name that every resource the stack creates is named after.
On Azure, the button opens the portal's custom deployment page with the template loaded, but Azure's deploy link has no way to carry parameters into it — you paste the licence key from this page into the template's licence field, and choose the resource group and region inside the portal itself, once it opens.
On Google Cloud, there's no launch button here yet — the marketplace signup flow doesn't publish a one-click template for GCP today. Deploy by hand instead (below), following the GCP requirements in the reference guide, which also needs a GKE Autopilot cluster with Config Connector running first — the one thing the other two clouds don't ask for.
Nothing is deployed until you say so, on any of the three. Every button is a pre-filled form, not an action; you review the template exactly as you would any other and create the deployment yourself — we have no access to your account at any point, before or after.
The stack builds the hub: the application, its database, its web interface, its scheduler and the roles it uses to read your account. All of it lands in your account, in the region you chose. Expect this to take a few minutes, and expect it to fail early and clearly if your permissions are short of what the hub needs.
Deploying by hand instead — through your own pipeline, Terraform, or a reviewed copy of the template — is entirely supported on every cloud, and it's the only path on GCP for now. The launch button is a fast path where it exists, not the only one.
When the stack finishes, its outputs carry the address of your Cloud-Vex interface. The credentials for the first administrator are not in those outputs, and they are not in any email — the stack writes them into your own cloud's secret store, and nowhere else.
Read the secret with the same access controls and audit trail you already apply to everything else in there, then open the interface and sign in.
You are required to change it. The first sign-in will not let the administrator go any further until that password has been replaced with one of your own choosing. It is not a prompt you can dismiss and come back to, so the credential the stack generated stops working the moment you are in — and a copy of the secret left lying in a terminal history or a ticket is worth nothing by then.
The new password must be at least 12 characters, with at least one uppercase letter, one number, and one special character. This isn't configurable — it applies to this account the same way for every deployment.
This is the only local account there will ever be — there's no way to create another one. Everyone else signs in through an OIDC identity provider connected afterward, with what they can do controlled by roles and claims rather than individual accounts. Keep this one's credentials safe even once that's set up: it's break-glass access for if the identity provider is ever unreachable.
Why this way. A password mailed to you exists in an inbox forever; a password in a stack output is readable by anyone who can describe the stack. Putting it in the secret store means the credential is governed by your policy from the moment it exists, we never see it at all, and the forced change means it is short-lived even there.
The licence email never arrived. Check the address you typed on the form, then spam. If it truly is not there, write to us and we'll resend it against your subscription.
The purchase hasn't confirmed. You'll hear from us before the day is out, and we alert ourselves within the hour. If the marketplace reports a payment problem the email will say so plainly and point you at your provider, because that is the one case we can't fix from our side.
The stack failed to create. Almost always permissions or an account limit — the failure event in your own console names the resource. Nothing is left behind that costs money; delete the failed stack and run it again once the block is cleared.
The interface won't accept the licence key. If the purchase confirmed only after you deployed, give it until the next check-in. If it persists, send us the organisation name from the signup form — never the key itself.
Want to see a setup in action? The video library will walk you through every step of this flow. If any of it still doesn't fit your environment, email support@cloud-vex.com with your concern — we answer within one business day.
Join the waitlist