Droco Trade ProPRIVATE ALPHA -- INVITE ONLY
BUILD 0.3.0OPERATIONAL
Droco Trade Pro
Open app

Control surface

Real money needs explicit consent.

Trading platforms fail closed when they are honest about what they will not do. Our control posture is built around that.

§ 01

Credentials and secrets

Broker keys and API tokens are encrypted before they ever touch the database. They are decrypted on-demand for a single request and never logged.

  • Fernet symmetric encryption with PBKDF2-SHA256 key derivation.
  • Encryption key lives in environment configuration, not in the codebase.
  • Legacy-key migration runs transparently on read; rotation is supported.
  • Public routes never accept, return, or log credentials of any kind.
§ 02

Authorization and access

Authentication and authorization are layered. Read access is one decision; live trading is another.

  • Authentication via httpOnly JWT cookies; optional TOTP MFA.
  • Account lockout window protects against brute-force attempts.
  • RBAC: superuser, platform admin, tenant admin, and regular user.
  • Per-broker live/paper toggle requires an explicit operator action.
§ 03

Order workflow

Every order passes through a synchronous risk evaluation before any broker call. The result is structured, traceable, and recorded.

  • Pre-trade risk gate: buying-power, position size, intraday loss.
  • Broker network I/O runs outside the database transaction, after the order row is committed -- no orphans on failure.
  • Reconciliation against the broker runs continuously, not on demand.
  • Cancellations require a successful broker confirmation before status changes.
§ 04

Audit and disclosure

If something happened on the platform, it is recorded. If we cannot answer 'who, when, why,' the platform is broken.

  • Audit log for every order, approval, credential rotation, and admin action.
  • Agent decisions persist with full source traceability.
  • Public agent-discovery metadata is machine-readable and explicit about boundaries.
  • Security contact published per RFC 9116 at /.well-known/security.txt.

Next step

Review the posture before connecting.

Walk through the security model and the audit surface with us before any broker connection goes live.

Discuss security posture