Security and hosting
Security built to the standards your operations committee expects
Your book of record holds borrower financials, investors’ personal data and the figures your NAV depends on, and it deserves to be treated that way. DebtLab is designed from the ground up so that your data stays private, every change has an owner and an approver, and nothing important rests on trust alone.
Hosted in London
- The application runs in London, right alongside its database, which is hosted on AWS in London.
- Documents are held in a private store in London. They have no public web address, can only be opened through the app by signed-in users, and every download is recorded.
- Emails to investors contain a secure link to the notice or statement rather than the document itself.
Sign-in
- Accounts are personal and issued by your administrator; there is no self-registration.
- Two-factor sign-in with an authenticator app and recovery codes can be optional or mandatory for each type of account.
- Single sign-on with Microsoft Entra ID or Google Workspace is available for existing accounts on the domains you allow. DebtLab’s own second factor still applies unless you choose to rely on your provider’s.
- Passwords are only ever stored as salted PBKDF2 hashes. Repeated failed attempts lock the email address for a period, and disabling an account or changing a role ends that person’s sessions immediately.
Role-based access
- Each person has a role in each module they use, such as investment team, loan operations, risk team, controller, accountant, IR lead, compliance officer or read-only.
- Every change is checked on the server against that role, and pages owned by another team open in view-only mode.
- Investors can only see their own funds and accounts, enforced on the server.
Four-eyes approval
- Ledger postings, facility amendments, covenant waivers, rating and stage overrides, model changes, manual journals, capital calls, distributions, payment files, onboarding approvals and NAV sign-off are all prepared by one person and approved by another.
- Nobody can approve their own request, and no change can be applied without its approval.
- Changes to investor bank details only take effect after a call-back to a number already on file and a check by a second person.
Audit trail
- A full audit log records who changed what and when across every module, with the values before and after.
- Settings and credit model changes keep their full history and can be rolled back, with the rollback recorded as a new change.
- Posted journals can only be reversed, as the database itself blocks any edit. Signed-off quarters, closed valuation dates and locked monitoring months cannot be changed.
- A periodic access review flags dormant accounts and approvers without two-factor, and its completion is recorded.
Backups and recovery
- Point-in-time restore of the database within the hosting provider’s restore window.
- Weekly encrypted backups of the database and documents are kept for 90 days. Each backup is restored into a clean database and checked table by table to prove it can actually be used.
- A written backup and recovery procedure is tested every week on a practice database.
Monitoring
- Server and browser errors are logged, grouped and prioritised, and administrators are alerted by email.
- Alert emails never contain stack traces, names, account numbers or tokens; instead, they link to the error log inside the app.
AI-assisted document reading
- DebtLab can read management accounts, credit agreements, compliance certificates and rate sheets and propose the figures and terms they contain. When your team uses this feature, the document is sent to Anthropic’s Claude API for extraction.
- The AI makes the suggestions and your team makes the decisions. Month locks, approvals and the audit trail apply to everything it proposes, and any term an agreement does not state is left blank rather than guessed.
Due diligence documentation
Detailed documentation written for your operations, risk and audit teams, and shared with you during due diligence so you can see exactly how DebtLab works.
Model methodology
How ratings, PD and LGD, IFRS 9 staging, ECL by scenario and DCF fair value are calculated, including their documented limitations.
Fund administration methodology
Allocation, equalisation, fees and caps, subscription lines, carry models, the NAV process and the related controls.
Access control
Roles per module, four-eyes rules, sign-in, two-factor authentication, SSO and the access review.
Backup and recovery
What is backed up, how each backup is tested and how recovery works.
See how DebtLab would work for your fund
Book a live walkthrough of our demo fund, tailored to the way your team runs deals, operations and investor reporting today, and bring your toughest questions with you.