No. The terminal is one capability inside a control plane for projects, logs, ports, Git, tunnels, databases, and machine operations.

No. Projects and commands run on your registered machine. Explicit Git publishing and AI actions send only the content needed to the provider or repository you select.

No. Register the folders and commands you already use. Dev Server Deck is designed to extend existing workflows rather than replace them.

Yes for Windows, WSL, and Linux; macOS support is coming soon. The Agent supports native project paths and WSL-aware workflows, with runtime and task discovery across the supported ecosystems. In Studio, the coding agent can read, write, run commands, and rename, delete, or create files and folders on a WSL-hosted project the same as a native one - the only piece still missing is live file-watching for changes made outside Studio itself.

Yes. A one-line installer sets up a systemd service on Debian, Ubuntu, and other systemd-based distributions - no desktop environment, display, or GUI credential manager required. The Agent runs as a real non-root user, starts on boot, and restarts automatically if it ever stops; self-update is systemd-aware, so it verifies and rolls back through the same service instead of fighting its restart policy. Provider API keys and other credentials fall back to an encrypted local file when there's no OS keyring to use, which is the normal case on a bare server. Size the box for at least 2 vCPU / 2 GB RAM (4 GB if you use Codex regularly or run more than one project's dev server on it) plus 1-2 GB of swap - a 1 GB "micro" instance is too tight and can get the Agent process itself killed by the kernel's out-of-memory killer mid-turn, losing that session entirely. See the Quick Start tab in this guide for the exact install command.

Remote operations require the Agent machine to be awake and connected. Background work can continue after you close the dashboard, but not after the machine shuts down.

Turn on automatic backups for a machine from Account & Billing → Agent Tokens: your project list (names, paths, start commands, and settings - not the project source code itself) can be backed up to your account, a local folder on that same machine, or both, on a schedule you choose (every 6, 12, or 24 hours, or weekly) and whenever you close the dashboard tab. The local folder defaults to a location outside the Agent's own data directory, and you can point it somewhere else - a synced or cloud-mirrored folder, for example. A "Clear cache" button in the same tab also lets you sweep any stray temporary files the Agent may leave behind.

Studio lets you point your own AI provider's coding agent (Claude, Codex, Gemini, Grok, DeepSeek, Qwen, GLM, Kimi, or Ollama) at a registered project directly from the dashboard, with a multi-tab source browser, live diffs, and a revert option for anything it writes. Rename or delete files from the tree, paste a screenshot straight into the chat for the model to see, attach text, Word, PDF, CSV, or Excel files for it to read, or start from a brand-new empty folder and have the agent scaffold a project from scratch. Opening an image file (PNG, JPEG, GIF, WebP, BMP, ICO, or SVG) shows an actual preview instead of a binary-file error - useful for checking something the agent just generated. The agent can also save what it learns as a reusable "skill" a later turn picks up automatically, kept either as real project files or in a machine-only folder that never touches the repo, your choice - view, download, add your own, or delete any of them from Configure Project's Skills tab, or see every project's at once from the dashboard's Skills Overview. On a shared machine, a team admin can scope access down to specific projects and choose exactly which AI providers a developer may use your credentials for, right from that same tab - Codex included, with its own optional daily token cap and the ability to watch and stop a developer's autonomous run. Every write and command still runs locally on your machine, and provider API keys are stored only in that machine's own OS credential store - never in your account or on our servers.

It keeps going. An agent-mode turn stays running on your machine after you close the Studio panel or navigate away, and reopening it resumes the live view exactly where it left off - the step-by-step progress so far, and any pending command approval still waiting on your answer. The dashboard's Studio button also shows a live indicator whenever a project's agent needs your attention or is actively working, so you can tell at a glance without reopening it. It only stops if you click Stop yourself, or if the Agent machine itself goes offline.

Business is €39.99 a month for one team workspace and includes the team leader's own working seat. Each additional Operator or Developer is €19.99 a month, and read-only Viewers are free. The team leader pays one consolidated bill; members never buy their own subscription to join your team. For example: leader only is €39.99, leader plus 4 working members is €119.95. Business is billed monthly for now and is available by request during the beta - the calculator above shows the planned pricing.

Only the team leader. Members, whatever their role, can't invite anyone, change roles, grant access to machines or projects, manage billing, or see the leader's credentials. A role sets the most a member can do (Viewer is read-only, Operator runs permitted operational actions, Developer can also edit code and use Studio); the leader's grants decide which machines and projects it applies to.

No. Viewers have read-only access to the machines and projects the leader grants them and don't need a paid seat - up to 25 Viewers per team. Only Operators and Developers beyond the leader count as additional working members.

Listed prices exclude VAT. Where VAT applies, it's calculated at checkout from your billing country and shown before you pay, and businesses with a valid EU VAT number can enter it there for reverse-charge treatment.

No. AI provider usage is billed by the provider, not by Dev Server Deck, and we don't promise unlimited tokens. In Studio you use your own provider API key, your ChatGPT account for Codex, or a local model through Ollama or LM Studio. A team leader can let a developer use the leader's credentials for specific providers; those credentials are never shown to the member.

Your plan stays active for 7 days after a failed renewal while the payment is retried, and we email you - and, for a Business team, your members - so there's time to fix it or back up your project configuration. If it isn't resolved by then, paid features are suspended. Nothing is deleted, and access returns as soon as the payment goes through.

Codex (ChatGPT) signs in with your ChatGPT account instead of an API key, picks its own model and reasoning effort, and shows how much of your plan's usage window is left. It plans and executes in one pass, so instead of an approve-the-plan gate you get a live read-only checklist of what it's doing. The Goal panel lets you set an objective and an optional token budget, then choose You drive (send each turn yourself) or Autonomous (the Agent sends the follow-up turns toward the goal on its own). An autonomous run stops at the budget, after its turn limit (20 by default, adjustable), when the goal is complete or blocked, or when you press Stop - and it pauses for your approval before anything outside the project or on the network. Like every agent turn, it keeps running on your machine even if you close Studio.