A named human owner, not a black box.
Customer approval policies, role-based access, tenant boundaries, and export and exit rights. Agents do the work; people approve what leaves the building.
Solace Delegated Access uses OAuth 2.0-compatible least-privilege scopes and local session controls. Ask what is covered for your engagement.
How requests and credentials move across Solace AGI, Buzz, and Browser.
Supported cloud-proxied actions route through solaceagi.com so LLM API credentials, tenant-scoped storage, and integrated services stay on the server instead of exposing third-party provider keys to desktop apps.
For supported integrations, requests pass through solaceagi.com so logging, budgets, and tenant checks apply to those agreed workflows. Meanwhile, Solace Buzz keeps cryptographic seat keys on each member's workstation across dedicated *.communities.solacebuzz.com relays, and Solace Browser keeps your Chromium profile and cookies on your machine (running in one shared local profile today; per-site action checks are in development). This cloud proxy covers the workflows you connect to Solace — it does not intercept unrelated traffic on your computer.
What's in place.
Cloud proxy egress
Supported model calls and cloud state route through solaceagi.com. Solace provisions and manages LLM provider credentials so you never paste third-party API keys.
Per-tenant isolation
Each customer has its own tenant scope, and access checks enforce it on customer data such as CRM records, messages, files and e-sign. The remaining routes are being brought under the same check; cross-tenant access is treated as a defect, never a setting.
Managed LLM credentials
solaceagi.com holds core LLM API credentials on the server side. You do not need to supply or manage external model keys for standard workflows.
Evidence logging
Evidence and access logging exist for specific approved actions and supported workflows, recording the approved action so the customer can review what ran.
Delegated access
Supported integrations use least-privilege scopes and local session controls; applicable access and review terms are set for the connected service.
WorldData separation
Public and licensed market data maintains documented separation and sources from customer records, and your engagement scope identifies how data is used.
SOC 2 posture
We build to SOC 2 control practices. We do not yet claim a completed SOC 2 audit; when one is complete, it will say so here with a date.
HIPAA / BAA
For qualifying healthcare engagements, a Business Associate Agreement and hardened deployment are available as a contracted option — not a default claim.
Self-host / on-premises
Companies that must keep AI inside their own network can run Solace on a Private AI Box, delivered with DTS Network (DTS), under a separate license. Our standard terms make no air-gap promise; an isolated deployment is agreed separately, in writing. See Sovereign AI →
If it isn't real, it isn't here.
Every security statement on this site must be one of four things: a control implemented today, a certification actually completed, a design goal clearly labeled as such, or a customer-specific contractual option. Anything that doesn't fit one of those is removed.
Our logging and automated checks exist for specific approved actions — they cover the workflows you run through Solace, not unrelated apps on your computer.