Custody & Security

Keep the data yours.

quantOS keeps the record of your research while your raw datasets and proprietary strategy code stay under your control.

Data Boundary

Stays on your machine

Proprietary strategy code (.py), custom simulators, unhashed parameter grids, and raw return matrices stay on your hardware.

Data Boundary

Crosses the network only on sync

Sealed study metadata, canonical SHA-256 digests, trial counts, and cited committee memos—with full return series sent only when you pass --share-series.

Live Controls

Controls in place today.

Every security and custody guarantee on this page reflects what is enforced in the codebase right now.

  • Local math execution

    The open-source AlphaEngine library and its math run offline on your machine. Your proprietary strategy code never crosses the wire.

  • Explicit series boundary

    Login, workflows, reporting, and sealing use the network. Full return series are sent only when you explicitly pass --share-series.

  • Canonical study seals

    Sealed studies are fingerprinted with a full 64-character SHA-256 over canonical JSON so tampering is immediately detectable.

  • Organization-scoped CLI keys

    Firm plans mint ae_live_ keys tied to the organization. Only the key hash is stored, and revoked or downgraded keys stop on the next call.

  • Session & admin verification

    Authenticated sessions are verified against Supabase JWTs, and administrative operations require founder credentials with multi-factor authentication.

  • Research-only retail boundary

    Individual workspaces enforce a strict server-side boundary that strips trade structuring and position-sizing prescriptions.

Formal audit status: Not yet. A formal third-party audit is not yet in place. Security and due-diligence questions go directly to quantos@qosai.app.