A concise view of what Kept implements today.
Each property runs in its own instance and database.
Accounts, roles and surface access are assigned to individual users.
Kept does not require guest names, reservation data or payment-card data for the core workflow.
Not implemented at the application database layer.
No SAML or OAuth sign-in today.
Not implemented today.
Recovery is based on scheduled backups rather than an arbitrary recovery timestamp.
Kept's audit chain and RFC 3161 anchors are designed so the record can be checked without relying on the dashboard itself.