Skip to content

SOC 2 readiness (not a certification) ​

Autlantic Billing is not SOC 2 certified. This page is a procurement readiness outline so merchants know what exists today and what still requires process work with a CPA firm.

Canonical company page (preferred for RFPs): autlantic.com/compliance

Contact: [email protected].

Already in product ​

Control areaWhat exists
AccessMerchant portal accounts, email verification, API keys with rotate, Test vs Live separation
Enterprise SSOWorkOS-backed SAML / OIDC for the Billing merchant portal, on request (invite-only seats). Optional Google OIDC remains available when configured
AuditMerchant audit log in the portal for key and webhook admin actions
Change managementGitHub PRs, CI, Railway deploys from production only
Data storeManaged Billing database on Railway for billing API, portal, and worker
MonitoringSentry error monitoring on billing-api, portal, and worker
AvailabilityGET /healthz on Billing API; public status page
Encryption in transitHTTPS on hosted API, portal, docs, and status
SecretsEnv-based secrets on Railway; webhook signing secrets per portal endpoint
Vulnerability intakeSECURITY.md / [email protected]
Legal draftsDPA outline and Security FAQ on the company site
SubprocessorsListed on the Trust center and DPA

Still required for a Type I / Type II report ​

These are not claimed as complete:

  1. Written information security policies (access, change, incident, vendor) signed by management.
  2. Formal access reviews and offboarding checklist with evidence.
  3. Incident response runbooks with tabletop evidence.
  4. Vendor / subprocessor due diligence records.
  5. Continuous monitoring evidence package for the audit period (Type II).
  6. Engagement of an independent CPA firm and scoped system description.

How we talk about this ​

  • Preferred: “SOC 2 readiness in progress” or “not SOC 2 certified; see compliance.”
  • Avoid: “SOC 2 certified,” “SOC 2 compliant,” or implying a report exists when it does not.