01
The workspace lives somewhere else
Cloud-only agent products make remote infrastructure the default place for source, sessions and operational context.
Solutions / teams
Collaborate without giving up the operating boundary.
OpenLink gives organizations a native multi-tenant workspace that can run locally, inside company infrastructure, or with optional cloud capability from VTSLX AO.
Product organization
BOUNDARY ACTIVEOWNER
Platform lead
ADMIN
Engineering
MEMBER
Product team
WORKSPACES
Core product01
Customer portal02
Research03
Personal sandbox04
Explicit rolesTenant-scoped dataProject-scoped runtime
The cloud-only default
A collaboration tool should not decide where the company operates.
Most agent platforms begin with a hosted workspace and ask the organization to adapt its controls around that choice. OpenLink begins with an explicit operating boundary.
02
Collaboration arrives before boundaries
A shared product is not the same as a tenant model. Teams still need explicit membership, roles and project-level separation.
03
Provider choice becomes platform policy
Model credentials, execution location and deployment decisions should stay visible instead of being silently selected for the team.
Native multi-tenancy
Personal work and organization work belong in the same product—not the same data scope.
OpenLink models organizations, membership and workspace scope directly. People can keep a personal workspace while joining shared organization workspaces with explicit roles.
ORGANIZATION
PERSONAL SCOPE
Private experiments
Owned by the individual identity domain.
ORGANIZATION SCOPE
Shared delivery
Visible through membership and role policy.
Organization ownerMANAGE
Workspace adminOPERATE
Project memberCOLLABORATE
One product, three operating choices
Choose the boundary project by project.
Local, self-hosted and managed cloud are deliberate deployment choices. The product model stays recognizable while identity and data domains remain separate.
OPENLINK LOCAL
Keep the complete workspace on the machine.
Identity, project state, sessions, storage and runtime services operate as an independent local domain.
SELF-HOSTED
Run the control plane inside your infrastructure.
Use the same workspace contracts while your organization owns the deployment boundary and operating policy.
VTSLX AO CLOUD
Add managed cloud capability by choice.
Use project-scoped cloud runtimes, remote access and organization controls when the workflow needs them.
Control surface
The controls teams need are part of the architecture.
OpenLink treats tenancy, identity and project execution as product primitives. VTSLX AO extends that model with cloud control-plane capabilities when an organization opts in.
01
Independent identity domains
Local and cloud environments keep separate identities and records. Moving between them is an explicit operation, not background replication.
02
Organization-aware access
Personal and organization workspaces share one product model with owner, admin and member roles enforced at the data boundary.
03
Project-scoped runtime
Each project owns its workspace, runtime services and durable state, so execution remains attached to the correct project boundary.
04
Cloud controls when needed
VTSLX AO adds project routing, region placement, entitlement and usage controls for organizations that choose managed cloud execution.
Start with the boundary
Make collaboration fit your operating model.
Inspect OpenLink's runtime choices, then decide which projects stay local, which run in your infrastructure and which use VTSLX AO Cloud.