Building Rilogram: How an Event Chat for Royale Gaming Evolved into an Invite-Only SaaS & Mobile App
Originally built as a direct host chat for a gaming community client called Royale Gaming, I rebuilt the project into Rilogram adding an invite-link system to secure inboxes, and launching both a SaaS web platform and a mobile app.
www.royalegamingg.comSystem Overview
Rilogram started out as a simple client project for a gaming community called Royale Gaming. At first, it was just a direct chat system where any user could message the host during events there was no invite system back then. While that worked for basic communication, leaving the host inbox wide open created clutter and privacy issues. When I decided to turn this into a full SaaS product called Rilogram, I completely overhauled the chat security by adding a host-generated invite link system. I also developed a companion mobile application. Today, the platform runs on royalegamingg.com, which is the original domain where the client project was first deployed.
Architecture Blueprint
The core upgrade from the old client build to Rilogram is the invite-first inbox architecture. Instead of letting anyone ping the host directly, the host generates a unique invite link and sends it to a specific user. Both inboxes stay completely locked until the user opens the link and accepts the invite. Once accepted, a private real-time WebSocket connection is established between both parties. This invite flow runs across both the web dashboard and the native mobile app, keeping inboxes completely spam-free.
1. The Original Client Project: Royale Gaming's Direct Chat
I originally took on this project for a client who ran an active gaming community called Royale Gaming. They hosted regular tournaments and gaming events and needed a web-based chat tool so players could contact the host with questions or event check-ins. In that initial version, the setup was very simple: any visitor or player could open the page and send messages directly to the host. There was no invite system, no access barrier, and no verification. It solved the client's immediate need to talk to players, but having an open door to the host's inbox naturally meant anyone could send messages, creating clutter during high-pressure match days.
2. The Evolution into Rilogram: Introducing the Invite Link System
After seeing the shortcomings of an open direct chat, I decided to take the project further and rebuild it as a standalone SaaS product under a new name: Rilogram. The biggest feature I introduced during this transformation was the invite link system to make communication intentional and secure:
- Before Rilogram, there was no invite system—users simply sent messages straight to the host.
- In Rilogram, the host generates a unique, private invite link from their dashboard.
- The host sends that invite link directly to the specific player or participant.
- The recipient opens the link and accepts the invite.
- Only after the user accepts the host's invite does the chat inbox unlock for both parties.
- Without an accepted invite, no inbox exists and nobody can message the host, eliminating all unwanted messages.
3. Why the Domain is Still royalegamingg.com
People often ask why Rilogram is hosted on royalegamingg.com instead of a generic domain. The reason is straightforward: that domain was purchased and configured for the original Royale Gaming client build. When I rebranded the platform to Rilogram and added the SaaS architecture, I kept the live deployment on royalegamingg.com to preserve existing users, avoid downtime, and keep the production infrastructure intact while the product grows.
4. The Mobile Application: Chatting on the Go
Gaming community hosts and players don't just stay behind desks; they are constantly on their phones coordinating teams and checking event brackets. As part of turning Rilogram into a complete product, I built a dedicated mobile application version of Rilogram with the exact same secure invite-link chat system. Whether someone is using the web platform on a browser or the mobile app on their phone, inboxes only unlock after an invite is accepted, and messages sync in real time through WebSockets with instant push alerts.
Technical Challenges & Solutions
From Open Chat to Invite-Only Inboxes
In the original Royale Gaming build, anyone could message the host directly. When rebuilding it as Rilogram, I introduced an invite gate where neither party can start chatting until an invite link is created and accepted.
Why the Domain is royalegamingg.com
The platform was originally built and launched for the Royale Gaming client on royalegamingg.com. When I rebranded the project as Rilogram and turned it into a SaaS, I kept the live deployment on that original domain to preserve live links and active users.
Companion Mobile Application
Built a dedicated mobile application version of Rilogram alongside the web platform with the same secure invite-link system, giving organizers and players instant push notifications during live events.
Real-Time Socket Room Isolation
Configured Socket.IO and Express to only open private chat rooms after verifying that the invite link was mutually accepted in the database, delivering messages in under 100ms.
More Engineering Case Studies
View All Case Studies →
Architecting RopeWallet: High-Throughput Digital Settlements, 256-Bit Audit Security & Web3 Motion
