Help us replace revshare
A small team, nine repositories and one platform that charges casinos for spins instead of a share of their revenue.
How this team works
These are the rules the team already runs on, written down. If any of them sound like a constraint rather than a relief, we are probably not the right place.
Nothing reaches production untested
Every release goes through staging and a smoke test, and rolls itself back when the smoke test fails. There is no manual path around it, including for the founder.
Verify before you report
A claim about what production does is checked against production. "It should work" is not a status, and neither is "I could not find it" before you have looked.
Agents do the repetitive half
Onboarding, partner chats, changelogs and triage run on agents with a human approving anything that costs money. You will be building that, not staffing around it.
Say what is not done
Partial work is reported as partial. We would rather hear about the half that is missing than discover it in a partner's chat.
Speak the partner's language
Operators care about spins, balances and time to go live. Internal vocabulary stays internal, and no partner is ever given a deadline we have not already met.
Small team, wide surface
Nine repositories, one platform, a handful of people. Everyone here owns something end to end and nobody hands work over a wall.
Open roles
Backend Engineer, Core Platform
Python. The metering path that counts every spin, prices it at the operator's purchase rate and deducts it from their balance. Correctness here is money, and the callback path answers on a latency budget.
Integrations Engineer, Game Providers
Bring a new game provider live end to end: their API, our contract, the certification pass, the first real spin. Each one arrives with different ideas about signatures, currencies and free rounds.
Frontend Engineer, Operator Console
TypeScript and React. The console an operator runs their casino from, and the Telegram Mini App that is becoming the way most of them do it.
Agent Engineer
The agents that run operations: partner chats, onboarding, release notes, triage. Building the tools they use and the gates that stop them acting alone where it matters.
Partner Operations
Own an operator from first contact to first live traffic, and stay their person afterwards. Half the job is spotting which recurring question should have been a product change.