Technology · Architecture
One ecosystem, drawn honestly.
A client arrives at a portal. The portal writes to a client record the CRM owns. The terminal authenticates against that record and sends orders through the risk engine to market connectivity. The intelligence layer observes all of it.
- What it is
- The system topology: client surfaces, client and relationship management, trading and execution infrastructure, and market and liquidity connectivity.
- Who it is for
- Technical evaluators who need to know where the boundaries and the failure modes are.
- Why it matters
- Architecture determines what is possible later. Shared state is why a limit change applies instantly across every surface.
- How it connects
- EMIL spans the lower tiers as an observing layer. It has no privileged path to market: its orders pass the same risk checks.
- What happens next
- Request the architecture walkthrough and the data-model overview.
Topology
The flow, end to end.
Hover a tier to see what it owns. The intelligence layer spans the lower three — it observes them, it does not sit above them.
EMIL observes the CRM, execution and connectivity tiers. Anything it proposes passes the same risk checks as a human order.
The stack
Four layers, and what each one owns.
Named rather than gestured at, because an evaluator’s next question is always which part was bought and which part was built.
Presentation
- A browser application, so there is nothing for a trader to install or update
- Charts drawn from the platform’s own indicator engine
Core engine
- Order management, position keeping, matching and price aggregation as separate services
- Built rather than licensed, which is why the order types are not a vendor’s list
Data
- Relational store with row-level security, so isolation is enforced where the data lives
- A time-series store for ticks and candles, a cache for hot state, and a search index for the record
Infrastructure
- Container orchestration across more than one region
- A global edge in front of it, and the same deployment for every tenant
Tier by tier
Client surfaces
Terminal, client portal and partner portal — separate surfaces, one identity model.
Relationship layer
CRM and back office own the client record and the permission model.
Execution infrastructure
Order management, the risk engine in the order path, and position keeping.
Market connectivity
Market data handlers and liquidity sessions, isolated per provider.
Intelligence layer
EMIL observes market, book and account state across the lower tiers.
Failure isolation
A degraded provider session does not take down the platform surface.
Ask the awkward questions
What happens when a feed goes stale, a provider rejects, or a client disconnects mid-order? Those are the useful questions.