Texas Hold'em and Omaha on a server-controlled game engine, with a secure wallet, verified players and infrastructure built to protect real money from day one.
We have already built a complete poker game in a previous project, and everything in this section is working functionality there: the game engine, web game, admin panel and player features. Our team has hands-on experience with each of these, which is what we bring to your platform. In that project, players choose from three table types.
Players see and hear each other through camera and mic. Face verification makes sure the person on camera is the real account holder.
LiveKit · FaceTecThe classic poker table with player profile pictures. No camera needed, ideal for quick play.
Classic tableAn immersive 3D poker room. Players can switch back to the 2D table at any time.
3D engineVideo and non-video players are matched to separate tables.
Shuffle, deal, bets and payouts all happen on the server. Players can't cheat from their device.
Public and private tables, with invite links to bring friends straight to a seat.
Turn timers, sit-out and rebuy windows keep every table moving.
If a player's connection drops, their seat and chips are held while they reconnect.
Next.js / React. Works on desktop and mobile browsers, with no download needed.
Manage users, tables, packages, rewards and game settings, with reports.
Google, Apple and Facebook sign-in, plus email accounts.
Push notifications to bring players back to the table.
Every step runs on the server. The player's device only shows the result, so no one can see other players' cards or change a bet.
At video tables, face verification links the face on camera to the account, and keeps checking it during play.
Compare the early-user setup of our previous poker project with the setup we propose for your real-money platform. Tap any component for a plain-English explanation.
Your platform handles real money, so we propose a setup built for it from day one. It has more capacity, no single point of failure, and the security that player funds and payments require. More players means adding servers, not rebuilding the platform.
If a server or the database fails, a standby takes over automatically.
Add servers as players grow, with no rebuild.
Backups, encryption, audit trail and fraud controls from launch.
Tested with simulated traffic before go-live.
| Item | USD / month |
|---|---|
| 2 game servers (EC2 c7g.large, 2 vCPU / 4 GB each) | ~110 |
| Web + admin server (EC2 t4g.medium) | ~27 |
| Application Load Balancer | ~25 |
| RDS PostgreSQL Multi-AZ (db.t4g.large + 100 GB storage) | ~211 |
| Redis (ElastiCache, primary + replica) | ~47 |
| Private network gateway (NAT) | ~35 |
| Public IP addresses | ~11 |
| Backups + Vault Lock | ~10 |
| S3 + CloudFront | ~5 |
| WAF firewall (web ACL, rules, requests) | ~18 |
| CloudWatch monitoring (logs + alarms) | ~20 |
| GuardDuty threat detection | ~10 |
| CloudTrail, KMS, Secrets Manager | ~10 |
| Data transfer out (~500 GB) | ~35 |
| Estimated total | USD 550–800 |
Based on AWS on-demand list prices for the US East (N. Virginia) region, November 2026. Prices vary by hosting region, and reserved pricing can lower server and database costs further.
Not included: LiveKit and FaceTec (charged per use), KYC provider (per verification), payment provider transaction fees, RNG certification and penetration testing (one-time, quoted by the testing lab), and gambling licence fees.
Added only if needed later: premium DDoS protection (AWS Shield Advanced, about USD 3,000/month), multi-region hosting and container clusters.
We have already built and delivered the core poker features in our previous project. For real money, a platform also needs these modules.
Deposits, withdrawals, transaction records and withdrawal approvals.
A gambling-approved payment provider or crypto. Stripe and the app stores don't allow gambling.
The platform's commission from each pot or tournament, which is your revenue.
ID check, age check and anti-money-laundering checks.
Only players from allowed countries can play.
A secure random card shuffle, tested by an independent lab.
No bots at real-money tables, plus detection of cheating, collusion and multiple accounts.
Deposit limits, self-exclusion and cool-off periods.
We've included only what matters for player funds, payment data and fraud prevention, with nothing added just to raise the cost.
In our previous project we built a poker engine that supports multiple betting structures (No-Limit, Pot-Limit, Fixed-Limit), including the Pot-Limit betting that Omaha is played with. With that experience, Omaha alongside Texas Hold'em is well within what we have done before.
Each player is dealt four hole cards.
Exactly 2 hole cards plus 3 board cards make the best hand.
Choose Hold'em or Omaha per table, controlled from the admin panel.
Table updates to show four cards clearly on every table type.
Real-money poker needs a gambling licence. We suggest talking to a gaming lawyer early, because the licence affects the technical setup. We'll build the platform to meet its requirements.
The licence sets the markets you can accept players from. Location blocking enforces it.
Some licences require hosting in a specific region. We choose the AWS region to match.
Such as shuffle (RNG) certification and security audits, planned into the roadmap.
Services we have already integrated and worked with in our previous project, plus the gaming-specific providers a real-money platform needs.
Live video and audio at video tables.
Worked with3D face verification and ongoing on-camera checks.
Worked withPush notifications.
Worked withSocial login.
Worked withAccount emails such as password reset.
Worked withImage and file storage with fast global delivery.
Worked withReal-money deposits and withdrawals, chosen to fit your licence.
Real moneyID, age and anti-money-laundering checks.
Real moneyPlease share the following.