WordPress Plugin
Settings UI, shortcode, and REST API (/wp-json/hkey/v1/encrypt|decrypt) for posts, forms, and custom data.
Install: copy to wp-content/plugins/, activate, configure salt.
Next-generation website data protection
HKEY seals your website’s sensitive data with gesture-derived, authenticated encryption packets built on a symmetric 256-bit, hash-based core. Install the ready-made plugin for WordPress, XenForo, or Drupal—or drop in an SDK—and add a powerful layer of resistance against AI-accelerated guessing and future quantum cracking threats.
Try changing the chords below—the ring and derived packet update to show how your sequence becomes a key.
Click “Derive & encrypt” to generate an authenticated HKEY packet.
HKEY is the fastest way to add a next-generation, AI & quantum-resistant protection layer to your website. Install a ready-made integration for one of the world’s most-used platforms or developer tools, set a context (salt), and start sealing sensitive data in authenticated HKEY packets—no cryptography PhD, no complex infrastructure required. Each integration below is functional, downloadable, and includes the HKEY v1 core (symmetric 256-bit, hash-based, tamper-evident) to help resist AI-accelerated guessing and quantum interception or cracking threats.
Protect your website data now
Download all 13 integrations (WordPress, WooCommerce, Shopify, Wix, Squarespace, Webflow, Joomla, Drupal, Magento 2, PrestaShop, Ghost, npm, Composer) or pick your platform below.
Settings UI, shortcode, and REST API (/wp-json/hkey/v1/encrypt|decrypt) for posts, forms, and custom data.
Install: copy to wp-content/plugins/, activate, configure salt.
Protects checkout/order sensitive fields with HKEY packets and WooCommerce admin settings.
Install: copy to wp-content/plugins/ (WooCommerce required), activate, configure.
Browser HKEY core + Liquid snippet and submit helper to seal form/customer fields before sending.
Install: add assets/snippet in Theme Editor and include on protected forms.
Client-side HKEY core for Velo/page code and custom elements to encrypt form inputs and payloads.
Install: add hkey.js in Velo/Public or Custom Code and wire to forms.
Code-injection snippet with HKEY JS core to protect marked form fields on submit.
Install: add footer code injection / hosted script and data-hkey-protect forms.
Custom code embed + HKEY core to encrypt protected form fields client-side before submission.
Install: add footer custom code and mark forms/fields with data attributes.
System plugin packaging the HKEY PHP core for use across Joomla extensions and forms.
Install: install/enable plugin, set salt/policy, call API in PHP.
Drupal 10/11 module with settings UI and hkey.encryptor service for webforms and fields.
Install: copy to modules/custom/hkey/, enable, configure at /admin/config/system/hkey.
HKEY encryptor model/service for checkout, customer data, and custom attributes.
Install: copy to app/code/Hkey/Encryption/, enable, setup:upgrade, cache flush.
Configurable module with HKEY core and admin settings for sealing sensitive shop data.
Install: copy/zip to modules/hkeyencryption/, install and configure.
Code-injection HKEY core for themes to encrypt protected form/member fields client-side.
Install: add script/injection in Ghost settings and mark protected fields.
hkey-hotkey-encryption)Functional TypeScript/Node package (source + build config) for apps, APIs, CLIs, and tooling.
Install: npm install (from package) / npm run build; or publish as hkey-hotkey-encryption.
hkey/hotkey-encryption)Functional PHP library with PSR-4 autoload for Laravel, Symfony, CMS extensions, and custom backends.
Install: composer require hkey/hotkey-encryption (when published) or install from package.
Use our drop-in SDKs (PHP, TypeScript, Python, Mojo) and the HKEY v1 spec to integrate gesture-based, authenticated encryption into any app or device workflow.
All integrations are reference implementations of HKEY v1. For best results, use strong unpredictable chord sequences, unique context salts, HTTPS, and secure secret handling. For production/regulated or high-risk environments, perform independent review and pair with audited standard AEAD and—where required—standardized post-quantum components. No solution guarantees absolute security.
Think of HKEY as a secret rhythm on your keyboard. You choose a short sequence of hotkey combinations and name the situation where it applies. HKEY blends them into a strong key and locks your data inside a sealed packet. If anyone changes even one bit of that packet, HKEY refuses to trust it.
Pick a few hotkey combos in order (for example Ctrl+Alt+H, Shift+K, Meta+E). HKEY normalizes them so the same gesture means the same thing everywhere.
Add a label like wp.payments.v1 or lab.station.3. This binds protection to a purpose, so the same chords produce different keys in different places.
HKEY stretches your sequence with PBKDF2-HMAC-SHA256 (210,000 rounds) into a 256-bit key, then derives separate encryption and integrity keys.
Your data is encrypted and authenticated (Encrypt-then-MAC). The result is a portable HKEY v1 packet that can be decrypted only with the same chords and context—and only if it has not been tampered with.
From everyday web apps to high-stakes operations, HKEY binds a human gesture to a specific context. Each example below shows where it fits, how it can be applied, and what you gain.
Where: SaaS admin panels, portals, customer dashboards.
How: Seal form fields, intent tokens, or local vault blobs with per-tenant salts before storage or transit.
Value: Reduces password reuse and detects tampering with authenticated packets.
Where: Proprietary algorithms, pre-release repos, contractor handoffs.
How: Encrypt modules, assets, or build secrets using project-scoped salts (e.g. repo.alpha.v1).
Value: Portable envelopes across toolchains with auditable digest labels.
Where: Release pipelines and production rollouts.
How: Unlock manifests or environment bundles at approval time with environment salts like prod:eu-west.
Value: Human-in-the-loop authorization bound to the exact environment.
Where: Microservices, partner APIs, admin endpoints.
How: Create short-lived authenticated payloads or envelopes derived from gesture material for high-trust actions.
Value: Strong domain separation and constant-time tag verification.
Where: Laptops, air-gapped workstations, field devices.
How: Protect credential stores, notes, or archives without typing long passphrases on risky keyboards.
Value: Mnemonic chords plus 210k-iteration stretching raise guessing cost.
Where: Sensors, gateways, embedded controllers.
How: Bind device-unique salts to technician chord rituals for provisioning or maintenance updates.
Value: Widely available hash/HMAC primitives fit diverse runtimes.
Where: Treasury desks, payment operations, audit workflows.
How: Seal high-value instructions with role-and-context salts to capture “how it was authorized.”
Value: Tamper-evident records that support controlled approval processes.
Where: Hospitals, labs, shared carts.
How: Use glove-friendly chord entry to protect station-bound notes or sample metadata.
Value: Fast, trainable rituals with clear separation by room, case, or department.
Where: Energy, water, transport control rooms.
How: Authenticate intent envelopes for setpoint changes or maintenance modes with console-specific salts.
Value: Adds a cryptographic human-authorization layer in segmented environments.
Where: Production lines, proprietary formulations, QA.
How: Encrypt recipe parameters or inspection results per line/shift salt.
Value: Limits leakage and misconfiguration across HMIs and back-office systems.
Where: Newsrooms, field reporting, evidence handling.
How: Seal drafts or bundles with shared gesture rituals and publication-context salts.
Value: Reduces reliance on memorable text passwords and detects tampering.
Where: eDiscovery, chain-of-custody, regulated filings.
How: Package exhibits or checklists into HKEY envelopes keyed by matter/case salts.
Value: Versioned packets and digest commitments aid auditability.
Where: Universities, certification labs, shared clusters.
How: Distribute encrypted kits or unlock tokens derived from instructor/proctor sequences per session.
Value: Teachable, accessible UX that is easy to rotate per cohort or experiment.
Where: Backup restoration and continuity runbooks.
How: Store recovery bundles unlockable by rehearsed multi-chord sequences scoped by site or incident salt.
Value: Drill-friendly access when normal credential systems are degraded.
Where: Deployed units, forward operations, contested networks.
How: Protect briefs, sensor snapshots, or store-and-forward messages with unit/mission salts and operator gestures.
Value: Low-dependency symmetric design, domain separation, authenticated envelopes, and a quantum-resilient key profile suited to long-term confidentiality goals.
Operational/defense use requires accredited implementations, hardware protections, doctrine, and independent review.
Where: Ground stations, mission control, delayed links.
How: Seal command parameters or telemetry archives with pass/mission salts for authenticated store-and-forward windows.
Value: Deterministic cross-language behavior and symmetric, post-quantum-aware confidentiality planning.
HKEY is engineered to protect website data against today’s AI-accelerated attacks and tomorrow’s quantum threats. Its v1 design uses symmetric, hash-based cryptography—PBKDF2-HMAC-SHA256 key stretching (210,000 rounds), HMAC-SHA256 keystream/tagging, and 256-bit derived keys—so there is no RSA/ECC math for Shor’s algorithm to break, and brute-force search faces a formidable quantum margin.
Bottom line: HKEY gives your website a practical, 1-click path to data that is resistant to AI-driven cracking and quantum interception threats—through strong symmetric 256-bit protection, high-cost key stretching, context separation, and authenticated, tamper-evident packets. No system can promise absolute or “unbreakable” security; real protection depends on secret strength, secure deployment, and (for regulated/high-risk use) independent review and standards-based hardening.
Read the SDK documentation right here on the site or download the packages you need. Every SDK implements the same HKEY v1 behavior so packets and keys stay interoperable.
PSR-style implementation using PHP hash_* APIs. Ideal for Laravel, WordPress, and server-side apps.
Node crypto implementation with timing-safe verification for services, CLIs, and tooling.
Clear reference using hashlib, hmac, and secrets—great for automation and testing.
Spec-aligned systems-oriented reference for high-performance and edge-focused workflows.
Want the exact rules for normalization, key derivation, and packet format? Read the full HKEY v1 specification.
Read the HKEY v1 specificationHKEY focuses on gesture-derived key UX, context separation, and portability. Mature standards like AES-GCM and ChaCha20-Poly1305 remain excellent defaults for many production systems. A powerful pattern is: HKEY-style derivation and workflow + a standard AEAD core + independent review.
| Dimension | HKEY v1 (this project) | AES-GCM | ChaCha20-Poly1305 | Password/KDF-only |
|---|---|---|---|---|
| Primary purpose | Hotkey-sequence derivation + authenticated packet envelope | Authenticated encryption (AEAD) | Authenticated encryption (AEAD) | Key derivation (not encryption alone) |
| Human input model | Native: ordered chord gestures + context salt | None (key required) | None (key required) | Usually text passwords/passphrases |
| Maturity & analysis | Reference design, not a ratified standard | Very high (NIST/SP 800-38D) | Very high (RFC 8439) | High for modern parameters |
| Quantum posture | Symmetric/hash-based 256-bit core: quantum-resilient profile (~128-bit effective under Grover) | 256-bit keys: quantum-resilient symmetric margin (key exchange around it may differ) | 256-bit keys: quantum-resilient symmetric margin | Depends on derived key use; KDF hardness still matters |
| Portability | High (SHA-256/HMAC/PBKDF2 widely available) | High, best with hardware/library support | High | High |
| Best fit | Gesture workflows, cross-domain use, interoperable envelopes | General-purpose AEAD at rest/in transit | AEAD with strong software performance | Password hardening and key storage |
HKEY v1 is a reference design for education, prototyping, and workflow exploration and is not a ratified standard. While HKEY’s symmetric, hash-based 256-bit core is designed to be resistant to AI-accelerated guessing and quantum interception/cracking threats, no solution can guarantee absolute security. Real protection depends on strong, unpredictable chord sequences, unique salts, HTTPS and secure endpoints, correct implementation, and sound operations. For regulated or high-risk deployments, seek independent cryptographic review and pair HKEY with audited, standardized AEAD primitives and—where required—standardized post-quantum algorithms for key exchange and signatures.