What goes into the platform, with its date. It is the most honest proof that a product is moving.
Inbox
The privacy policy now covers Sound Republic OS: what the Inbox keeps from each message that comes through Meta, what for, who else sees it, for how long and how to ask for it to be deleted.
Creators
The value of each mention gets worked out, stored and audited — and the second version fixed the fact that it was looking at only a third of what matters.
Creators
A piece deleted after three days only half delivered, and now it shows. And everything stored about a person has an expiry date, with a warning before deletion.
Creators
A column that ranks your creators by relative performance, not by followers. It is where the ones who come cheap and work show up.
A status dashboard that verifies each piece is working, not that its configuration is filled in. The first version did the second and was corrected the same day.
Rather than hiding what is not built yet, the dashboard shows it disabled. You know what is there, what is coming and what you cannot use yet.
Creators
A story deleted after twenty minutes is not the same side of the bargain as one that lasts the full twenty-four hours. Now they are told apart, and the piece is kept for six months.
Web
The two things people actually ask for after a purchase, sorted where the order is and not across three different tools.
Web
The ticket store exists and payments connect from the dashboard, with a distinction almost no system makes: being connected is not the same as being able to take money.
Creators
A mention from someone in the programme and one from an outsider are not the same thing. They get told apart, and the outside ones become the list of people worth talking to.
Inbox
First piece of the Inbox: the knowledge base goes into the system and comes out through the API. There stops being one version on the site and another in the head of whoever is replying.
Row-level rules forced in the database: not one badly written query can return another client's data. It is the first stone, not a later hardening.
Direct Sales
Entry scans and messages to the customer are stored. When somebody says they were never told, there is something to answer with.
Direct Sales
Month-end stops being an afternoon of reconciling figures: commission comes out of the same data as the sale, and payout is requested and approved inside the system.
Direct Sales
Admin, leader and promoter talk inside the booking they are talking about. No more reconstructing a table change from three WhatsApp screenshots.
Data Science
If a piece is missing to work out an indicator properly, the indicator gets flagged as provisional rather than shown as if it were complete. It is a rule of the system, not a preference.
Studio
The full pipeline works: from the folder of rushes to assembled pieces, run on real recordings and not on a test case.
Web
The integration renews its own session. Before, when it expired somebody had to go in by hand — and until they did, nothing synced.
Web
What gets sold outside the ticketing platform lands inside it without anyone typing it in. It is the piece that lets you sell through other channels without doubling the work.
Web
Every sync reports in, there is a status endpoint, and one specific booking can retry on its own. Finding out something is not syncing stopped depending on somebody looking.
Direct Sales
Team isolation is enforced in the database, not on the screen. A leader cannot see another team's sales even by forcing the URL.
Creators
The check-in of somebody arriving on a guest pass is attributed to whoever invited them. The list stops being an anonymous cost.
Data Science
Not just how many tickets you have sold: when they get bought. It is what decides when you launch a campaign and when you are launching it late.
Creators
Not a decorative card: the pass code is the ticket code, so the door scans it like any other and the entry gets recorded.
Floor
Two stars or fewer trigger an alert on the phone, not a line in next month's report. And whoever is on the floor can write to their manager without leaving the system.
Floor
A QR code per member of staff, a private page with what they have generated, installable on their phone. The review stops being about the venue in the abstract and becomes about whoever served.
Data Science
A supplier changes a field and your history starts lying without anything failing. Now the change gets detected, normalised and logged.
Creators
The exchange is set out, the system checks it happened, and without delivery there is no access. A guest list with a measurable other side.
Direct Sales
Everyone who sells has their link, their panel and their commission worked out by the system — one person or one business, the mechanism is the same. And the door has its own role, with check-in against the booking.