Your own Testver, always on
The full Testver application on a machine we look after, at your own address — awake at any hour, from any device.
- Awake
- 24/7Awakeschedules fire overnight
- Machine per workspace
- 1:1Machine per workspacenever co-tenanted
- Backup locations
- 2×Backup locationsplus an off-site mirror
- Things to install
- 0Things to installit is a web address
How Testver Cloud works
- 1
Create your workspace
In your dashboard, press Create my workspace; the name you choose becomes your-team.cloud.testver.com.
- 2
It builds itself
A private machine, Testver installed, a certificate issued — about a minute.
- 3
Sign in from anywhere
Same Testver, same projects, same reports — from any device.
- 4
Point it at your repository
Your workspace stays in step with the branch you nominate.
Everything Testver Cloud handles for you
Awake when you are not
Schedules fire overnight and at weekends because the machine never goes to sleep, closes its lid, or joins a different Wi-Fi network.
One place for the whole team
A team gets exactly one workspace. Everyone signs in to it and sees the same runs, history and reports; the team owner and one platform manager look after it.
Backed up continuously
Your workspace is backed up on a schedule and mirrored to separate storage in a second provider, so one failure is never the only copy.
Repairs itself
The workspace is watched. If the application stops answering it is restarted automatically, and a machine that cannot be revived is rebuilt from the latest backup.
HTTPS, handled
Your subdomain gets a certificate automatically and renews it on its own. There is no certificate to buy, install or remember.
Upgraded for you
New Testver versions are rolled out to your workspace. You do not schedule a maintenance window or run a migration.
The parts you would otherwise be on call for
Hosting something is easy until it breaks at 3am. These are the jobs Testver Cloud takes off you — not as a promise, but as machinery that runs whether or not anyone is watching.
It watches itself
The workspace is health-checked continuously. An application that stops answering is restarted without anyone being paged.
It rebuilds itself
A machine that cannot be revived is replaced and restored from the most recent backup, rather than waiting for someone to notice.
It keeps a second copy
Backups are mirrored to storage at a different provider, so one provider having a bad day is never the same as losing your history.
It renews its own certificate
HTTPS on your subdomain is issued and renewed automatically. Nobody diarises an expiry date.
The specifics
- Your address
- your-name.cloud.testver.com
- Isolation
- One private machine per workspace — never shared
- Machine size
- Set by your plan, and resizable later
- Backups
- Scheduled, plus an off-site mirror in a second provider
- Available on
- Team plans, as an add-on — one workspace per team
- Who manages it
- The team owner and one platform manager
Nothing here locks you in: a Cloud workspace runs the same Testver you would run yourself, on the same projects, in the same repository.
Testver Cloud, answered
Is my workspace shared with other customers?
No. Each workspace is its own private machine with its own address, its own storage and its own credentials. Nothing is co-tenanted.
What happens if the machine fails?
It is monitored continuously. An application that stops responding is restarted automatically; a machine that cannot be recovered is rebuilt and restored from the most recent backup.
Where is my data stored, and is it backed up?
Your data stays on your workspace’s own private machine, which is never shared with another customer. Backups are taken on a schedule and mirrored to a second, independent storage provider, so a single provider failure never leaves you without a copy.
Can I move off Testver Cloud later?
Yes. It is the same Testver application working against the same Git repository — you can go back to running it yourself without changing your tests.
Do I still need my own machine for anything?
Only if you want it. You can keep running Testver locally as well; the Cloud workspace is an addition, not a replacement, and both work against the same repository.
How do I get one?
Testver Cloud is an add-on for Team plans. Add it on the pricing page when you buy or renew your team plan, or later from Cloud or Billing → Add-ons in your dashboard; it is prepaid for the same term as your plan and renews with it. Once it is active, open Cloud, choose your name and press Create my workspace — it is ready in about a minute. There is no password to invent: Open & set up takes you to Testver’s own first-time setup, where the team owner or platform manager creates the administrator account.
Does every team member get a workspace?
No — a team has one shared workspace, which is the point. The team owner, and one member the owner names platform manager, create and manage it; everyone else signs in and uses it. Ending the workspace or downloading its data is reserved for the owner.
Keep your framework. Add AI and a premium toolset.
Set up in minutes. Self-host on your own hardware. Describe a test in plain English and get working code in your own framework — in a fraction of the time.