GIBLEX Phantom Suite
Phantom Obscura, Attestor, Recovery and Key suite emblems
Local-first · Device-bound

Access that unlocks only on the system you control.

Giblex builds local-first security tools. Instead of routing sensitive storage, access, and recovery through cloud accounts and remote trust, Phantom products keep them on the device the owner holds — and on the USB keyfile the owner carries.

4Phantom tools
0Cloud dependency
1Trust model
The model

Security with fewer assumptions

Most software puts remote infrastructure in the middle of access, storage, and recovery. Giblex takes the narrower path: keep sensitive workflows local, and make physical possession part of access where it matters.

01 — local

Keep workflows local

Sensitive data stays on systems the owner controls, rather than depending on remote infrastructure by default.

02 — possession

Make possession part of access

Split-key and device-presence checks let protected workflows require something you physically hold.

03 — composable

Independent, shared trust

Each Phantom tool solves a different problem, but all of them run on the same local-first security model.

Phantom Obscura vault detail view
In development · flagship

A vault that stays local and opens only when it should

Phantom Obscura keeps credentials, keys, cards, notes, and identity records in a local encrypted vault. Unlocking it requires a USB keyfile — a password is an optional extra factor on top, not a substitute.

  • Encrypted at rest, fully available offline
  • A USB keyfile is required to create or unlock a vault — possession is part of access, not an option
  • Your data stays on the system you control, not a sync layer
How it holds up

The model, explained in the open

Three pages set out exactly what Phantom protects, how it is built, and where the limits are — in plain language, then in technical detail.

/ principles

Security principles

The assumptions behind local storage, device presence, and controlled recovery — stated plainly.

Read principles →
/ architecture

Architecture

The layers behind root trust, vault containers, session control, and integrity enforcement.

Read architecture →
/ threat model

Threat model

What Phantom products are designed to protect against — and what stays out of scope.

Read threat model →
Early access

Join the Phantom waitlist

Phantom products are under active development. Join the waitlist to follow progress and get early-access releases first.