Remote work in one workspace
Bring together RDP, SSH and Mac remote control through VNC. Manage profiles, sessions, remote tasks and file transfers in the context of each host.
RELAYNE · NATIVE WINDOWS WORKBENCH
Remote access. Verified recovery. Shared operational knowledge.
From the first look at a host to documented repair evidence: Relayne brings remote sessions, diagnosis, reviewed tasks and your team’s knowledge into one workbench.
For IT administrators, managed service providers and support teams.
In development · Validate a pilot environment together
More than a connection to a screen.
Remote access is the starting point. The value grows when diagnosis, changes and the next support ticket build on verifiable knowledge.
Recovery with a rehearsal
Rehearse Windows service repairs in a suitable clone first. Compare clone and production, check HTTP functionality and approve the specific production run separately.
Living recovery plans
Track review intervals and rehearsal expiry. Read-only comparisons can detect changes and invalidate previous evidence; automatic comparisons require consent for the current session.
Verify application outcomes explicitly
Turn approved descriptions into reviewable HTTP criteria. Check status, text, login sequences and JSON rather than treating a running service alone as proof of recovery.
Diagnosis with traceable evidence
Compare cause hypotheses and keep contradictions and missing information visible. Runbooks, timelines and redacted result reports support clear handoffs.
Share operational knowledge
Demonstrate procedures and prepare reviewable workflows. Share masked images and annotations; team input remains subject to roles and explicit approvals.
Review repair packages before use
Verify signed packages through publisher keys, a trust store and revocation. An import remains a reviewable draft until a task is explicitly started.
Connect infrastructure deliberately
RemoteApp, gateways and enterprise sign-in extend the workbench. Required Windows components, provider configuration and the target environment determine suitability.
From an incident to a verified outcome.
- 01
Understand
Capture the case, target and observed failure. Collect diagnostic evidence and review proposed repairs.
- 02
Rehearse
Select a suitable clone, compare initial conditions and run explicit application tests.
- 03
Approve
Inspect the current production state. Explicitly approve the change for this plan and target.
- 04
Verify
Document the change and application outcome. Reuse the redacted report, runbook and reviewed knowledge in future cases.
Operator control is part of the workflow.
An AI suggestion does not start a connection. A successful clone test does not replace production approval. Missing, stale or conflicting evidence remains visible and cannot establish a confirmed repair.
Read the example view
- What is shown?
- The “Plan, check & learn” workspace compares seven fixed local scenarios, including a stopped service, DNS errors and TLS errors.
- What can you explore?
- Expand individual scenarios to inspect their checks, compare expectations and copy the simulation comparison as JSON.
- How should results be read?
- A matching simulation result describes this test model. It does not establish the cause of a real incident or prove successful recovery.
Example: an application cannot be reached
Select the local example, examine the simulated DNS checks and compare them with the stopped-service and TLS scenarios. Use the differences to discuss which evidence a real diagnosis would require. This example does not connect to or change a production system.
Security Investigator: a separate investigation service
Security cases use a separate service with a web interface, persistent case queue and shared MCP case API, accessible from Relayne. Live sources and the A1 capability are disabled by default.
Before your pilot
Is Relayne generally available?
Relayne is in development. We discuss a suitable pilot scope and validate requirements and acceptance in your environment. The documented development distribution is unsigned.
Which systems are supported?
The workbench runs natively on Windows. RDP, SSH, Mac VNC and additional integrations have individual requirements. Compatibility with your servers, gateways and identity providers needs explicit validation. Mac VNC is unencrypted and requires a trusted LAN or VPN.
What does recovery currently cover?
The documented starting workflow combines a Windows service start with an explicitly defined HTTP functionality test. Clone rehearsals require suitable Hyper-V/WinRM infrastructure. Scope and recovery limits are agreed for the pilot case.
What does “verified” mean?
Local software tests and results in your target environment are different evidence. A confirmed repair requires matching case, plan and targets, plus actual change and application evidence. Infrastructure-dependent live acceptance remains necessary.
A focused start with your support case
- 01
Define the case
Describe the target system, symptom and intended application test. Name the support owner and approver.
- 02
Validate the environment
Check the Windows workbench, access permissions and connections. Clone recovery requires suitable Hyper-V and WinRM infrastructure; Mac VNC requires a trusted LAN or VPN.
- 03
Agree acceptance
Agree the available development scope, test evidence and explicit production approval. Compatibility and live acceptance must be verified in your environment.
Which operational case would you like to handle better?
Bring a specific support or recovery case. Together we define requirements, pilot scope and measurable success criteria.
Discuss a pilot