Orcraft setup overview

This is how a typical Orcraft setup looks like.

Controller and endpoints

A typical Orcraft deployment consists of a single controller and endpoints. The controller orchestrates test execution, distributes the test package and collects results, while each endpoint receives the package and executes the assigned steps. Endpoints are registered with the controller prior to use.

Internet access

Endpoints need no internet access: the controller delivers the test package to them and updates the endpoint application. The controller itself reaches the external network to check for Orcraft updates, to sign in and renew licenses, and to check the status of suite repositories.

CI runner

A CI runner is not an endpoint: it is a separate controller installation running in CLI mode, using the same configuration exported from the original controller as a CI snapshot. This allows a pipeline to reproduce a run exactly as it was configured, without a GUI.

Controller roles

The same controller can be used for test development, manual execution and as a CI runner, or these roles can be split across separate controller installations, each dedicated to a single function. In either case, controllers can share endpoints between them, allowing the same infrastructure to serve development, manual and CI workflows.

Remote endpoints

Endpoints may also be reached over an external network, allowing distributed teams and remote labs to participate in the same session. Communication between the controller and its endpoints is secured with mutual TLS and token-based authentication, ensuring that connections beyond the internal network remain safe.

Single machine

Endpoints are not a strict requirement. The controller can execute structured tests on localhost, making it possible to develop and run suites on a single machine before extending execution to additional endpoints.

Next steps

Ready to install? Start with Prerequisites, then follow Getting started. Adding endpoints registers and licenses the lab machines, and Licensing explains the plans, the renewal and the license states. The System reference covers compatibility, permissions and optional integrations.