Build · Run · Monitor  /  Totality 000%

Scroll

Built for live markets

Trading technology,built and run.

We design, build and operate trading platforms, execution systems and fund technology for brokers, prop firms and emerging managers, from first commit to the 3am alert.

01The labs

Eight disciplines. One lead.

A trading system crosses disciplines, so each lab is a specialist practice with its own methods, standards and a live tool you can try. They share one delivery lead, one engineering standard and one contract, so nothing falls between suppliers.

  1. 01

    Fintech Lab

    Software that moves money in live markets.

    • Trading platforms
    • Quant analytics and algorithmic trading
    • Fund technology
    Enter the Fintech LabLive tool: Options payoff explorer
  2. 02

    Software Lab

    Platforms your operations can stand on for a decade.

    • Custom platforms
    • Web and mobile apps
    • APIs and integration layers
    Enter the Software LabLive tool: Scope-to-estimate configurator
  3. 03

    AI and Automation Lab

    Agents that do real work, inside guardrails you set.

    • AI agents and copilots
    • LLM integrations
    • Workflow automation and integrations
    Enter the AI and Automation LabLive tool: Agent demo and automation roi calculator
  4. 04

    Search Lab

    Found by Google. Cited by the answer engines.

    • SEO and AEO
    • Content and analytics
    • We run search for the sites we build
    Enter the Search LabLive tool: SEO and AEO page checker
  5. 05

    Design Lab

    Interfaces that make sense the first time.

    • UX and UI, product design
    • Design systems
    • Brand
    Enter the Design LabLive tool: Contrast and token playground
  6. 06

    Data Lab

    One version of the numbers, ready to be questioned.

    • Data engineering and pipelines
    • BI dashboards
    • Talk-to-your-data agents
    Enter the Data LabLive tool: CSV to dashboard
  7. 07

    Cloud Lab

    Infrastructure designed to stay up at 3am on a holiday weekend.

    • DevOps and cloud infrastructure
    • Observability
    • 24/7 monitoring
    Enter the Cloud LabLive tool: Cloud cost estimator
  8. 08

    Security Lab

    Secure by design, with the evidence regulators ask for.

    • Secure-by-design engineering and code review
    • DORA and FCA resilience evidence
    • Partner-attested pen testing
    Enter the Security LabLive tool: Security headers grader

02Case studies

What we have built.

  1. Live in production with paying subscribers

    Web trading terminal

    Read the case study
  2. Tested on the broker's demo server. Production access is pending

    Server-side order execution for a broker

    Read the case study
  3. Built and tested in staging. Not live, pending legal review

    Multi-level referral and commission system

    Read the case study

03Trading standards

Press the kill switch.

A demo: every automated trading system we build can be stopped like this.

  1. Backtest

    Same inputs, same result, with costs modelled.

  2. Pricing tests

    Thousands of generated cases on the maths.

  3. Audit trail

    Every order recorded with what triggered it.

  4. Kill switch

    Halted instantly, by a person or a breached limit.

Orders flowing to market

04Standards

What every engagement includes.

Seven commitments written into every contract, whichever lab leads the work. They are what keeps software easy to change long after launch.

  1. 01

    Fixed-price paid discovery

    A short, fixed-price sprint that ends in scope, architecture and a costed plan. You own the output, whoever builds it.

  2. 02

    A named accountable lead

    One senior person answers for delivery across every lab involved, from kickoff to run.

  3. 03

    You own the code and documentation

    Repositories, infrastructure accounts, runbooks and decisions sit in your name from the first day.

  4. 04

    Automated test gates

    Unit, integration and end-to-end tests run on every change. Nothing merges or ships on a red build.

  5. 05

    Observability from day one

    Logs, metrics, traces and alerts are part of the first release, not a phase after launch.

  6. 06

    Written architecture decisions

    Every significant choice is recorded with its context and the alternatives considered, so future teams know why.

  7. 07

    An SLA-backed run retainer

    Hosting, monitoring, patching and support under a service level agreement, delivered by the team that built it.

05Live tools

Try the labs.

Every lab hosts a working tool built to the standard we ship to clients. They run in your browser, and nothing you enter is sent to us unless you choose to email it.

06What we build

The systems behind the work.

Named by what they do. Clients are never named, and every lab page goes deeper into its own archetypes.

