We're onboarding players in waves. Drop your email and we'll send your invite code when your slot opens up.
Your code will arrive at this address when we open your slot.
A new kind of platform where your gaming journey matters. Connect, compete, and build your legacy — together.
Be the first to know when we launch. No spam.
What's Coming
One profile that captures your entire gaming journey across every platform and title.
A living system that rewards engagement. Level up by being part of the community.
Share moments, discover players, and connect with people who play the way you do.
Track every game you play. Follow new releases. See what your community is playing.
The Project
Players Engine is a social platform for gamers — one profile that gathers your games, your progress and your people, instead of leaving them scattered across a dozen launchers and chat apps. It's built by a solo founder, bootstrapped, and currently in a closed beta with real players using it every day.
The platform runs on a deliberately frugal architecture: small services that scale to zero when idle, two databases that each do what they're best at, and an engineering culture — validation at every boundary, structured logging, keyless deploys — that's written down in public. You can read the mission on the about page and the rules we hold ourselves to in the engineering standards.
The beta grows in small waves on purpose: every new group of players gets the attention their feedback deserves, and the platform gets better between waves. If that sounds like your kind of early access, request an invite.
From The Devlog
The devlog documents how Players Engine is actually built — the architecture decisions, the closed-beta lessons, and the occasional 2 a.m. war story, written by the person who lived them. Eighteen entries and counting. A few recent ones:
Every service here scales to zero, so the first request after a quiet spell pays a wake-up tax. This entry walks the anatomy of a cold start and the four fixes that actually moved the number: boot-order discipline, lazy client construction, smaller images, and measuring the p95 users really feel — plus the written rule for when we'll start paying for warm instances instead.
Read entry →Profiles and posts want O(1) reads; social features want traversals. Forcing one engine to answer both questions is how you end up hating a good database, so Players Engine runs a document store and a graph database side by side — with one-directional event-driven sync, exactly one owner per fact, and a float-versus-integer war story at the driver boundary.
Read entry →CI used to mean a downloaded service-account key: immortal, powerful, and one leak away from disaster. The deploy pipeline now exchanges GitHub's signed attestations for credentials that live minutes and can only deploy — nothing more. Included: the artifact-retention policy that quietly deleted an image production was still running, and what changed afterwards.
Read entry →After a tester's screenshot showed a button living half outside the screen, "the app is responsive" stopped being a claim and became a counted property: every route swept across six viewport widths by a headless browser, violations defined mechanically, fixes applied to shared components rather than pages — and a regression sweep so it stays true.
Read entry →Stay In The Loop
Drop your email and we'll let you know when Players Engine goes live. Early supporters get first access.
Be the first to know when we launch. No spam.