Current product fit
Evaluate the capability. Keep the qualification attached.
This matrix turns the site's current product boundaries into one buyer-facing reference. It describes approved architecture and implementation-scoped capability without asserting universal availability.
Review the matrixDirect answer
Current fit is specific to the work and the selected implementation.
SautX product fit depends first on where the work executes, then on the exact product, protocol, runtime, integration, Site, deployment, policy, endpoint, and release. A category description or visible interface does not establish that a particular capability is available.
- Start with a non-sensitive workflow and required result.
- Select Secure Workspace, Agentic Workspace, or an explicit handoff according to the execution boundary.
- Confirm the exact capability, retained responsibilities, evidence, and limitations before making a commitment.
Version 1.0 · August 11, 2026
Capability and qualification stay together.
This matrix is a public decision aid, not a contract, service-level commitment, certification, assurance report, or complete release inventory.
| Area | Current approved description | Confirm before use |
|---|---|---|
| Secure Workspace execution | Governed interaction with an existing protected application, server, desktop, or web resource through an eligible application or protocol runtime. | Application, protocol, runtime image, integration, Site, deployment, endpoint, and release. |
| Secure Workspace controls | Presentation and implementation-scoped view, control, clipboard, upload, download, duration, recording, and related session capabilities. | Control availability and depth vary by protocol, agent, runtime, policy, deployment, and release. |
| Secure Workspace protocol coverage | The architecture covers web, SSH, RDP, VNC, and X11-based workflow patterns. | Coverage does not imply identical feature depth or current availability for every protocol or target. |
| Agentic Workspace execution | One selected execution backend for a request: eligible model, sandbox, application, or allocated endpoint, with selected files, tools, and compute. | Provider, model, tool, endpoint, runtime, route, Site, deployment, policy, and release. |
| Agentic private and shared state | Private Session work remains separate from shared Workspace state; publication is an explicit attributable operation. | Exact collaboration, review, retention, and destination behavior depends on the selected implementation and policy. |
| Agentic human review or control | Supported endpoint sessions can include live display and human review or control where policy and implementation permit. | Endpoint, provider, runtime, transport, Site, deployment, policy, and release determine availability. |
| Using both products | An explicit handoff when Agentic work crosses into a separately governed protected-system session. | Human participation alone does not require both products; the execution boundary selects the workspace. |
| Customer-controlled deployment direction | SautX is designed for customer-controlled deployment with Admin, User Portal, Resource Edge, and Site responsibilities. | Supported packaging, placement, transport, availability, operations, and integrations remain deployment- and release-specific. |
| Configured workspace composition | Users start with the task, administrators define the boundary, and SautX automatically composes approved infrastructure into a governed workspace. | Automation depends on configured eligibility, policy, resource, provider, runtime, integration, Site, deployment, and release; it does not imply independent inference, zero administration, instant readiness, or support for every resource. |
Scroll horizontally to review the complete matrix.
Retained responsibilities
Deployment still matters.
01Identity providers retain authentication, federation, account, recovery, and upstream revocation responsibilities.
02Protected targets retain native permission, configuration, patching, availability, and system-of-record responsibilities.
03Sites retain networking, certificates, secrets, endpoint, runtime, logging, retention, and operating responsibilities.
04Customers retain lawful purpose, policy, approval, disclosure, review, and operating-procedure responsibilities.
Start with the work
Bring one workflow. Confirm exact current fit.
Describe non-sensitive product, protocol, runtime, integration, Site, deployment, endpoint, and release context together with the required result and retained responsibilities.
Contact SautX