Skip to content
OnionZero
STATUS: 100% AIR-GAPPED · CORE INTACT Technical Briefing
OnionZero
STATUS: 100% AIR-GAPPED · CORE INTACT
Technical Briefing
TR EN

INDEPENDENT CRYPTOGRAPHIC R&D LABORATORY

We engineer the vault your software ships inside.

OnionZero is built by HBY Software as an industrial software-fortress: a native C core, offline-verifiable signed licenses, and an encryption format designed for terrain where the cloud never reaches.

  • ESTABLISHED 2019 — ISTANBUL
  • COORD 41.0082° N / 28.9784° E
  • CORE NATIVE C · ZEND INLINE
  • NET BUDGET 0.0 KB OUTBOUND

/01MISSION LOG · 2019 → 2026

From a field problem to an air-gapped release

Every station on this rail exists because somebody’s production machine, somewhere without internet, taught us a lesson. Scroll the log — the chronology fills as you descend.

MISSION LOG // SCROLL TO ADVANCE

  1. 2019 ORIGIN

    ORIGIN

    The field problem

    License files cloned between machines and source code leaking out of offline customer facilities — the gap was witnessed first-hand. The requirements list for OnionZero was written on that shop floor.

  2. 2020 PROTOTYPE

    PROTOTYPE

    First offline license engine

    A PHP-side, domain-locked licensing core that works with zero connectivity. It proved the model, and exposed exactly where a pure-PHP approach runs out of road.

  3. 2021 FORMAT

    FORMAT

    OZP1 v1 container

    A per-file encryption envelope: every source file sealed with its own randomly generated key under AES-256-GCM. No static obfuscation, no reusable keystream, no plaintext resting on disk.

  4. 2022 RUNTIME

    RUNTIME

    ozguard native extension

    The decryption layer moved into a C extension living inside the PHP engine: sealed bytes decrypted in memory during the compile phase and handed straight to the Zend executor. Plaintext never touches disk or swap.

  5. 2023 BINDING

    BINDING

    Hardware fingerprint lock

    Licenses began binding to a machine fingerprint — CPU, motherboard and interface identifiers fused into one signature. A copied package on foreign hardware simply refuses to open.

  6. 2024 INTEGRITY

    INTEGRITY

    Ed25519 envelope + anti-rollback

    Every license and update artifact moved under an Ed25519 signature envelope, guarded by a monotonic counter. Time in the vault only moves forward; rolled-back states are rejected on sight.

  7. 2025 COMMAND

    COMMAND

    Self-hosted licensing panel

    The whole licensing backend became self-hostable: machine quotas, install telemetry and signed update delivery behind your own perimeter — with the cryptographic test suite (Wycheproof vectors) wired into CI.

  8. 2026 RELEASE

    RELEASE

    OnionZero — general availability

    The hardened enterprise release: air-gapped verification, tamper-lock semantics, a Windows/Linux build matrix for PHP 8.1–8.4, and the deployment discipline of critical infrastructure.

/02FOUNDER’S VISION

//

Software sold into the field shouldn’t have to trust the field. Protection is not a feature you bolt on after the sale — it is the architecture. We build OnionZero so that a license remains mathematics, not a promise.

Hasan Berat Yıldız

Founder & Principal Engineer — HBY Software

The lab behind OnionZero is a product of HBY Software, an independent software house specialized in enterprise engineering and software security.

/03THE MANIFESTO

Five laws of the air-gapped vault

These are not marketing claims; they are constraints we refuse to relax, written into the code and into the release process.

  1. 01

    Zero plaintext on disk. Ever.

    Source exists as plaintext in exactly one place: the process memory of the machine that holds the license. Swap, temp files and caches never see it.

  2. 02

    Offline is the default, not the fallback.

    License verification is signature math over a pre-installed public key. It needs no socket, no DNS, no certificate authority — it works in a lead-lined bunker at month thirty of a deployment.

  3. 03

    Every artifact is signed and reproducible.

    Licenses, update packages and extension builds ship under Ed25519 signatures. What we built is what you run — byte for byte, verifiable by you, without us.

  4. 04

    Time moves forward or not at all.

    A monotonic anti-rollback counter rejects re-flashed states, replayed counters and back-dated licenses. Once advanced, the vault cannot be turned back.

  5. 05

    Nothing phones home from your bunker.

    Self-hosted deployments emit zero bytes of outbound telemetry. Your machines, your network, your air gap — sovereign by construction.

SEALED // AIR-GAP VERIFIED

OPEN A CHANNEL

Brief the lab on your deployment terrain

Tell us about your environment — the PHP version, the hardware, the air gap — and we will answer with an architecture, not a brochure.

Contact the laboratory Read the documentation