Included with Power and Team plans

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.

No additional cost — it comes with your AI credit plan. Testver Cloud is included with the Power and Team plans. There is no hosting fee and no separate subscription: buy the plan, create the workspace, and it is yours.

Your own subdomainRuns 24/7Continuous backupsAutomatic HTTPSSelf-healingOne machine per workspace
acme.cloud.testver.com

Your workspace

acme

Healthy
Status
Running
Version
Testver 1.1.2
Last backup
18 minutes ago
Off-site mirror
In step
Certificate
Renews automatically
Uptime, last 30 daysno interruptions
Awake
24/7Awakeschedules fire overnight
Machine per workspace
1:1Machine per workspacenever co-tenanted
Backup locations
Backup locationsplus an off-site mirror
Things to install
0Things to installit is a web address

Testver on your laptop stops being enough the moment a schedule needs to fire overnight, a second person needs the same test history, or CI needs somewhere to talk to. A tool that only exists on one machine quietly becomes one person’s tool.

Testver Cloud is the same application, running on a private server we build, patch, back up and repair for you. You get a web address of your own, everyone on the team signs in to the same place, and nobody installs anything. It comes with the Power and Team plans — one workspace per plan, created from your dashboard in about a minute.

A testing tool that sleeps when you do isn’t infrastructure

Everything below is a consequence of Testver living on a laptop rather than a server. None of it is a limitation of Testver itself — it is a limitation of where it is installed.

  • Scheduled runs only fire while the machine is awake and connected.
  • Test history, credentials and recordings live on one person’s disk.
  • CI pipelines have no address to call.
  • Upgrades, backups and OS patching are somebody’s side job — until they are nobody’s.
Getting started

How Testver Cloud works

Four steps, in order — and none of them is a migration.

  1. 1

    Create your workspace

    Open Cloud in your dashboard and press Create my workspace. The name you choose becomes your address — your-team.cloud.testver.com — and you set the password you will sign in with. On a team plan, the team owner or the platform manager does this.

  2. 2

    It builds itself

    A private machine is provisioned, Testver is installed, and a certificate is issued for your subdomain. About a minute later the address works, and there is nothing for you to configure.

  3. 3

    Sign in from anywhere

    Open your address in a browser. Same Testver, same projects, same reports — from a laptop, a second laptop, or a phone on the way to a stand-up.

  4. 4

    Point it at your repository

    Connect the Git repository holding your tests and your workspace stays in step with the branch you nominate.

What you get

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 plan is 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.

What "managed" actually means

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
Where it runs
European data centres
Machine size
Set by your plan, and resizable later
Backups
Scheduled, plus an off-site mirror in a second provider
Included with
Power and Team plans — one workspace per plan
Who manages it
You — or, on a team, the 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.

Questions

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?

Workspaces run in European data centres. 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?

It comes with the Power and Team plans. Open Cloud in your dashboard, choose your name and press Create my workspace — it is ready in about a minute. An administrator can also grant it to an individual account outside those plans.

Does every team member get a workspace?

No — a team plan is 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.

Ready to upgrade your test suite?

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.