Skip to content

Trust

Trust Center

Last updated: 2026-06-01

This page is the canonical reference for security questionnaires about auxon.dev and the three products we operate: Paragon, Trueform, and NetMender. It covers what data we handle, where it goes, what controls are in place, the live operational status of our surfaces, and how to reach us with a security concern.

All systems operationalSee live status

Security packet

Hand this to your security team.

A PDF of the posture, sub-processors, controls, and disclosure contact, sized to drop into a vendor review packet. Generated fresh from this page.

Data handling

The auxon.dev marketing site collects only what you type into a form: name, work email, company, and the free-text description. It does not set tracking cookies and does not run cross-site profiling.

Paragonreads read-only data from the systems you connect (Okta, Google Workspace, GitHub, MDM providers) to run its governance modules. Findings, plans, and policy drafts are stored per tenant in our database. Assessment inputs and outputs reach the Anthropic API for the RCA and policy-drafting steps; no data is used to train models. Each tenant's data is isolated at the row level and never shared across org boundaries.

Trueform receives the plain-English descriptions you type into the generator. Those descriptions, along with the provider context you supply, are sent to the Anthropic API to produce Terraform. Generated files are stored per org. Prompts are scrubbed of 19 categories of secrets and PII before they reach the model.

NetMender receives telemetry from Meraki, UniFi, and an on-LAN host probe. Fault events and root-cause records are stored per org. The remediation agent calls the vendor control-plane API server-side; vendor credentials never leave the vault and are never returned to the browser. Audit records are append-only and cannot be modified.

Infrastructure

Vercel hosts the auxon.dev marketing site and all three product frontends, with cookieless Vercel Analytics for aggregate traffic data.

Cloudflare handles DNS for auxon.dev and routes inbound mail (hello@auxon.dev forwards to our team inbox).

Resend sends outbound email when you submit a form and when we reply.

Anthropicprovides the Claude model that powers Trueform's generation step and Paragon's RCA and policy-drafting layer.

Security controls

  • HTTPS only with HSTS preload. All traffic is TLS-only. The domain is submitted to the HSTS preload list so browsers never attempt a plain HTTP connection.
  • Strict CSP and security headers. All pages ship with a Content Security Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy headers.
  • Multi-tenant isolation (Paragon, Trueform, NetMender). Data across Paragon, Trueform, and NetMender is isolated at the row level per org. No cross-tenant reads are possible through the application layer.
  • Per-run cost caps (Paragon). Each Paragon module run carries a hard cost ceiling. An agent loop cannot run indefinitely; node-level costs are tracked and capped per assessment.
  • Append-only audit trail (Paragon, NetMender). Every assessment, plan, approval, and execution is logged with timestamps. The trail cannot be edited or deleted, even by an admin.
  • Kill switch (NetMender). A global kill switch hard-blocks all remediation regardless of UI state. Detection keeps running; nothing executes against a vendor API while the switch is on.
  • Vault-backed credential storage (NetMender, Paragon). Vendor control-plane credentials and API tokens are stored in an encrypted vault, isolated per org, and decrypted only server-side at execution time. They are never returned to the browser.
  • Confidence gate (NetMender). A root-cause analysis below the confidence threshold is never pre-formed into an approvable fix. Low-confidence faults go to triage with no action attached.

Compliance posture

SOC 2 (in progress). We are aligning controls to the Trust Services Criteria. Paragon's own SOC 2 Gap Analysis module is actively used on our own stack, so the program we are building is the same one the product generates for customers.

HIPAA. Paragon's HIPAA Readiness module is designed to help customers scope, gap-analyze, and document their own HIPAA programs. For engagements that require us to operate as a business associate, we sign a BAA on a case-by-case basis. Contact us to discuss the specifics of your environment.

Sub-processors

The following third parties process data on our behalf as part of operating auxon.dev and the three products. The list is reviewed each release; when a vendor is added or removed, the list below and the review date at the bottom of this section both roll forward.

  • Vercel (US) - Hosting and cookieless analytics for the marketing site and all product frontends.
  • Cloudflare (Global) - DNS for auxon.dev and inbound email routing.
  • Resend (US) - Outbound transactional email.
  • Anthropic (US) - LLM API behind Trueform's generation step and Paragon's RCA and policy-drafting layer. Data is not used to train models.

List last reviewed: 2026-06-01.

Responsible disclosure

If you find a security vulnerability in auxon.dev or any of our products, email hello@auxon.dev with a description and steps to reproduce. (A dedicated security@ address is being set up; for now hello@ reaches the same inbox.)

We follow a 90-day coordinated disclosure window: we will acknowledge within two business days, work toward a fix, and ask that you hold public disclosure until the patch is in place or 90 days have passed, whichever comes first. We do not run a paid bounty program at this time.

For general security questions or the vendor questionnaire form, use the same address or see the contact page.