Zenith Dual

Zenith Dual turns your install into a local multi-profile platform — like picking who watches Netflix on the TV: one app, separate spaces.

What is my «Profile»?

A profile is your local identity inside Zenith. Each profile has:

Its own indexed library (zenith.db)
Listen stats, playlists, and taste data
Visual settings (theme, accent)
Optional Vault for private tracks

You do not duplicate music on disk. Multiple profiles can share the same music_root. What stays separate is metadata, history, and preferences.

On launch you see the Identity Gate: «Who is listening?» Only one profile is active; audio and queue belong exclusively to it.

Why the Vault PIN?

The PIN is not friction — it unlocks your encrypted Vault:

Vault tracks are encrypted with Argon2id + XChaCha20
The PIN is not stored in the UI or in plain text
Another profile on the same PC cannot read your Vault without the PIN

Security advantage: you share the PC and want certain downloads or private folders hidden from others. Without a PIN, the profile is still DB-isolated, but the Vault has no extra layer.

You can create profiles without a PIN. Guest is temporary and does not persist sensitive data.

Data Bridge (between profiles)

To let another profile «know» a track without copying the file, use Data Bridge in Settings → Zenith Dual. Exports metadata, listen sessions, and library state to the target profile.

Backup before reinstalling

All Zenith Dual data lives under your Windows app folder:

%APPDATA%\com.gabri.zenith\

com.gabri.zenith\
├── profiles.json
├── core\
└── profiles\
    └── {id}\
        ├── zenith.db
        ├── vault.json
        └── …

To back up Dual completely:

Quit Zenith fully.
Copy com.gabri.zenith to external drive or private cloud.
After reinstall, restore the folder to the same path.

Important: if a profile has a Vault PIN, you need that PIN after restore. Zenith cannot recover a Vault without the key derived from the PIN.

Health and maintenance

Settings → Zenith Dual → System health shows disk space, DB fragmentation, and orphan files per profile. Pro Maintenance runs VACUUM on profile databases.

Leer en español · More help