Telephony, healthcare, fintech and gaming platforms — built by a senior team, shipped fast, engineered to hold up under real load.
We're a small studio with eighteen years of combined engineering experience, most of it spent on systems other people relied on without ever seeing our name on them — big companies, big traffic, the kind of work where the highest compliment is that nobody noticed it.
At some point we got tired of only building other people's ideas. So alongside client work, we build our own products and write down what happens. Some of it works. Some of it doesn't. Both are worth talking about.
Right now our time goes into call tracking and triage platforms, AI-assisted development tools, and — on evenings and weekends — a multiplayer shooter, because a studio this serious needs one project that's purely for fun.
We keep a small number of client engagements running at a time, on purpose. Email us and we'll tell you honestly whether we have room.
Honest version: these are where we'd back ourselves against most teams. The bars are our own read on it, not a certificate.
Dialers, routing, and pay-per-call systems. Getting a call to the right person in under a second, over whichever carrier is cheapest that day.
Putting language models into real products where they have to work every time, not just in the demo. Agents, tooling, and the boring plumbing around them.
Clinical workflows and compliant systems, where a routing bug is a patient who didn't get a nurse. Built for audits from day one, not retrofitted later.
Real-time 3D, multiplayer netcode, and the kind of feel-it-in-your-hands polish that game engines force you to care about.
Telephony, healthcare, crypto and games — a sample of what we've shipped. Click into any of them for what it does, why it was built, and where it stands.
See exactly which campaign, keyword and creative drove every phone call — not just every click.
A dialer with a full CRM behind it, for call centres, brokers and support teams. Bring your own carrier.
Electronic medical records built around how clinicians actually work — one connected chart, not six tabs.
Admissions, beds, scheduling and billing for a multi-site hospital group, on one system instead of six.
Real-time pipeline, forecast and rep-performance dashboards on top of the CRM you already use.
A spot exchange built for latency first — matching engine, custody and compliance in one stack.
A non-custodial mobile wallet with recovery that doesn't depend on a seed phrase written on paper.
Mint, list and trade NFTs, with creator royalties enforced on-chain on every resale.
Permissionless token swaps with a router that finds the best price across every liquidity pool.
A round-based shooter in Unreal Engine with a twist: capture one asset and hold it for ninety seconds to win.
A turn-based strategy game where every choice has an opportunity cost that shows up ten turns later.
Matchmaking, lobbies and server-authoritative netcode we now drop into every multiplayer title we ship.
Not a list of everything we've touched — just what we actually reach for, and what we use each one for. All of it is in something currently running.
Large enterprise front-ends where structure matters more than novelty. Most of our consultancy work lived here.
Product UI where things change weekly. Our default when the interface is the product.
Anything that needs to be fast on first load and rank in search. All four project dashboards run on it.
Streams of events that arrive out of order — live call feeds, socket updates, anything you can't wait on.
Structured Node services. When a team is going to inherit the codebase, the opinionated framework wins.
The workhorse. API layers, job runners, and the glue between everything else.
Where milliseconds are the product. The hot path of the bidding engine is headed here.
Every project on this site. We'd rather push logic into the database than build a service to do it.
Wiring language models into real product surfaces — not a chat widget bolted on the side, but a feature that fits the interaction it's replacing.
Plumbing for LLM features — retrieval, tools, and getting models to talk to real systems.
Agent workflows that branch and loop. When a chain isn't enough because the work has actual state.
Running and fine-tuning open models when sending data to an API isn't an option.
Classic ML — scoring, classification, and the prediction work that predates the LLM era.
Vector search at a size where doing it yourself stops being clever and starts being a second job.
Real-time updates that don't need a full WebRTC stack — live dashboards, call queues, chat. The default when Node already owns the connection.
Peer-to-peer audio and video in the browser, no plugin required. Underneath every voice feature we've shipped.
The SFU behind anything with more than two people on a call at once. Selective forwarding instead of every client uploading to everyone.
Wallet connections, contract calls, and reading chain state from the browser. The unglamorous half of every crypto product.
Where most of what we ship actually runs. RDS, ECS and S3 cover almost everything; we reach for something fancier only when we have to.
CI/CD, infrastructure as code, and the pipelines that make "it works on my machine" somebody else's problem.
Real-time 3D for the game projects on this site. Nanite and Lumen changed what a small team can ship without a dedicated art department.
Global consultancies, telecom operators, healthcare systems, hospitality groups and industrial firms — across the Gulf, Europe and the US. Some were long engagements. Some were one hard problem.
Some of these are proper articles. All of them are things we're happy to be argued with about.
A game has to respond in 16 milliseconds or it feels broken. Most AI tools have no such standard.
Read it →Nobody gets excited about phone calls anymore. That's exactly why the numbers are so good.
Read it →Tell us what you're trying to do. We'll tell you honestly whether it's a fit.
Start a conversation →