Security work from the first week of October
What we closed after an internal audit, and how we back up our code.
The database is no longer public
The production database was reachable from the internet. It isn't now: the API reaches it over the internal network only.
Fixes from our audit
We went through an internal audit and fixed the findings: authentication, server-side request handling, ownership checks on your data, a stricter content security policy, and separate sessions for each admin. Error messages from our MCP tools no longer leak internals.
Backing up our code
Our source code is mirrored every hour into encrypted storage in a different location from our servers, and a missed hour alerts the admins. We tested a restore from the real backup. This covers code, not customer data. Customer-data backups are a separate job, and we'd rather say so than blur the two.