GIBLEX Phantom Suite
Company

Own the keys. Own the system.

Giblex builds local-first security software for people who would rather not hand their most sensitive systems to someone else's infrastructure.

Why Giblex exists

Over the last decade, the default answer to almost every security problem became "put it in the cloud." Storage, authentication, recovery, identity — all of it routed through remote services and remote trust. That trade buys convenience, and it quietly moves control away from the person who owns the data.

Giblex starts from a different default. Sensitive systems should stay close to the people who own them, and access should depend on conditions those people actually hold — a device in hand, a key they control — not an account a third party can reach.

The approach

Every product under the Phantom name follows the same discipline: keep workflows local, make possession part of access, and stay honest about the limits. Tools are built to work independently but share one trust model, so the suite stays composable without becoming a single point of failure.

The security model is published in the open — principles, architecture, and threat model — because a security claim you cannot inspect is just marketing.

Why there is no sign-in portal

You may notice that Giblex has no user accounts, no login page, and no online dashboard. This is not an oversight — it is a deliberate part of the trust model.

Accounts are attack surface

Every account system is a centralised list of targets. A credential database can be breached. A password reset email can be phished. A session cookie can be stolen. By eliminating accounts entirely, Phantom products remove a whole class of attacks from the picture — there is nothing to breach because there is nothing to hold your identity.

The device is the identity

Phantom products treat the device itself as the trust anchor. Access is granted because you have the right machine, the right USB device, or the right combination of local secrets — not because you authenticated against a remote server. The possession of the hardware is the credential. An attacker who cannot physically touch your device cannot impersonate you.

Local-first means the vault owner is the authority

When your vault lives on your device and is encrypted with keys derived from conditions you control, there is no Giblex server that can grant or revoke your access. We cannot be subpoenaed for your data because we do not have it. We cannot lock you out because there is no lock on our end. The only person who can open a Phantom vault is the person holding the device and the required secrets.

What this means in practice

  • No "forgot password" flow — your access conditions are things you possess, not things we remember for you
  • No account recovery via email — recovery is handled by Phantom Recovery, a separate controlled process under your own authority
  • No subscription dashboard or portal login — licensing is verified locally, without phoning home
  • No remote session management — sessions are bound to the device and end when you choose

If you are accustomed to apps that let you reset access from your phone, this is a real tradeoff to understand. Phantom products do not make access recovery effortless — they make it controlled. That control belongs to you, not to us.

What we build

The Phantom suite spans encrypted storage, USB-based authentication, controlled recovery, and split-key device-bound access. Four tools, one trust model: nothing sensitive leaves the device, and possession of a physical key is part of getting in.

Giblex Pty Ltd is an Australian company. Products are in active development, with early access opening through the waitlist.

Early access

Follow the build

Join the waitlist for progress updates and early-access releases, or get in touch directly.