Last updated: November 2, 2026
Dev Server Deck lets you control a machine from a browser or a phone. That is powerful, so this page says exactly how a request travels, what we can see on the way, and what your machine refuses on its own. If something here and the product ever disagree, tell us at info@devserverdeck.com.
The Local Agent on your machine opens an outgoing connection to our relay. Your browser or phone talks to our servers over TLS, and the relay passes each request to the Agent over that connection. Nothing connects in to your machine.
Studio only: the AI chat, the file editor and approvals. Your device and your Agent agree on a key (ECDH, P-256) and encrypt with AES-GCM; the Agent signs the handshake with its own identity key. The relay forwards ciphertext and can neither read nor change it. Each browser and phone keeps its own copy of the machine's identity key after first use, because the copy in our database is written by the relay. The first connection to a machine is trusted on first use, so compare the short fingerprint shown in Account with the one the Agent prints on your PC (--studio-fingerprint).
Everything else: the project list and status, starting and stopping, logs, scripts and the terminal, .env files, Git, file browsing and downloads, backups, and restart or shutdown. These pass through our relay as readable data over TLS, because the relay has to read them to enforce team roles. Whoever controls the relay could read that traffic and send your Agent the same requests you can send. This is why the machine decides.
Four kinds of remote request are refused by the Agent itself until someone at that PC turns them on. All four are off by default.
.env, read or restore backups, download a project's structure, set AI credentials, change where Git sends your source, and the cloud copy of your project list.Starting and stopping the projects you already set up, status, logs and tunnels need no switch. Backups written to a folder on the PC itself need none either. A switch is changed in the Agent's tray menu, or on a headless Agent with --allow=commands:on (and :off). The state is a file signed with a key kept in your operating system's credential store: an edited file, or one copied from another PC, reads as everything off. There is no message that the web, the app or our servers can send to change a switch.
Time-limited switches. At the PC you can turn a switch on for a set time, for example --allow=files:on --for=30m(1 minute to 7 days). The end time is stored inside the same signed file and the Agent checks it on every request, so a switch that ran out while the Agent was stopped is already off when it starts again, and an end time cannot be edited or removed without breaking the signature. If the PC's clock is moved back past the moment the switch was set, the timed switch counts as over.
A record of what the switches did (Agent 2.15.62 and later). The Agent keeps a log on the PC of every switch change (and whether it was made in the tray menu or on the command line), every remote request a switch allowed (which route, which folder for file requests, and the role of the person who asked), every request it refused, and every update it verified or turned away. Account shows the latest entries. It never stores file contents, .env values or request bodies, is readable only by your user on the PC, and rotates at 2 MB. The web and the app cannot change or delete it. The dashboard and the app also show a banner when a PC has refused requests in the last day.
Backups.Without a path, a backup goes to a default folder on the PC and needs no switch. A custom backup path sent from the web is checked on its real location (links are followed): it must be a full local path, not the Agent's data folder, not inside any project folder (project folders are often shared or synced) and not on a network file system such as NFS or SMB. From Agent 2.15.63 it is also refused inside anything that looks like a project, such as a folder with .git, package.json or index.html, so a project you never added to Dev Server Deck is covered too. Even then it is accepted only if the files switch is on or it is the one folder named at the PC with --backup-folder=<path>.
Main projects folder. You can name one folder on the PC (tray menu, or --projects-folder=<path>). Add Project can then browse and create folders inside that folder, and only there, even while files is off. Downloads still need files. Links inside the folder that point elsewhere do not open the outside.
Every route the Agent has is listed with the switch it needs; a route that is not listed needs commands, and a test fails if a route is added without being listed. Account shows each machine's switches and what was refused.
Studio content would stay unreadable and every switch that is off would stay off. An attacker could still do what needs no switch (start and stop your configured projects, read status and logs, open tunnels) and anything for which you turned a switch on. Leave switches off unless you use the feature. When a switch is on, trusting the relay and your account is part of that choice, and code running as you on that PC could also reach the switch file and its key.
From Agent 2.15.56 the small server the Agent runs on 127.0.0.1 refuses any request that does not carry a secret made when the Agent starts, and any request whose Host is not the loopback name, so a web page open on the same PC cannot reach it. Earlier versions did not do this; please update.
The Agent updates itself from a fixed address on GitHub when you confirm in the dashboard. From Agent 2.15.60 an update is verified before anything is installed. Each release carries a signed manifest (update-manifest.json and update-manifest.json.sig): the version, and the SHA-256 and size of every download, signed with an Ed25519 key that is kept offline and never shipped. The Agent has the matching public key built in and installs an update only if (1) the signature is valid, (2) the release is newer than the version running (an older, genuinely signed release cannot be replayed to downgrade it), and (3) the downloaded file matches the signed size and checksum. If any check fails, nothing is extracted, copied or run, and the dashboard shows why. Someone who took over the download location could withhold an update but could not make an Agent install their own file. There is no setting, environment variable or flag that changes where updates come from or turns the check off (from 2.15.61; 2.15.60 still had a developer override that logged a warning). Windows builds are also code-signed. The update helper still keeps the previous version and rolls back if the new one does not stay up.
Which updates are verified. Agents older than 2.15.60 do not check updates. The update to 2.15.60 is installed by such an Agent, so it arrives unverified, and so does any update installed by 2.15.59 or older. From 2.15.60 on, every update an Agent installs is verified. If you want to be certain of the step to 2.15.60, download it yourself and check it (below), or install it from the release page.
Checking a download by hand. Every release since 2.15.58 carries a SHA256SUMS.txt next to the zips (sha256sum -c SHA256SUMS.txt on Linux, shasum -a 256 -c SHA256SUMS.txt on macOS,Get-FileHashon Windows). A checksum from the same place as the file proves it arrived intact; the signed manifest is what proves who made it. Account shows whether a machine's Agent verifies its updates.
Key custody and recovery. The daily signing key is encrypted with a passphrase and backed up in encrypted form. From Agent 2.15.62 every Agent also trusts a second, recovery key whose private half is kept offline on a device that is never connected to the publishing machine. A release signed with the recovery key can tell Agents to stop trusting the daily key; Agents remember that, refuse anything signed with it from then on, and check the latest release for such a notice shortly after starting and twice a day, without installing anything. The daily key cannot revoke anything and the recovery key cannot be revoked. If a key were ever exposed we would say so here and in the release notes. Limits, plainly: an Agent that is offline, or older than 2.15.62, does not learn of a revocation until it updates, and between a key being stolen and an Agent seeing the revocation a thief who also controlled the release address could still serve that Agent a signed update. The procedure is written down in the repository (docs/key-recovery-runbook.md).
Update to the latest Agent to get all of it. This is the complete list, newest first.
filesswitch on or when it is the one folder named at the PC. The data folder's files become owner-only and leave shared groups (Linux, macOS). The dashboard shows a banner when this PC refused remote requests. Releases publish SHA-256 checksums..env from the folder it was started in. Daily copies of the project list.files, commands, secrets, machine), off by default and signed..env and Git traffic still cross our relay in readable form. Extending end-to-end encryption to them is a separate design that is not built yet.Write to info@devserverdeck.com. We read every report and say plainly what we find; the Agent's release notes list security fixes.