Skip to main content
In-house flagship build

Building a remote-access platform over peer-to-peer

Our flagship build is the platform this site belongs to: a system that connects two machines across hostile networks, directly wherever the network allows, and keeps latency low enough for live screen control. Its Windows client is in early access today. Because it's our own, we can talk about it openly.

Rust and Go
Languages
Early access
Windows client
Encrypted
Every session
As code
Infrastructure

Shown as a first-party flagship build: Vexaro's own platform, the product this site belongs to. Client engagements are kept confidential, so the work we can talk about openly is our own.

The challenge

Connecting machines the internet doesn't want connected

The hard requirement was a direct connection between two machines across networks designed to prevent exactly that. It had to work without routing every session through a datacentre and be fast enough for live, interactive screen control. Everything else in the platform sits on top of solving that.

What made it hard
  • Establish direct connections through NATs and restrictive firewalls
  • Keep latency low enough for live screen control, not just file transfer
  • Avoid routing every session through a datacentre, for cost and privacy
  • Keep every session encrypted, with each side verifying exactly who it is connected to
What we built

Four layers, each in the right tool

We matched the language and the architecture to each layer rather than forcing one stack across the whole system. We bring the same judgement to client work.

1

A Rust core for speed and safety

It connects directly wherever the network allows, and through an authenticated relay when it doesn't, with every session encrypted and identity-verified. The performance-critical core is written in Rust for memory safety and predictable latency.

2

A Go backend

Accounts, devices and access rules are handled by a backend written in Go, the layer where readability and fast iteration matter most.

3

Desktop and mobile clients

A Windows desktop app, in early access today, with a mobile client in development.

4

Infrastructure as code

Every environment is defined as code, with monitoring, logging and backups built in, plus a Kubernetes option for self-hosted Enterprise installs.

The outcome

A platform we run on every day

We describe the result by capability and architecture, not invented numbers. This is the system we operate, and it shows that we ship hard things instead of only talking about them.

What it achieves
  • Sessions connect directly wherever the network allows, and through an authenticated relay when it doesn't
  • Live remote control stays responsive, with video that adapts to network conditions
  • Infrastructure is reproducible from code
  • Direct sessions are end-to-end encrypted; when a network forces a relayed connection, traffic stays encrypted in transit through Vexaro-operated relays
The stack

The stack behind the platform

Languages

Rust and Go.

Apps

A Windows desktop app in early access, with a mobile client in development.

Infrastructure & data

Containers and infrastructure as code, with monitoring, logging and backups built in.

Have a hard problem of your own.

The engineering behind this platform is the same we bring to client work. Tell us what you're building.