iGaming · VCM
VCM for an iGaming site — batch rate ops, and a bid that flexes by currency and conditions.
Under NDA we extended the operator's currency manager: batch updates to FX, and a bid built per currency and condition — deposit, withdrawal, method, VIP — so the rate on the site is a rule, not a midnight paste.
- rate ops
- Batch
- bid
- Variable
- client
- NDA
One mid for every corridor was a lie
The site showed a single mid. Deposits, withdrawals, crypto ramps and fiat rails do not share a spread. Finance pasted CSV at night. We made VCM the source of the published book.
Batch operations
Ops select a set of pairs, a book date, a source. Preview the delta. Apply. Roll back. No row-by-row clicking through 40 currencies when a feed moves.
- Batch import and apply with a dry-run
- Locks so two people cannot publish the same book
- History: who published which bid, and from which feed
Bid by currency and conditions
The bid is not mid plus a constant. It is a function of the pair, the rail, the direction, the VIP tier, sometimes the amount band. EUR deposit is not USDT withdrawal. The cashier gets the bid the rule produced, not a guess.
NDA note
Brand names, pairs and spread figures are not disclosed. Engagement scope: VCM batch operations and condition-based bid on an iGaming site.
Technologies
- TypeScript
- Postgres
- Redis
- Go
Outcomes
- Rates update in batches, with preview and rollback
- Bid is composed per currency and condition, not one global mid
- Cashiers and lobby read the same published book
Recommended articles
Blog
The case for boring web stacks
TypeScript, Postgres and edge deployment are not exciting — they are how you still iterate fast in year three without rewriting the platform.
Blog
Shipping evals before prompts
Why we run regression suites on LLM outputs before every release — and how it changed our AI delivery cadence at ZNN.
Blog
Mobile release trains that do not break
Fastlane, staged rollouts and feature flags — a practical playbook from eighteen App Store submissions without a Friday-night rollback.
Recommended case studies
Luxury · Volume eDTL
The Brand Collector
The Brand Collector resells pre-owned luxury through a supplier network. Same class of problem as a catalogue feed — except each dump crossed 120,000 rows, and the CSV they hold sits above 169,000. Fastify stayed the orchestrator. The heavy compute moved to Go workers. About 60% faster on taxonomy, mapping and pattern-match at that volume.
iGaming · Platform
Casino operator · NDA
Under NDA we stabilised three production gambling brands: cleaned up legacy PHP/JS stacks, extracted shared modules, and shipped a new marketing site without stopping live traffic.
Marketing · Fintech
Digital DAO
Digital DAO is a marketing studio in Belarus that works mostly with fintech. We did not repaint the old site. We rebuilt the story and the visual system so it would sit in a room with banks, not with a carnival agency deck.