What we set out to build
A copy-trading product that competes on the thing that actually breaks copy trading — slippage between leader and follower — rather than on a leaderboard.
What was built
- A follower engine measured on tracking error against the leader, continuously
- Prop-firm rule headroom modelled as a first-class constraint: daily loss, total drawdown and consistency rules checked before a copied trade is taken
- An embedded database rather than a container dependency, so the desk runs locally
- Connector architecture designed around the reality that serverless platforms cannot hold long-lived exchange connections
What it achieves
- The wedge is measurable: a follower can see exactly how far their fills drifted from the leader's, which is the number every other copy product hides
- Rule headroom is shown before the trade, not discovered after a breach
The stack
TypeScript, PGlite, exchange connectors.
Common questions
How was this built?
A founder brought the idea and the domain knowledge. We brought the team. The founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.
What state is it in?
Built, pre-launch. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.
Can you build something like this for us?
That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.
Where to next
If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.