The session
What you get once the far machine says yes.
-
Remote control
The far screen with its keyboard and mouse, in a window or full screen.
-
Multi-monitor
Pick which of the host’s displays you are watching, and switch during the session without reconnecting.
-
Ctrl+Alt+Del and lock screen
Sent as one key each, and adapted to what the far machine actually is — a Windows host gets the real combination, everything else gets its equivalent.
-
Three quality presets
Best, balanced or performance. The preset is not just remembered: it is written into the default the client sends at login, so the encoder on the other side obeys it.
-
Hardware decoding
On or off, read by the codec layer when it decides which encoders it may use.
-
Frame rate, latency and codec on screen
Live figures while you work — frames per second, round trip in milliseconds, the codec in use and the bitrate it is aiming for.
-
Session recording
One control records what you are watching to a video file on your own machine.
-
Remote audio
What plays on the host plays for you too, inside the same session — and the host can leave audio out when accepting.
-
Voice call
Talk to the person at the other end over the session itself, without a second tool and without a phone number.
Files
Moving things between the two machines, and the record of it.
-
Dual-pane file transfer
Your files on the left, theirs on the right, with a queue underneath and jobs you can cancel mid-flight.
-
Both directions, during the session
Send and fetch while you are still working, not as a separate mode you have to switch into.
-
Host-side file audit
The host gets its own panel naming every file read off the machine or written to it, with the path and the direction. It is the host’s record, not the visitor’s.
Clipboard and chat
The small channels that save a phone call.
-
Clipboard sync
Text follows the clipboard between the two machines — and the host decides, connection by connection, whether it is shared at all.
-
Clipboard history
What crossed, on your side, so the thing you copied three steps ago is still reachable.
-
Chat
A message channel running alongside the session, for whoever is sitting at the other end.
The network
How the two machines find each other, and who carries them.
-
Direct first, relayed only if it must be
Delta tries to connect the two machines to each other and falls back to a relay only when the network refuses. Fewer hops whenever the ports allow it.
-
Our relay, in the EU
When a relay is needed it is relay-eu1.altovar.net: our machines, our image, inside the EU. Nobody else sits in the middle of your session.
-
Or your own infrastructure
Rendezvous, relay, API and key are four separate fields. Fill them in and the client talks to your servers instead of ours.
-
Port forwarding
Forward a local TCP port to the remote machine and reach a service that was never exposed to the internet.
-
LAN discovery
Finds other Delta devices on the same network by broadcast, without involving the rendezvous server at all.
-
Wake on LAN
Send the magic packet to a machine that is asleep, from the same screen you connect from.
-
SOCKS5 proxy
Type, host and port. All three describe one proxy, and changing any of them rebuilds it in the core rather than storing a preference nobody reads.
-
Diagnostics
Memory, the disk your recordings and transfers land on, and whether the rendezvous server actually answers — measured, not assumed from a status pill.
Who gets in
Every gate between a stranger and your screen.
-
Host mode with an explicit accept
Starting host mode forces every incoming connection through a click on the machine being connected to, even when the caller already has the password.
-
Five permissions, decided at the door
Keyboard, clipboard, audio, files and restart are switches on the accept dialog. They are the host’s to set, per connection, before anything is granted.
-
One-time, permanent, or both
A password that changes every time host mode restarts, one that does not, or both accepted at once — a choice the host makes rather than one the product makes for it.
-
Two-factor on the host
A time-based code checked before an incoming connection is accepted, set up from a standard authenticator URI.
-
Trusted devices
Listed and revocable. Nothing in the interface can add one: an entry appears only after a successful two-factor login from that hardware.
-
The settings pane behind its own password
Lock the settings and the machine can be left running host mode without leaving its configuration open to whoever walks past it.
-
Auto-disconnect on idle
Never, or after five, fifteen, thirty or sixty minutes. The timer is armed in the core for incoming sessions, not kept as a note in a file.
-
Sign in with an Altovar account
The account layer the rest of the catalogue uses, over an authorisation code exchange bound to the client that started it. Or skip it entirely and use Delta without an account.
What stays with you
The data Delta keeps, and where it keeps it.
-
Address book
Saved devices in groups, exported to and restored from a file you hold. There is no server copy, because there is no server for it.
-
Session statistics
Sessions, minutes, files and bytes moved, average frame rate and latency, per device — from sessions that actually happened, kept on your machine.
-
History per contact
Open a device in the address book and read what happened the last times you connected to it.
-
Secrets in the operating system’s keyring
The gateway key and the key to each recording are handed to the OS keyring, not written into a configuration file next to them.
The client itself
The parts you meet before any session starts.
-
A device ID you can read aloud
A word and three digits, generated once and kept. Easier to say down a phone line than nine digits, and easier to hear correctly.
-
Six languages, two themes
German, English, Spanish, French, Italian and Portuguese, light or dark, and it keeps running from the tray.
-
It updates itself
The client checks our own channel and applies the update only after verifying its signature — exercised on a real installation, not only in a test.
And the parts that are not here.
A remote terminal, a privacy mode that blanks the host’s screen, a virtual display, a knowledge base that fills itself, deployment packages and voice commands all exist somewhere in the client. None of them can work on the build we ship — some need a platform we do not build for, some need a permission no interface can grant. They are on this page nowhere except in this paragraph, and that is deliberate.
What ships, and what does not