SeiBoost

01The problem

The dashboard had to show live operational state to many users at once while still drawing lines around who may see what. Polling the server every few seconds from every open tab is a fast route to a saturated database — with a few dozen people logged in, the traffic grows faster than the value it delivers.

02What I built

• WebSockets over Soketi instead of polling — the server pushes the change and the browser never has to guess.
• Private channels per role and per team, so authorisation holds at the transport layer, not only in the view.
• Redis as the middle layer for events and read caching, leaving PostgreSQL to handle writes rather than refresh traffic.
• The schema is driven by Prisma migrations, so a model change is versioned alongside the code instead of clicked into a panel.

03What it does now

• A state change appears for every authorised user without a page refresh.
• Permissions are enforced in one place — adding a role does not mean auditing every view.
• Everything runs in Docker, so local and production are the same environment.