We build front-, middle- and back-office software for capital market firms across the UAE. Our Dubai-based engineers know DFSA and FSRA reporting, write code that survives audit, and have shipped to live trading floors handling real flow.
Capital markets software has two audiences: the people on the desk who need it fast, and the regulator who needs every action traced. We build for both from sprint one.
Most engagements pair one platform build with two or three add-on services.
Order management, execution, position keeping and risk dashboards for buy-side and sell-side desks.
Real-time exposure, VaR and limit-monitoring with alerting your risk team trusts.
Confirmation, allocation, settlement and break-resolution workflows.
Trade and transaction reporting (DFSA, FSRA, MiFIR-style) with full audit trails and replay tools.
Tick capture, historical replay, and analytics warehouses on commodity cloud.
Trade surveillance, comms monitoring and case-management workflows for compliance teams.
These are ranges from real engagements. We measure them because retainers depend on them.
Default target for the trading platforms we ship, on standard cloud (AWS Tokyo / Bahrain regions).
Breaks surface in real time, not the next morning. Settlement risk drops by orders of magnitude.
From kickoff to a DFSA / FSRA-style report-generation pipeline with full audit replay.
Where reconciliation and breaks workflows are automated. Operations teams shift to exceptions, not data entry.
We pick stacks proven on real trading floors. Low-latency where it matters, low-overhead everywhere else.
Java, Go and C++ for the latency-sensitive paths. Lock-free queues, NUMA-aware threading, and benchmarks in CI.
QuickFIX-style engines, vendor adapters, and a normalised internal protocol so venue changes are not a rewrite.
Postgres for state, ClickHouse for tick history, dbt for risk models the team can read.
Replayable event store. Re-run a regulator's question against last week's data without disrupting today's trading.
AWS Bahrain or Tokyo for low-latency UAE-region work. Terraform, Datadog and PagerDuty for the operational layer.
Pricing shared openly during scoping. Smallest engagement starts around the cost of one senior in-house hire.
A two-week review of your trading platform, data flows and reporting before audit or scale-up.
Firms preparing for DFSA / FSRA review or a major platform upgrade
A senior pod shipping front-, middle- and back-office features alongside your team each sprint.
Brokers, custodians and asset managers shipping new venues, products or reporting flows
We own your reporting pipelines, reconciliation tooling, and ops dashboards on a monthly retainer.
Live firms past go-live who want one steady partner for ops engineering
Capital markets platforms live or die by a few decisions made in the first quarter. We focus there and leave clever for the analytics layer.
Append-only event store as the source of truth. We can re-derive any report by replaying events through a new processor.
Order, fill and settlement messages can arrive twice. Our pipelines treat re-delivery as normal, not an outage.
Books, ledgers and venue state reconcile continuously. Breaks surface within seconds, not on the morning report.
-- Row-level tenant isolation.
-- One schema, many tenants, zero "where did this data leak from" tickets.
ALTER TABLE invoices ENABLE ROW LEVEL SECURITY;
CREATE POLICY tenant_isolation ON invoices
USING (tenant_id = current_setting('app.tenant_id')::uuid);
-- Application sets the tenant for every connection.
-- If we forget, the query returns zero rows, not someone else's.
SET LOCAL app.tenant_id = '8f3a-...-c1';
SELECT id, amount_cents, status
FROM invoices
WHERE status = 'pending'
ORDER BY created_at DESC
LIMIT 25;
An example of tenant isolation we apply to per-desk and per-client books. The same principle underpins our segregated reporting pipelines.
Walk the floor (literally or remotely), read the books and ledgers, talk to traders, risk, ops and compliance. We listen for the breaks that always happen on Mondays.
Milestones, risks, and what we would do first. Including the work we would recommend you do not do this quarter.
Our senior pod is in your repos shipping production features. Your team owns the merges, we own the cadence.
Measured against the outcomes we agreed on. The people who start with you are the same people in month six.
SKIMBOX rebuilt our reporting pipeline and risk dashboard in one quarter. Our DFSA submissions stopped being a fire drill, and the desk now sees risk numbers a full minute faster than before.
Manual prep replaced by a replayable pipeline.
Desk now sees PnL and exposure essentially live.
Across four quarters since we rebuilt the reporting layer.
Yes. Our team has shipped reporting pipelines for both DIFC and ADGM-licensed firms. We work alongside your compliance counsel, build the audit trails inspectors actually look for, and rehearse the reg-change motions before they happen.
Tell us what is slipping on the desk, what is breaking in ops, and what your reg team is bracing for. Written plan in two weeks, or an honest 'we are not the right team'.