Common questions from institutional teams.

Architecture, security, rollout, and governance—answered in plain language. Expand a question for the full answer.

Frequently asked

Click a question to expand. Links point to deeper public pages when you need detail.

▸Do you start with microservices?

No. We start with a modular monolith and extract only when scale or isolation is justified—see Architecture and Workflows.

▸How do you handle compliance overrides?

Overrides are first-class workflows with maker-checker, rationale, and audit logs—see Compliance and Audit.

▸Can we integrate our OMS/FIX later?

Yes. Integrations are adapters behind ports; the core domain stays stable—see Integrations and API design.

▸How is AI controlled?

Permission-aware context, citations, and no silent order-affecting actions—see AI Copilot and Security.

▸What about reporting?

Exports run asynchronously with trace IDs and artifacts in object storage—see Reporting and Observability.

▸What’s the fastest MVP?

Portfolio, compliance, manual orders, execution tracking, post-trade states, and audit trails—see Roadmap and Modules.

Cross-links across the public site for architecture, trust, specialty modules, and rollout.

Modular monolith approach with extraction-ready boundaries.

Commercial, technical, and governance inquiry channels.

Top-level public documentation index.

Authorization, approval controls, and trust posture.

Structured walkthrough of workflows and controls.

Phased capability progression plan.