Seal the gate. Let time become the operator.

Chronos is a local-first time lock console. It forges a new password, stores the seal on this device, and inserts an hourglass between the impulse and the reversal.

Backup and restore

REVEAL AUTH GATE

PASSPHRASE CHECK

SECRET READOUT

MASK-BY-DEFAULT

HEX SCAN

TIME WINDOW ACTIVE

SEALED VAULTS

UNLOCK WINDOWS

LOCAL MEMORY

ON-DEVICE

CONSOLE SHELL

Install the time lock shell.

Offline-ready shell active. Local vault data stays on this device even while the network is down.

Network is down right now. Cached UI remains available, but new browser assets wait for connection.

MEASURED CONSTRAINTS

Honest constraints, not fake certainty.

Chronos does not pretend to be absolute security. It is a disciplined speed bump: no cloud, no recovery, no convenience layer, and no promise that a determined technical user cannot bypass local restrictions.

Data is stored only on this device.
Clearing browser data may erase everything.
Losing this device may mean losing access permanently.
There is no cloud recovery.
Chronos is not a password manager replacement.
This is a commitment tool.
A technical user may still bypass local restrictions.

ARCHIVE COMMAND BLOCK

Export and import stay client-side.

Export creates a locally encrypted file. Import decrypts locally. Neither action talks to a backend. If you lose both this device and your backup, Chronos cannot help you.

Local passphrase

Choose backup file

Import replaces current local data.

I understand import will overwrite the current device state if the backup decrypts correctly.

Vault

Current LockIns

Secrets stay masked until the lock expires and the correct passphrase is provided. There is no emergency bypass in V1. That friction is intentional.

LOCAL MEMORY // READ

The hourglass turns while the console reads the local vault.