Observe
Markets, events, accounts and positions.
Platform · control layers
One integrated workspace for market intelligence, AI-assisted analysis, manual trading and rules-based automation. Analysis stays flexible while capital movement remains deterministic, permission-bound and traceable.
AI assists. You decide.Why a control layer
Fragmented workflows split market data, accounts, models, bots, wallets, funding and cost control across disconnected systems.
AI explains and structures information. Users and configured policies decide. Risk gates verify context and permissions. Deterministic services execute and reconcile the resulting state.
Flexible analysis. Deterministic capital movement.Native client
Portfolio context, market intelligence and assistive AI workflows are being prepared for a native mobile experience.
Store availability will be announced after release validation.
Follow iOS progressFour layers
Markets, events, accounts and positions.
Structured AI analysis with freshness and source context.
User permissions, policies and explicit risk gates.
Deterministic adapters, runners and reconciliation.
Public architecture
The product connects market context, account state and controlled workflows without hiding which layer owns each responsibility.
Dashboard, intelligence, trading, predictions and bot workflows present one connected workspace.
Authentication, permissions, billing, market context and audit rules keep product state bounded.
Strategies create intents; policies and normalized adapters determine what may run.
Orders, positions, provider health and recovery states are verified against their source.
Wallet, funding and isolated Bot Vault workflows remain explicit, test-bounded and separately released.
Responsibility boundaries
AI may analyze, explain and prepare structured workflows. It cannot become an uncontrolled execution key.
Market data, spot, perpetuals, transfers, grid and vault support are evaluated separately.
Missing or stale source data remains visible and can restrict value-moving actions.
A local response is not treated as final account, venue or onchain truth.
Who it serves
Release principle
Read-only before write. Paper before live. Minimum capital before normal limits. Reconciliation before success. Recovery before scale.
Explore the six product surfaces