Satura Remote

Satura Remote is a phone web app for tuning and checking on agents away from the desk. It connects to Satura Space on your computer. It's only a web app: it runs in the phone's browser or as a Home Screen app (PWA).

#What it shows

• Your agents. Check on them and steer them from anywhere.
• The game stream. Watch and play what they built, live.
• Files and Git. Browse files and review changes from the phone.
• Notifications. Know when an agent finishes or needs you.
• A monthly traffic allowance. The phone app shows what you have used and what is left.

The phone shows one panel at a time. On the workspace you have open, it shows the tab your computer focuses, and an agent can bring a tab to the phone, such as a Tuner it wants you to look at. Ask Drift works from the phone too: Drift acts in the Tuner the phone shows, but its bubbles show only on the computer, so the agent puts the answer in its reply.

#Pairing

Satura Remote stays off until you turn it on to pair a phone. From then on, the desktop app connects to the hosted relay. Satura Remote is the only part of Satura Space that needs an account.

1. On your computer, open Settings → Mobile. It shows a QR code and a one-time code that works once, for 10 minutes.
2. Open Satura Remote on your phone, sign in, and scan the QR code or type the code.
3. Allow the phone on your computer when Satura asks.

The phone app and the desktop each send a protocol number. When they don't fit, the phone shows an update screen instead of the app.

#Security and encryption

Everything between your phone and your computer is end-to-end encrypted and authenticated. Our relay only passes sealed frames along: it can't read, change or replay your terminals, code, files, prompts or the game stream, so we can't see or analyze your work.

• Keys stay on your devices. The phone makes its key in the browser as non-extractable, and your computer keeps its own. Neither reaches our servers, and the relay holds no keys.
• Pairing needs you at the computer. The phone proves it has the code shown on your computer without sending it, and the computer pairs it only after you allow it. A relay that swaps keys in the middle fails that proof.
• Every connection is checked. Each one starts with a signed key exchange and fresh keys. A replayed, reordered or changed frame fails and the session closes.
• The game stream is peer-to-peer when possible. Video and input go over WebRTC with DTLS, and the fingerprints are checked inside the encrypted channel, so the relay can't slip in its own.

What the relay still sees. Routing metadata: your account email, IP addresses, your computer's name, connection times and message sizes. Not the content.

Removing phones. Your paired phones are listed in Settings → Mobile. Remove one and it disconnects at once and can't connect again with its old key. Remove all phones does that for every phone.

Pairing again. A removed phone pairs again with a new code. So does a phone whose browser cleared its storage, and a phone paired before end-to-end encryption, which shows as needing to pair again. On iOS, a Safari tab and the Home Screen app are separate phones and each pairs on its own.

The relay serves the phone app's code, so that code is the one thing you still trust us for. The details are in Security.

#Pricing

The desktop app is free and open source. Satura Remote is the paid part: a subscription managed at app.saturaspace.com. See pricing.

#Source and license

The code is in packages/companion-app. The relay is under the Elastic License 2.0: you can use, change and run it for yourself, but you can't offer it to others as a hosted or managed service. The phone app the relay serves is built from apps/orchestrator, which stays Apache-2.0. See License.