Skip to main content
Version: 2026.09

Introduction

Install takes your organization from nothing to a working Istari Digital Platform: the control plane, at least one agent, the CLI (stari), and a job on that agent using an open-source module.

Your infrastructure or IT team deploys the control plane — the shared services your organization runs so teams can use the web app, agents, and integrations — and puts agents on hosts that can reach your data. An organization administrator then configures the organization from the web app; those cross-cutting tasks are collected under Admin.

The control plane runs in your own virtual private cloud (VPC), on a Kubernetes cluster, using Helm charts, an object store, and a PostgreSQL database. File contents stay in that object store; the platform tracks relationships in a graph database.

Plan on about two to three hours for the platform installation itself. Expect longer if you still need the prerequisites in place, such as the Kubernetes cluster, the database, or TLS certificates — Infrastructure Prerequisites lists everything you need before you start.

When the platform and your first agents are running — and each agent has passed the Open Text job at the end of its OS guide — continue in Connect to add modules for your other engineering tools and bring their data onto the platform. The agent pages here stay useful long after the first deploy — you come back to them whenever a new machine or a newly deployed tool needs to run jobs.

Download installers, container images, Helm charts, and registry credentials from the Istari Customer Portal (https://portal.istari.app/welcome; access is by invitation).

What you will find here​

  • Customer Portal — Download packages and generate registry credentials.
  • Install control plane — Prerequisites and the Helm install for the platform services; follow these pages in sidebar order.
  • Account — Sign up, sign in, or recover access to the web app.
  • Install Agents — Put an Istari Digital Agent on each machine that should run jobs, then return to these pages whenever you add another machine. Each OS guide ends by deploying Open Text so you can test the agent without a licensed tool.
  • CLI — Install stari on Linux or Windows (and macOS when that is the agent host) so you can publish modules and manage keys. Start with Get started.
  • Operate the installation — What you need after the first deploy: usage metrics, updates, migration guides, the Secure Connection service, and Zitadel user management.
  • FAQ — Short answers to common planning questions, such as whether the Windows agent can run as a service or the agent can use a SOCKS proxy. See Install FAQ.

Checklist​

  1. Prepare infrastructure and install the control plane
    Follow the control-plane pages in order, starting with Infrastructure Prerequisites (VPC, cluster, object store, database, certificates) and ending with Istari Platform Installation. When the install succeeds, open the Istari Digital web app and sign in to confirm the platform is running.

  2. Create an account and sign in Follow Account Management to sign up or sign in. If you are the organization administrator, continue under Admin to invite users, assign roles, and configure access policy.

  3. Install agents, the CLI, and test with Open Text On each machine that should run jobs, install an agent. On Linux or Windows (and on macOS if that is the agent host), install and authenticate stari. Finish the OS guide's last step: put Open Text on the agent, publish it, and run @istari:extract on a small .txt file. That proves the agent before you add licensed tools.

  4. Connect your other tools Continue in Connect to add modules for CAD, MBSE, solvers, and third-party applications, and to bring their data onto the platform. When one of those tools runs on a machine with no agent, repeat step 3 for that machine.

  5. Optional: exchange Resources with a partner organization Install the Secure Connection Service so an organization administrator can set up connections to a partner, then hand over to Share.

If you get stuck, contact support@istaridigital.com.

Audience​

Control plane installation: DevOps engineers or IT administrators with administrator-level access to your cloud provider (for example the AWS Console), the ability to deploy and manage Kubernetes clusters and Helm charts, and access to the hosts where agents will run.

Agent, CLI, and first-job installation: the same IT audience, plus anyone who administers a workstation that should run jobs (Windows, Linux, or macOS).

Organization setup: organization administrators, who need only a web app account with the admin role.

Conventions​

Commands: kubectl apply -f
File paths: /etc/config/
Variables: <variable_value>