Moderation queues and tools
Reports routed to reviewers with context and a decision recorded.
Moderation queues, reporting flows and the infrastructure for a user base that arrives at once. Built on a platform that took 30,000+ concurrent users.
The Online Safety Act puts duties on services where users can post to each other. The systems that let a platform find, review and remove content have to work at the same scale as the feed.
a platform that carried 30,000+ concurrent users, built on microservices and AWS Kinesis
We have no published social networking case. We say so on the first call and show the closest work.
Reports routed to reviewers with context and a decision recorded.
Users report, moderators decide, and the record shows both.
Microservices and event streaming for spikes.
Profiles, groups and permissions.
Volumes, response times and outcomes.
Settings and defaults for young users.
These come from Ofcom and gov.uk pages on the Act.

Different sector, same load. A platform connecting thousands of users had to support 30,000+ concurrent users, with one month for the first phase. We delivered on microservices and AWS Kinesis, with .NET and Angular.
Teams past the first version and facing real traffic.
Where one event brings the whole audience at once.
Products where reports and age checks are daily work.
Teams who need better tools around the moderators they already have.
Related reading: game software, news and media software and politics software.
Not yet published. We say so on the first call and show the closest work, which is a high-concurrency platform delivered in one month.
No. That advice comes from your lawyers and Ofcom. We build the moderation and reporting systems they specify.
Usually. We start with the queue and the audit trail, then connect it to your content store.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes with the engineers on how a report travels, who sees it and how long it takes.