For your IT provider
The technical side, open to checking.
This page is for whoever checks BerserkOS on the port's behalf. Everything here can be verified. Ask about anything that is missing.
- Sign-in
- Named accounts, and nobody can register themselves. Two-factor is on for the office roles that run operations (administrator, dispatch, manager, PFSO, shore excursions and transport manager): sign-in on the web is confirmed with a code from an authenticator app. In the mobile app everyone signs in with their mobile number and their own code. A PFSO can decide berth requests in the app with that code. Bookings are approved on the web, behind two-factor.
- Microsoft sign-inComing
- Sign-in with the Microsoft account the port already uses (Entra ID). It is built, but not switched on.
- Separation between ports
- The port's operational data in the database is tagged with the port, and the database refuses a signed-in user access to other ports' rows. More than 100 isolation checks must pass before a new version is released. Those checks test the database rules, not the server routes. Many server routes use a service key that bypasses the database rules and check the port in code. We are going through the routes one by one, and that review is not finished. Holes we find, we close.
- Who at Berserk sees the data
- As platform administrator, Berserk can technically see every port's data, for operations and bug fixing. A log of each such access is coming.
- Email and Microsoft 365
- BerserkOS reads the port's own mailboxes, with the port's consent, through Microsoft Graph. Reply drafts are placed in the port's mailbox, and replies to agents go from the port's own addresses. Sign-in links and system alerts are sent from goberserk.no.
- Backups
- An encrypted copy of the database every hour, kept in three places. The key is not on the server. Rebuilding from a copy was rehearsed on 25 September and 13 October 2026.
- The digital helpers and AI
- The digital helpers use language models from Google (Gemini) and Anthropic (Claude), chosen per task. The port can use its own keys. No helper enters a booking, a tour list or a driving list without a person approving it.
- Where the data lives
- Servers in Germany. Database, sign-in and files in Frankfurt. Encrypted copies of the database in Germany, Finland and Norway. Traffic passes through Cloudflare. AI requests, push notifications (Expo), SMS (Twilio) and outgoing email from goberserk.no are processed in the USA. The full list of sub-processors comes with the data processing agreement.
- Privacy
- The port is the data controller. The data processor is Remedy Media AS. We write the data processing agreement together with the port before you start, and the list of sub-processors comes with it.
- How the system checks itself
- Every hour BerserkOS checks that each reply the port has sent to an agent from the connected mailboxes has a row in the call list. If one is missing, the port gets an alert. The check came after a mistake in August 2026, when a reply said “registered” and nothing was.
- What we don't have
- No ISO 27001 or SOC 2 certification. No security test by an outside firm yet. No SLA.
- Ask for the pack
- Architecture, sub-processors, a summary of the isolation tests and the latest restore drill. Write to [email protected].