K
Establish trust before release.
Verified boot, rollback controls and target-specific signing determine what code may reach protected keys.
- Controlled boot chain
- Release-bound policy
- Recovery boundaries
LOCAL DEFENCE CONTROL PLANE V1.0
Your lock screen
is not the
security boundary.
Kernward coordinates the controls underneath it—boot trust, encrypted-data sealing, session shutdown and device policy—into one explicit, fail-closed state.
KW // CONTROL STATE ARMED
SEALEDVERIFIEDKEYS
BOUNDPOLICY
ENFORCED
TRUST CHAIN04 / 04
REMOTE DEPENDENCYNONE
LOCK RESPONSEIMMEDIATE
NETWORK MAINNET
VISITORS TODAY—
TOTAL VISITORS—
PUBLIC REVIEWS—
LIVE SOL / USDSYNCING
01
DEFENCE ARCHITECTURE
Four layers.
One unambiguous state.
Kernward does not paint a lock over a running session. Each layer answers a different attack path, then reports into a single local policy decision.
Seal what matters.
Protected storage is considered locked only after configured key handles and mappings are closed.
End every path.
Local, remote and service-held sessions enter the same transactional shutdown contract.
Uncertainty resolves to locked.
Clock rollback, invalid state, helper failure or incomplete enforcement never produces a false “safe” signal.
INPUT→VERIFY→ENFORCE→LOCKED
02
DESIGN DOCTRINE
Built for the moment
control changes hands.
Threats do not wait for a friendly environment. Kernward’s architecture assumes theft, offline media access, boot replacement, rollback, malicious peripherals and service failure.
See exact assurance boundaries →Local ownership
No cloud account, telemetry pipeline or recurring permission check.
Cryptographic honesty
Data-key state is the boundary. A graphic lock screen is not evidence.
Explicit limits
Device Owner, managed Linux and OEM integration remain distinct tiers.
Perpetual control
One licence, permanent v1 builds, both supported platforms.
03
ASSURANCE PROFILES
Specific claims.
Visible boundaries.
Choose a platform profile to see what Kernward controls—and what still belongs to the underlying hardware and operating system.
DEPLOYMENT PROFILEMANAGED LINUX
Protected storage, session quiescence and a local control plane.
Designed for controlled Linux images with encrypted volumes, hardened services and a verified boot policy. The convenience install remains clearly distinct from hardware-bound assurance.
CONTROLLOCAL
DEFAULTLOCKED
TELEMETRYNONE
04
LIVE FIELD NOTES
Signal from the field.
Unedited and live.
Public reviews appear as they are submitted. Verified-purchase badges are only applied after an on-chain purchase is matched.
Be the first signal.
Real feedback belongs here. We do not manufacture social proof.
Leave a field note+
05
PERPETUAL OWNERSHIP
One licence.
Two control planes.
Keep the Kernward v1 Linux and Android builds permanently. The price is fixed in US dollars and converted into an exact, short-lived SOL quote when you create an order.
Linux control planeAndroid management appPublished SHA-256 manifestV1 security maintenance
PAYMENT CONTRACTREFERENCE-BOUND · FINALIZED
01 QUOTE02 PAY03 UNLOCK
PERPETUAL PERSONAL LICENCEUS$499.00
LIVE SOL EQUIVALENTCalculating…
Fetching current SOL / USD rate…
CONTRACT V2 · QUOTE LOCKED10:00
PAY EXACTLY SOLUS$499.00
SCAN WITH A SOLANA PAY WALLET
Or open the same verified request on this device. The unique reference is attached automatically.
Open compatible wallet↗AUTOMATIC SETTLEMENT DETECTION
We check only this order reference, recipient, amount and finalized chain state.
Having trouble? Verify by signature +
Loading a live market quote. Checkout fails closed if price data is stale.
FINALIZED RPCONE-TIME REFERENCEINTEGER LAMPORTS
◆ PAYMENT VERIFIED
◆ Download SHA256SUMS verification manifest ↓
Your private release bay is open.
Download access is available for 24 hours.
01 Android / Pixel / AOSP+
- Use a dedicated device. Back it up, then factory-reset it; Device Owner provisioning requires a fresh device with no accounts.
- Download the APK and SHA256SUMS into one folder and run
sha256sum -c SHA256SUMS. The Android line must report OK. - During initial setup, enable Developer options and USB debugging, connect it to the trusted Linux workstation, and confirm its exact serial with
adb devices -l. - Install the signed build:
adb -s SERIAL install --no-streaming kernward-android.apk. - Before adding any account, provision Device Owner:
adb -s SERIAL shell dpm set-device-owner dev.kernward.agent/.KernwardAdminReceiver. - Open Kernward, verify “Device Owner” and “Policy ready,” set a strong Android screen lock, then test Lock Now, reboot, Quick Settings lock and failed-unlock throttling.
For a high-assurance Pixel/AOSP deployment, stop here until the exact device codename, AVB keys, rollback indexes and factory recovery image are independently verified. The APK does not own the bootloader.
02 Samsung Galaxy+
- Charge above 60%, record the exact model/build and back up the device before resetting it.
- Follow the Android Device Owner steps above. Samsung retail firmware may add setup restrictions; do not bypass Knox or flash a generic image.
- Run the included read-only workstation preflight with the connected serial and exact model:
android/samsung/preflight.sh SERIAL EXPECTED_MODEL. - If preflight exits 3, no boot-chain update is authorised. Keep the Device Owner tier and do not use Odin, fastboot, cross-model firmware or a guessed partition image.
Boot-chain work requires an OEM-signed, model-specific A/B OTA, operator-controlled signing and a proven rollback path. It is a separate, confirmed hardware project.
03 Managed Linux x86_64+
- Start in a disposable VM or a backed-up test host. Do not arm Kernward first on a workstation holding valuable unlocked data.
- Verify the release:
sha256sum -c SHA256SUMS, then extract withtar -xzf kernward-linux-x86_64.tar.gz. - Inspect the policy, protected mapping names and systemd units. Run the packaged installer as root:
sudo ./kernward/install.sh. - Configure exact LUKS mappings, session users, TPM-backed generation state and recovery before enabling anything.
- Run
sudo kernwardctl lockin the test environment and prove sessions stop and mappings close. Only then runsudo systemctl enable --now kernwardd.service.
The installer deliberately stages files without enabling the fail-closed service.
Kernward materially raises the cost of attack but cannot make a general-purpose device “impenetrable.” High-assurance deployment requires supported hardware, controlled signing and target-specific validation. Network fee is separate.