# On your servers, or ours.

> AutoST deploys as a container on your own infrastructure, or as an instance hosted by Zyberum. The backend serves the API, the dashboard and the docs; the Carbyne agent runs on your bench. AutoST is multi-tenant with six roles and groups that own components, licensed per component count plus feature flags. Test results and reports stay with your organisation.

Run AutoST as a container on your own infrastructure, or let Zyberum host it. Multi-tenant with role-based access and groups. Test data and reports stay with you.

Source: https://auto-st.com/deployment

AutoST runs as a single container you host yourself, or as a managed instance run by Zyberum. Either way, your test results belong to you.

## Hosted or on-prem

### On your servers

Deploy the container on your own infrastructure. The ECU, the agent and the data never leave your environment.

### Hosted by Zyberum

We run the instance for you. You install the lightweight Carbyne agent on your bench and start testing.

## Roles, groups and tenants

### Roles

Six roles from user to admin, so engineers, leads and managers each see what they should.

### Groups

Group ECUs by project or vehicle line, with access control, to keep teams and suppliers apart.

### Licensing

Licensed per component count and feature flags. Upload a licence file; no per-seat surprises.

## FAQ

**Can we keep everything on-prem?**

Yes. AutoST runs as a container on your own infrastructure, with the agent on your bench, so test data and reports stay in your environment.

**How is it licensed?**

Per tested component plus feature flags, via a licence file. Talk to us for a quote that matches your number of ECUs and the engines you need.

**Who owns the test results?**

You do. Test results and reports belong to your organisation, whether you host AutoST or we do.

---
AutoST by Zyberum. Canonical page: https://auto-st.com/deployment
