Contact us

MyWorkspace by Intryl is a governed work-access portal that replaces fragmented VPN-style workflows with one browser front door under assignment and policy. It is built for organisations that need assigned access to office PCs, hosted desktops, cloud workspaces, and hybrid setups—without shipping laptops everywhere or maintaining parallel access tools.

After signing into the tenant portal, users see only the workspaces, environments, or operational resources assigned to them. Depending on deployment design, a launch target may represent an office PC, a hosted desktop, a Linux or Windows environment, a server-backed workspace, or an internal application. When a launch begins, the session is brokered through the platform and becomes available through a browser-oriented experience or another approved client path defined by policy. The endpoint device acts primarily as an access surface rather than the execution environment itself.

Yes. The platform is designed around controlled access to assigned environments rather than assuming every endpoint is permanently managed as a corporate workstation. Organisations can define policies appropriate to their own operational and security posture.

Yes. The public demo opens from the Demo entry point on this site and walks a safe sample tenant experience with representative flows. It is ideal for evaluation and stakeholder demos—not for production credentials.

The portal experience targets modern evergreen browsers on Windows, macOS, and Linux contexts customers already deploy. The goal is fewer bespoke fat clients—standard laptops and managed desktops stay in scope.

Users start from an HTTPS portal with tenant-aware assignments and policy—not from a thick client that flattens the network. Connectivity toward targets is brokered through paths aligned with your architecture, while administration, authentication flows, and audit-oriented signals stay with the portal tier.

At a high level, the platform resolves tenant context, validates assignments and policy server-side, brokers an approved launch path, and exposes the resulting environment through the configured access model.

In common deployment models, workload execution remains associated with the assigned remote environment while the endpoint device acts primarily as an access surface. This allows organisations to present operational environments through a more consistent access model without requiring every user device to become part of the internal trust boundary.

Depending on tenant design, environments may include office PCs, hosted desktops, Windows environments, Linux environments, macOS resources, cloud workspaces, server-hosted systems, or internal operational applications.

Yes. A single tenant may expose office PCs, hosted workspaces, cloud environments, server-backed systems, operating-system environments, and internal applications through the same assignment and launch model.

Yes. A tenant may expose office devices, hosted desktops, cloud workspaces, internal systems, and operational environments through the same assignment and access model.

The tenant portal handles identity flows, assignment-aware presentation, and launch orchestration. Target environments remain separate operational systems reached through approved session paths rather than becoming part of the portal trust domain itself.

MyWorkspace is designed to reduce traditional VPN-heavy workflows for end users. After onboarding, users access assigned resources through the company portal and protected launch flow, while customer-specific network or edge controls can still be part of the deployment.

A tenant-aware portal, administrative controls, user and role management, assignment-aware launch flows, browser-oriented workspace access, and controlled connectivity toward office PCs, cloud workspaces, server-hosted environments, and internal operational resources.

No. MyWorkspace acts as a managed secure work access layer. It can work with an organisation’s edge, zero-trust, SSO, and target-environment controls instead of replacing every layer.

Administrators define users, roles, assignments, and available launch targets within the tenant context. The platform resolves those assignments server-side before presenting available environments or launch paths to the user.

MyWorkspace is not positioned as a direct replacement for every existing infrastructure layer. Organisations may continue using endpoint management, identity systems, VPNs, segmentation controls, or other operational tooling where appropriate. The platform focuses on assignment-aware workspace presentation, governed launch paths, browser-oriented access flows, and controlled connectivity toward approved environments.

Yes. MyWorkspace is designed to work alongside existing operational environments and infrastructure investments. Organisations may continue using current identity systems, hosted environments, office PCs, segmentation models, and operational tooling while introducing a more unified access and launch experience.

No. Tenant deployments may vary depending on operational requirements, infrastructure models, identity architecture, workspace types, and environment design. The platform is intentionally designed to support multiple operational patterns rather than enforcing one rigid topology.

Teams usually begin with a bounded pilot: targeted users, clear assignment policies, and success metrics around onboarding time and support tickets. Scale follows once the access model is proven—weeks-to-months horizons are realistic when prerequisites are aligned.

Use the contact form on this page or email the address listed alongside it. Include rough user counts, regions, and whether you need office connectivity, cloud workspaces, or both—that accelerates a tailored response.

Start with the Technology overview for architecture language, then open the public developer-oriented overview for trust boundaries and operational framing—linked from this contact page for convenience.

Commercial pilots, pricing, and rollout planning—use this contact form or email. Architecture, security review packs, and integration posture—reference the Technology pages first, then engage through the same channels with context.

Yes. Administrators can manage users and assign the workspaces, desktops, remote applications, or devices each person is allowed to access.

Sign-in happens through the company-branded portal flow. Where policy requires it, integrated multi-factor authentication is part of the journey—not bolted on inconsistently per device image.

Operational metadata and configuration are partitioned per tenant. Control-plane checks resolve in tenant context so cross-tenant launches are rejected by construction—not by informal convention.

The product direction favours standards-friendly identity flows where customers expect interoperability. Exact protocols and rollout windows belong in architecture review—use Contact or the Technology pages to start that conversation.

Yes, MyWorkspace supports second-factor authentication as part of the access flow where policy requires it.