Private starts
with a clear boundary.
Local inference is one part of a private workspace. Permissions, external tools and the way a host is operated matter too.
Keep the core on your host
The local deployment model places project storage, prepared context, agent workers and model inference on the computer or server you control. A separate hosted inference provider is not required for that path.
Browser access to a remote workspace still travels over a network. Its operator must protect access with HTTPS, account authentication and appropriate host controls.
Make external access deliberate
Web research, external connectors, model downloads and software updates cross the local boundary. An agent should receive only the tools and destinations needed for its task. Sending a document or taking an external action deserves its own review point.
| Activity | Boundary |
|---|---|
| Read project files | Selected source content stays on the workspace host during local processing. |
| Generate with a local model | Prompts and outputs go to the configured local inference endpoint. |
| Research the web | Queries and retrieved pages involve outside services when that tool is enabled. |
| Share or send an output | The selected information leaves the workspace after the authorized action. |
| Back up the workspace | The operator chooses the backup location, encryption and retention. |
Give agents bounded authority
Reading source content should not grant new tool access. Treat instructions found in documents or web pages as untrusted task material. Use separate permissions for reading, writing, moving files and communicating externally.
Local execution does not guarantee correct reasoning. Keep references, review drafts and verify consequential results. Protect credentials outside the documents an agent can inspect.
Operate the environment deliberately
Keep model services off the public internet, maintain host updates and manage membership. Choose log and context retention deliberately, monitor resource use and test restoration from backup.
Encryption at rest, network isolation and backup protection depend on the deployment. They should be configured and verified by its operator; the public website does not certify a private host.
Report a security concern
Email contact@deskarden.com with a short description and affected component. Please do not send credentials or private content in the first message. We will establish how to exchange the details.