{"schemaVersion":"1.0","product":"Atlas","publisher":"Syntora","legalEntity":"Automize LLC","canonical":"https://runatlas.sh/security","reviewedAt":"2026-08-03","controls":[{"id":"offline-egress","title":"Opt-in offline egress boundary","status":"available","summary":"When Atlas runs with atlas --offline or ATLAS_OFFLINE=1, it blocks network traffic except the configured model endpoint and local services.","evidence":"The boundary is covered by egress, session-wire, and choke-point tests in the Atlas product repository.","documentation":"/docs#deployment-boundaries"},{"id":"local-models","title":"Explicit local model discovery","status":"available","summary":"atlas models --local probes Ollama on port 11434 and LM Studio on port 1234, then registers discovered chat models.","evidence":"Local provider construction and discovery behavior have automated repository tests.","documentation":"/integrations"},{"id":"tool-permissions","title":"Permission-gated tool actions","status":"customer-controlled","summary":"Atlas supports allow, ask, and deny decisions for tool actions. Teams remain responsible for selecting rules that match each repository and workflow.","evidence":"Permission configuration and review behavior are documented in the product documentation.","documentation":"/docs#permissions"},{"id":"telemetry-schema","title":"Allowlisted telemetry schema","status":"available","summary":"Atlas telemetry events use a fixed field allowlist that excludes prompts, code, file paths, file names, repository names, and error messages.","evidence":"Producer-side schema tests reject disallowed fields before an event can be emitted.","documentation":"/docs#telemetry"}],"deploymentBoundaries":[{"title":"Local and offline","route":"Local model endpoint and local services","description":"Use a local runtime with Atlas offline mode when the workflow must prevent other outbound Atlas network traffic."},{"title":"Private or enterprise endpoint","route":"Customer-approved network endpoint","description":"Point Atlas at an approved OpenAI-compatible model service and apply the organization's network, identity, logging, and retention controls."},{"title":"Hosted provider","route":"Selected third-party provider","description":"Provider calls cross that provider's boundary. Review the provider contract, retention behavior, region, and data policy before using sensitive repositories."}],"assurance":[{"label":"SOC 2","status":"Not audited","detail":"Independent SOC 2 work is deferred while the company establishes budget and operational readiness."},{"label":"HIPAA","status":"No product certification claim","detail":"HHS does not issue a HIPAA compliance certificate for software products. Deployment, access to PHI, contracts, and customer safeguards determine the applicable obligations."},{"label":"PHI handling","status":"Architecture decision pending","detail":"Atlas 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."},{"label":"Vendor integrations","status":"Evidence-labelled","detail":"Integration support and vendor recognition are tracked separately. Test-backed does not mean certified, endorsed, or listed by a vendor."}],"disclosure":{"contact":"mailto:contact@runatlas.sh","policy":"https://runatlas.sh/security","securityTxt":"https://runatlas.sh/.well-known/security.txt"}}