Security and trust
Verify the boundary before you trust the agent
SeaShell documents what the product controls, what your team controls, and what has not been independently attested. Every claim on this page is scoped to a named operating mode.
Evidence reviewed 2026-08-03
Verified product controls
Claims tied to implementation evidence
Opt-in offline egress boundary
When SeaShell runs with seashell --offline or ATLAS_OFFLINE=1, it blocks network traffic except the configured model endpoint and local services.
The boundary is covered by egress, session-wire, and choke-point tests in the SeaShell product repository.
Review documentationExplicit local model discovery
seashell models --local probes Ollama on port 11434 and LM Studio on port 1234, then registers discovered chat models.
Local provider construction and discovery behavior have automated repository tests.
Review documentationPermission-gated tool actions
SeaShell supports allow, ask, and deny decisions for tool actions. Teams remain responsible for selecting rules that match each repository and workflow.
Permission configuration and review behavior are documented in the product documentation.
Review documentationAllowlisted telemetry schema
SeaShell telemetry events use a fixed field allowlist that excludes prompts, code, file paths, file names, repository names, and error messages.
Producer-side schema tests reject disallowed fields before an event can be emitted.
Review documentationDeployment boundaries
The selected route determines where model data goes
Local and offline
Local model endpoint and local services
Use a local runtime with SeaShell offline mode when the workflow must prevent other outbound SeaShell network traffic.
Private or enterprise endpoint
Customer-approved network endpoint
Point SeaShell at an approved OpenAI-compatible model service and apply the organization's network, identity, logging, and retention controls.
Hosted provider
Selected third-party provider
Provider calls cross that provider's boundary. Review the provider contract, retention behavior, region, and data policy before using sensitive repositories.
Assurance posture
Current status, without badge inflation
SOC 2
Not auditedIndependent SOC 2 work is deferred while the company establishes budget and operational readiness.
HIPAA
No product certification claimHHS does not issue a HIPAA compliance certificate for software products. Deployment, access to PHI, contracts, and customer safeguards determine the applicable obligations.
PHI handling
Architecture decision pendingSeaShell has not published a blanket PHI-handling commitment. Buyers should confirm the exact data flow and whether Syntora-operated services receive, maintain, or transmit PHI.
Vendor integrations
Evidence-labelledIntegration support and vendor recognition are tracked separately. Test-backed does not mean certified, endorsed, or listed by a vendor.
Reviewer packet
Give procurement evidence, not adjectives
- Operating-mode and data-route documentation
- Integration evidence and vendor-recognition status
- Permission and telemetry documentation
- Customer-specific PHI and contract review when applicable
Security FAQ
Direct answers for reviewers
Is SeaShell SOC 2 audited?
No. SeaShell does not currently claim a SOC 2 report. The security program is documenting controls and evidence first, with independent assurance deferred until budget and readiness support it.
Has a regulator issued SeaShell a HIPAA product certification?
No such claim is made. HHS does not issue a HIPAA compliance certificate for products. A customer must evaluate its deployment, data flow, safeguards, contracts, and legal role.
Does a local model make the whole workflow offline?
Not by itself. Run SeaShell in offline mode and verify every configured model endpoint, MCP server, plugin, provider key, and local service against the intended boundary.
How do I report a security issue?
Email contact@seashell.sh with a clear description, affected version, reproduction steps, and impact. Do not include live credentials, PHI, or customer secrets.