Verified gaming identity platform
GAMERGRAMA gaming record - players can trust.
A platform where players link their game accounts and build one verified profile - rank, clips and results pulled from the game itself - so coaches, recruiters and squads can judge them on evidence instead of screenshots. We rebuilt its media delivery and database layer and rolled a new interface onto the live product without changing the stack or breaking a feature.
NovaX✓ VERIFIED
Entry fragger · Jaipur · 13+
Recruiters watching verified players
Team Veloce · trial for their Valorant roster
- Live at
- gamergram.gg ↗
- Region
- India
- Timeline
- 2026
- Platforms
- Web · iOS · Android
Mobile
The same product, built for a phone - not shrunk onto one.
Shipped to the App Store and Play Store, with push, OTP and payment flows tuned for how people actually use the product on the move.
- Web
- iOS
- Android
The problem
What made it hard
The claim the product makes is trust - a rank on a profile has to be worth something to a recruiter. That puts the weight on evidence: verified account links, clips that load instantly anywhere, and a data layer that can serve a feed without slowing writes. All of it on a live product, with one hard constraint from the owner: do not change the tech stack, and do not break anything that currently works.
Our role
- Infrastructure architecture
- Media CDN
- Database migration
- UI implementation
- MVP scope
The approach
How we solved it
- 01
Verified account linking across Valorant, BGMI, CS2 and Apex, so rank and match history come from the game rather than a self-reported field.
- 02
S3 plus CloudFront for every clip and image, with signed uploads, cache policies tuned per media type and origin access locked to the distribution.
- 03
A standalone managed database with automated backups, retention windows, encryption and least-privilege access, replacing an application-local setup.
- 04
Primary and read-replica topology with separate read and write paths, so profile and discovery traffic scales without touching write throughput.
- 05
Flyway kept as the migration authority so the existing schema history stays intact and future features migrate the way the old ones did.
- 06
A new UI set - splash, onboarding, sign up, login and home - applied to the live web and app codebases as layout, theme and UX only, plus sign-up through Google and mobile OTP behind a 13+ age gate with unique username checks.
Architecture
What it runs on
- Media
- S3 origin behind CloudFront CDN
- Database
- AWS RDS PostgreSQL, primary + read replica
- Migrations
- Flyway, existing history preserved
- Identity
- Google sign-in, mobile OTP, 13+ age gate
- Verification
- Linked game accounts, synced ranks
- Constraint
- No stack change, no regressions
- AWS S3
- CloudFront
- RDS PostgreSQL
- Read replicas
- Flyway
- OTP auth
- Google OAuth
Outcome
What changed
CDN
clips served globally
Replica
reads split from writes
Zero
features broken in migration
4 games
accounts linked and verified
Want this level of detail for your own product? The architecture document comes out of discovery - and it is yours whether or not you build with us.
Book a consultationNext case study
TAB The AirBox