Tosca Cloud architecture

Your Tosca Cloud environment consists of these main components:

  • The Tosca Cloud web application, where you create, store, and run your test artifacts and handle all related administrative tasks, such as user or subscription management.

  • The user machines from which users access Tosca Cloud to create tests.

  • The agent machines where you run your tests. These are so-called team agents, which are remote or virtual machines hosted within your own network. Alternatively, you can use cloud agents, which are hosted in the Tricentis cloud and fully maintained by us.

This diagram displays the basic architecture of Tosca Cloud and how it connects to user machines, agents, virtual machines, Tosca on-prem, and the system under test.

Tosca Cloud architecture

Ports and connections

Generally, you don't need to open any ports or establish any connections on any machine.

The only exception to this are Simulator agents, who may need a port for specific use cases. For example, if you want to simulate a service listening on port 8080, you may need to open that port.

You access Tosca Cloud via browser from within your own company network. As long as your company firewall and proxy allow access, there's nothing else you need to do for Tosca Cloud. The communication between team agents and the web application happens via WebSocket, with an HTTPS binding.

Local components

Tosca Cloud has these local components:

  • Launcher, which Tosca Cloud uses to install and manage components on user or agent machines. The only exception to this are Simulator agents, which you have to copy-deploy manually.

    Launcher is versioned and controlled by Tosca Cloud. This means that Tosca Cloud invokes silent auto-updates, if necessary. Reinstalling Launcher also reinstalls all components it manages.

  • Browser extensions for Chrome and Edge, which Tosca Cloud uses to automate these browsers during scanning and test runs. Browser extensions are versioned, but Tosca Cloud doesn't trigger auto-updates.

All Tosca Cloud binaries are signed.

Identity management and authentication

Tosca Cloud uses Okta (opens in new tab), but don't worry. You don't need to know Okta. Administrators can perform all user management tasks directly in Tosca Cloud.

Compatibility with Tosca on-prem

Tosca Cloud is compatible with Tosca on-prem version 16.0 or later. They have some components in common. However, silent updates for Tosca Cloud don't affect Tosca on-prem because local components are in separate folders.