What we do
Retrieval, assistants, and classification built on top of models rather than around them. Evaluated before they ship.
Server-rendered applications that stay fast on a mid-range phone. Accessible by default, not as a later pass.
Documented, versioned HTTP interfaces for people who are not in the room. Stable contracts, honest errors.
Evidence
Three projects measured themselves, and the measurement came back against them. Each one names the file that says so.
Nothing here was found by a reviewer. Each is in the project’s own output or its own source.
Open source
Star counts read from GitHub on 4 September 2026. Two repositories are private and are not counted.
Selected work
Stack
Not a capability list. Counted from the projects themselves.
Ordered by how many projects use each one. Tools that appear in a single project are left out.
For developers
Documented before it is announced, and thin enough to read in an afternoon. These lines are from the README.
pip install rone-arenaSecurity
One short policy, published in every repository. Research inside its limits is authorised in writing.
A human reply inside the published window. The same promise is in every SECURITY.md.
Research within the stated limits is authorised. We will not pursue legal action over it.
The weaknesses we decided to live with are written down, so nobody rediscovers them.
RFC 9116, with a fixed expiry. A date that is always fresh tells a reader nothing.
From people who use it
Unsolicited, and quoted as written. Two are building products of their own on these endpoints.
“Thank you for your API for MLBB, it has been very helpful and supports the community.”
Every one of these is a full five. Nobody was handed a rating scale — the feedback arrived as sentences, and none of them is qualified, so none is scored below five. If one ever comes back mixed, it will be published with the number it earned.
Square brackets mark one edit and one only: a product name that has since changed. Rone Arena was called the MLBB Public Data API when some of these were written, and rewriting the sentence around it would have been misquoting the person who wrote it. Where a quote names the game or the data source rather than the product, it is untouched — those were accurate then and remain accurate now.
Where it runs
Two things worth checking before you email anyone: who we are on the register, and what this runs on.
4701130820260086
Tell us what you are building. If we are not a fit, we will say so.