01Fintech Lab

  • Trading terminals and execution bridges
  • Order and execution management
  • Backtesting and research environments
  • Algorithmic trading systems

02Software Lab

  • Operations platforms
  • Customer portals and web apps
  • Mobile apps
  • APIs and integration layers

03AI and Automation Lab

  • Customer and staff agents
  • Retrieval over your documents
  • Copilots inside existing tools
  • Workflow automation

04Search Lab

  • Technical SEO foundations
  • Entity and schema graphs
  • Answer-ready content
  • AI citation tracking

05Design Lab

  • Product UI for complex work
  • Design systems
  • UX audits and redesigns
  • Marketing sites with product depth

06Data Lab

  • Warehouses and lakehouses
  • ELT pipelines
  • Semantic layers
  • BI dashboards

07Cloud Lab

  • Cloud migrations
  • Infrastructure as code
  • CI/CD pipelines
  • Container platforms

08Security Lab

  • Secure development lifecycles
  • Threat models
  • Secure code review
  • DORA and FCA resilience evidence

07Approach

Discover, build, then run.

  1. Phase 01

    Discover

    We map the workflow, the data and the risk with the people who own them, then agree scope, architecture and a fixed-price plan with one accountable lead.

    • Workshops and system audit
    • Architecture and risk register
    • Fixed scope and milestones
  2. Phase 02

    Build

    We ship in short increments you can see working. Tests, security review and observability are part of the build, never bolted on later.

    • Fortnightly working releases
    • Review on every change
    • Monitoring from day one
  3. Phase 03

    Run

    We host, monitor, patch and grow what we built: search, support and round-the-clock monitoring under the same contract and the same team.

    • Hosting and 24/7 monitoring
    • Search and content, every month
    • Support with a named lead

Agentic delivery

How we use AI, and where people sign off.

We deliver agentically. Claude Code agents write, test and refactor a large share of the code, working in the same repositories, tickets and pipelines as the people who lead the work. That makes delivery faster. It does not make it unsupervised.

Every change passes automated quality gates, then an engineer reviews it before it merges. The decisions that carry accountability are made, and signed, by named people.

Automated gates

  • Type checks and linting on every commit
  • Unit, integration and Playwright tests
  • Security review on every pull request
  • Dependency and secrets scanning

People sign off

  • Architecture decisions
  • Security findings and risk acceptance
  • Production releases
  • Anything regulated

08Who we work with

Who we build for.

  • Brokers and prop firms

    Firms that need terminals, execution and client portals they control, with the audit trail their compliance team will ask for.

  • Fund managers

    Emerging and established managers who need investor portals, reporting and operations tooling with data that stays correct and private.

  • Fintechs and larger firms

    Scale-ups whose first codebase has become the constraint, and established businesses that need written governance and evidence of how software was built.

  • Agencies

    Agencies and consultancies that sell the strategy and need engineering behind it. Our partner route lets you deliver under your own brand.
    The white-label partner route

09Founder

Who leads the work.

Aurion Labs was founded by Komey Tetteh, who spent 12 years at Deloitte and owned the roadmap for 25+ audit applications used by 13,000 practitioners in the UK and Switzerland. More about Komey.

11FAQ

Questions, answered.

What is a lab?

A specialist discipline with its own methods, standards and tools. Specialists are brought in where the work needs them, and the labs share one delivery lead, one engineering standard and one contract, so a project that needs software, data and security still has a single accountable team.

What size of project do you take on?

Engagements usually start with a fixed-price discovery sprint and grow into builds and run retainers for brokers, fund managers, fintechs and larger firms. If a project is too small to justify our process, we will say so.

Do you use AI to write code?

Yes. We deliver agentically with Claude Code, and every change passes automated tests, security review and a human code review before it merges. People sign off architecture, security, releases and anything regulated.

Who owns the code?

You do, from the first commit, along with the documentation, architecture decisions and infrastructure accounts.

Can you run what you build?

Yes. The run retainer covers hosting, monitoring, patching, search and support under an SLA, delivered by the team that built the system.

Do you work with agencies?

Yes. Agencies and consultancies can refer, resell or co-deliver our engineering under their own brand through the white-label partner programme.

12Contact

Tell us what has to work.

Your first call is with the person who will lead the work, not a sales script. Bring the system, the deadline and the constraints.

hello@aurionlabs.io
+44 7832 617626 Milton Keynes, United Kingdom