Security command center
Evidence before escalation. Point Armalo at your code, name the attacker paths that matter, and get a pinned investigation you can review. Every conclusion stays attached to a saved copy of the code and a clear record of what the scan was allowed to access.
Listed in the Cloud Security Alliance’s Agentic AI startup showcase, mapped to their identity, governance, observability, and guardrails frame. See how permissions, approvals, and the audit trail work together on the governed work page.
Scans record the exact target, preserve the evidence behind each result, and keep possible issues separate from confirmed findings.
The hosting table, residency matrix, and subprocessor list below answer the questions an enterprise buyer brings to /security: where your data lives, how long we keep it, and who can access it. The investigation workspace is further down this page.
Quarterly review cadence, owner: Armalo security team security@armalo.ai
Armalo separates the public edge, account services, customer work, and long-term storage. Customer work runs on dedicated servers first, with per-customer isolated environments as the second option, behind a hardened edge. The certifications listed below are our hosting providers' attestations, not Armalo's. Armalo itself is not SOC 2 certified.
| Hosting | Component | Data type | Region | Compliance posture | Legal-review status |
|---|---|---|---|---|---|
| Dedicated account servers | Sign-in and identity, workspace separation, permissions, billing, audit records, secrets storage, workspace rules, and conversation history | Account details, organization and workspace details, workspace conversation history, permission settings, usage records | US primary | ISO 27001:2022, GDPR Art. 28 DPA | Pending |
| Dedicated compute servers | Main servers where customer work runs | Temporary work state, a working copy of your code, build files, finished work waiting to be saved to your workspace | US primary | ISO 27001:2022, GDPR Art. 28 DPA | Pending |
| Hosted isolated environments | A second way work runs, in an isolated environment for each customer | Temporary files, a downloaded copy of your code, your task instructions, command output, work produced for you | EU and US, selected by workspace settings and availability | SOC 2 Type II, HIPAA posture, GDPR DPA | Reviewed |
| Public edge network | TLS termination, proxying, traffic filtering, DNS | IP address, request metadata, TLS session metadata, cached public responses where configured | Global network | Covered by the provider's contractual and data-processing terms | Reviewed |
| Encrypted long-term storage | Long-term encrypted storage for approved work results, backups, long-term audit exports, image files, and saved copies | Encrypted files and file details | United States (West) | ISO 27001:2022, GDPR Art. 28 DPA | Pending |
Your saved account and workspace data and your temporary work files live in different places and have different deletion paths. Backups are kept in the same region as the data they copy.
| Data class | Where stored | Default retention | Who can access | Deletion path |
|---|---|---|---|---|
| Workspace conversation log | Stored on Armalo's dedicated account servers; encrypted backups in encrypted storage | Routine conversation retention: active for the life of the workspace plus 90 days after the conversation. Workspace deletion or an accepted erasure request removes data in live systems within 30 days; database backups rotate at 7 days | Workspace members, according to their workspace role; Armalo staff with limited access, for support or incident response; the AI receives only the context for its own task | Delete workspace or submit an erasure request; policy requires removal on workspace deletion or accepted erasure; database backup copies expire within the 7-day rotation after live deletion; today we confirm each removal through a direct request; automatic removal at the routine window is not yet in place |
| User-uploaded files | Encrypted storage; temporary working copies inside your private work area | Active for the life of the workspace; 30 days after deletion request; temporary work-area copies expire when the work area is deleted | Workspace members, according to their workspace role; the AI only when you grant the file to its task; Armalo staff with limited access, during support or incident response | Delete the file or workspace, or revoke the AI's access to it; uploaded files are not currently backed up, so deleting the stored file is final |
| Generated code artifacts | Workspace code storage and encrypted storage; temporary build files in the work area | Active while attached to the workspace or its code storage; 30 days after workspace deletion; work-area output lasts only until it is saved to the workspace or the work area is deleted | Workspace members; connected code host; the AI, when it has access to your code; Armalo staff with limited access, during support | Delete from code storage and the workspace artifact store; delete the work area; request workspace erasure - Armalo keeps no independent backup copy of generated artifacts beyond workspace code storage and our encrypted storage, so deletion removes every copy Armalo holds; copies at a connected code host follow that host's retention |
| Integration credentials | An encrypted vault for your connected accounts; the AI receives only short-lived, limited access | Your stored credential stays until you revoke it, replace it, disconnect the integration, or delete the workspace; the AI's short-lived access expires at its set deadline | Owners and Admins you authorize manage the connection; Armalo issues the AI's access; the AI never receives your actual credential | Disconnect the integration, revoke access at the provider, replace the secret, or delete the workspace; any short-lived access still open is revoked or left to expire |
| Workspace audit logs | Workspace audit log on Armalo's dedicated servers, where entries are added and never edited; Enterprise exports may be copied to your own destination | 30 days by default; Enterprise override available | Owner and Admin by default; a security Viewer role where you configure one; Armalo security staff with limited access, for incident response | Automatic daily removal after the 30-day window; the workspace deletion process; you control how long Enterprise exports are kept |
| Request logs | Log of tool use on Armalo's dedicated servers; entries are added and never edited | No automatic expiry yet; these records are append-only | Armalo security staff with limited access, for incident response; authorized admins through the admin audit log | Not yet deletable on request; if a request covers them, we will tell you |
| Billing data | Armalo's account servers, for your usage records and account link; Stripe for payment processing and regulated payment records | Usage ledger retained while the account is active and as needed for accounting, tax, dispute, and legal obligations; payment-card data remains with Stripe | Owner and billing Admin; Armalo's billing team; Stripe for payment processing | Close account and request deletion; Armalo removes data not subject to legal retention; Stripe follows its contractual and legal deletion obligations |
| Telemetry | Armalo's monitoring systems and encrypted storage; our providers' own monitoring where it applies | Our policy target: monitoring data that can identify a workspace is kept up to 30 days unless needed for an active incident; automatic expiry is not yet in place; combined, anonymous metrics may be kept indefinitely | Armalo engineering, reliability, and security staff with limited access; workspace administrators, for views inside their own workspace | Scheduled expiry is not yet automatic; policy requires removal of workspace-linked records on account deletion, and today we confirm removal through a direct request; combined, anonymous metrics cannot be linked back to a workspace |
Residency controls
A provider receives only the data needed for its purpose. This list is current as of 2026-07-30; it may evolve as Armalo adds regions, integrations, models, and delivery providers. Notice is provided through the DPA or customer agreement where required.
| Subprocessor | Purpose | Data shared | Region | DPA status | Legal-review status |
|---|---|---|---|---|---|
| Cloudflare | Edge proxy, TLS termination, traffic filtering, DNS | IP address, request metadata, TLS metadata, public response data, DNS query metadata | Global edge | DPA available; transfer terms governed by Cloudflare agreement | Reviewed |
| Hetzner | Dedicated servers for account services and customer work, private networking, long-term storage, backups | Encrypted customer data, account and workspace details, conversation history, work results, audit records, system monitoring data | United States (Hetzner us-west) | GDPR Art. 28 DPA; ISO 27001:2022 | Pending |
| E2B | Isolated work areas | Part of your task instructions, selected files, a copy of your code, command input and output, temporary work files, short-lived limited access | EU or US, selected by policy | GDPR DPA; SOC 2 Type II; HIPAA posture | Reviewed |
| Stripe | Subscription billing, invoices, payment processing | Customer name, billing contact, plan, invoice data, payment method data handled by Stripe, transaction status | Stripe service regions, including US processing | Stripe DPA available; payment data governed by Stripe terms | Reviewed |
| OpenAI | Model processing when selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | The provider's DPA applies when Armalo runs the model; if you bring your own key, your agreement with the provider also applies | Reviewed |
| Anthropic | Model processing when selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | The provider's DPA applies when Armalo runs the model; if you bring your own key, your agreement with the provider also applies | Reviewed |
| Model processing when Gemini is selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | The provider's DPA applies when Armalo runs the model; if you bring your own key, your agreement with the provider also applies | Reviewed | |
| xAI | Metered model inference when selected | Prompt and context required for the model request; generated response; request metadata | Provider-selected region or customer-contracted region | Provider contractual data terms apply; availability and DPA terms are reviewed per Enterprise schedule | Reviewed |
| Google Workspace | Identity and organization sign-in | Email address, display name, account identifier, sign-in details, organization-domain metadata | Google global service | Google Workspace or Google data terms apply; customer agreement may govern BYO identity | Reviewed |
| GitHub | Code connection, download, and sync of changes and review requests | Code project details, selected source code, change history, installation identity, limited-access code token | GitHub service regions | GitHub DPA available; customer may connect its own organization agreement | Reviewed |
| SendGrid | Transactional email when configured | Recipient email, template variables, delivery metadata, bounce and complaint events | Provider service regions, commonly US/global | DPA available when SendGrid is the configured sender | Reviewed |
| Mailgun | Transactional email when configured | Recipient email, template variables, delivery metadata, bounce and complaint events | Provider-selected US or EU region where configured | DPA available when Mailgun is the configured sender | Reviewed |
Connect a public GitHub code project or an approved private connection.
Security scans do not write code, apply changes to your code, or open change requests.
Each run records the exact code version it examined and the evidence behind its findings, in a record that cannot be changed afterward.
Give the investigation a target and a useful question. The first pass is designed to be safe, legible, and reviewable.
TARGET
Code project + version
Pin what was actually examined.
MODEL
Threat priorities
Focus on consequence, not noise.
RECEIPT
Evidence trail
Trace every finding to proof.
Only this workspace’s authenticated runs appear here.
Workspace history is private.
Scan history belongs to each workspace. You’re signed out, so there’s nothing to show here — sign in to see your workspace’s runs.
Start a new investigation →Redacted. What a finished investigation looks like: every finding traces to evidence.
Sample web application
target ▓▓▓▓▓▓ · ref 9f3ac21 · completed 2026-09-10
Dependency with a known CVE
High2 evidence receipts · lockfile excerpt, advisory reference
Storage bucket allows public reads
Medium1 evidence receipt · saved policy copy
Security headers missing on 4 pages
Low1 evidence receipt · header scan
Sample data: customer identifiers, code project names, and evidence contents are redacted. Real investigations show the same structure with your workspace’s data.
Found something we should know about? Email security@armalo.ai with what you found, where you found it, and how to reproduce it. We read every report and confirm we have received it.
