Audit and the record
Every change attributed, every permission logged, and undo recorded rather than erased.
Today
- Every change is attributed. Each Patch Log entry records who or which agent made it, when and what it touched, with the file before and after.
- Undo is recorded, not erased. A rollback is a new entry, so the history shows both what happened and what was reversed.
- Changes made elsewhere are caught. Edits in other editors are recorded as External Edits, and files changed while Tortilloid was closed are recorded on the next open.
- Every permission decision is logged, automatic approvals included. See Tools and permissions.
- The record can be exported. Patch Log › Export Patch Log... saves the history to a file.
Project data is protected by your machines' own security, such as FileVault, and isn't encrypted by Tortilloid in this beta. See Known limits.
Compliance
Tortilloid hasn't completed a SOC 2 audit or an ISO 27001 certification. It helps you produce evidence for the controls those audits ask about, such as change management, logging and incident response. It doesn't make your organisation compliant by itself. Tell us what your review needs, see Shape Enterprise with us.
Coming with Enterprise
- Audit views and exports designed with security and compliance teams.
- History that holds up across large teams and very long timespans.
- Immutable off-site copies of the record, so history can't be altered or quietly deleted.
- The record kept in secure, encrypted databases, in your own cloud or on your own servers.
- Encryption at rest for project data on every Mac.