History · original March 2026 8Z Publish presentation (English)Zgodovina · izvirna predstavitev 8Z Publish iz marca 2026 (angleško)
Original wording is retained below as a dated historical record, including research proposals and commercial claims. It is not the current product specification or a verification of every earlier claim. “No server” describes standalone/password architecture. Today’s optional email access uses a server. Current capabilities and limits are stated above; deletion does not revoke copies already obtained, and claims about quantum safety, copy prevention or guaranteed leak attribution are not adopted here.Spodaj je ohranjeno izvirno besedilo kot datiran zgodovinski zapis, vključno z raziskovalnimi predlogi in komercialnimi trditvami. To ni današnja specifikacija izdelka ali potrditev vseh prejšnjih trditev. »No server« opisuje samostojno/geselno arhitekturo. Današnji opcijski email dostop uporablja strežnik. Aktualne zmožnosti in meje so navedene zgoraj; brisanje ne prekliče že pridobljenih kopij, trditve o kvantni varnosti, preprečitvi kopiranja ali zagotovljenem pripisu razkritij pa tukaj niso prevzete.
8Z Framework • A New Software Category
Sell anything.
No server.
No platform.
Just encryption.
8Z Publish lets you encrypt any HTML content — courses, tools, music, newsletters, AI agents — into a .8zv capsule. Host it anywhere for free. Customers decrypt with a passphrase. You keep 97% of revenue. No backend. No login system. No platform tax.
The Problem
The platform tax is a design flaw.
To sell digital content, you're told you need servers, databases, login systems, and a platform that takes 10–12% of everything you earn. That assumption is wrong.
💰
Revenue Cut
Substack, Gumroad, Patreon take 8–12% of your revenue. On top of payment processing. That's $800–$1,200 per $10K in sales — for hosting files.
🔒
Platform Lock-In
They own the customer relationship. They own the distribution. They change terms whenever they want. Your business runs on their infrastructure and their rules.
⚙
Infrastructure Burden
Self-hosting means servers, databases, session management, security patches, SSL certs, and $20+/month minimum. All to gate access to files.
🔥
Attack Surface
Every server is a target. Every database is a breach waiting to happen. Every login system is a password leak risk. Complexity creates vulnerability.
The 8Z Insight
If the content is encrypted and the passphrase is the only key, you don't need a server to protect it. You need good encryption and a browser that can decrypt. Both exist. The server was never necessary — it was a habit.
How It Works
Five steps. Zero servers.
The entire workflow runs on static files and browser crypto. No backend. No database. No login system.
1
Create
Build your content as HTML — a course, trading tool, music player, newsletter, portfolio. Any web content works.
2
Encrypt
Drop the file into 8Z Shield. Enter a passphrase. Download the .8zv file. Five seconds. No install required.
3
Upload
Host the .8zv on any free static host — Netlify, GitHub Pages, Cloudflare Pages, Vercel, S3. Cost: $0/month.
4
Sell
Create a Stripe Payment Link. Use Zapier to auto-deliver the passphrase on purchase. Customer opens the decoder page, enters passphrase, sees the content.
5
Revoke
Delete the .8zv from your host. The passphrase becomes useless. Instant, atomic revocation. No account suspension workflow needed.
Passphrase
→
SHA-256
→
XorShift64Star ×1024
→
SHA-256
→
PBKDF2 (10M)
→
AES-256-GCM
→
.8zv
Pricing
Keep 97% of what you earn.
Every other platform charges you for the privilege of hosting files behind a login page. 8Z Publish doesn't have a login page.
| Platform |
Revenue Cut |
Server Cost |
Owns Customer? |
Quantum Safe |
| Substack |
10% |
Their server |
Yes |
N/A |
| Gumroad |
10% |
Their server |
Yes |
N/A |
| Patreon |
8–12% |
Their server |
Yes |
N/A |
| WordPress + Plugin |
Stripe only |
$20+/mo |
No |
No |
| 8Z Publish |
2.9% (Stripe only) |
$0 (free hosting) |
No — you own it |
Yes (P=NP safe) |
The entire product is static HTML files. The "server" is any free host. The "database" is the filesystem. The "auth system" is AES-256 + a passphrase. Simplicity, pursued honestly, produces resilience that complexity never reaches.
The Bigger Picture
A new class of software object.
The industry offers an unsatisfying choice: distribute a weakly controlled file, or build a full SaaS application. That choice is too narrow. There's a middle layer that's been missing.
Plain Files
Cheap and simple. But once delivered: easy to copy, impossible to revoke, no personalization, no attribution.
Full SaaS
Powerful and trackable. But requires backends, accounts, billing, permissions, support, and ongoing ops.
The Thesis
An .8zv file is not just an encrypted file. It's a protected digital capsule — encrypted, personalizable, traceable, revocable, and offline-capable. It gives creators the control of SaaS without the operational burden. Many products are too valuable to give away as files and too small to justify full SaaS. Capsules fill that gap.
🔐
Encrypted
Content is ciphertext until an authorized passphrase unlocks it. At rest, in transit, everywhere.
👤
Personalizable
Each customer receives a distinct build with unique forensic fingerprints baked in.
🔍
Traceable
Multi-channel watermarking lets you attribute leaks to the exact source copy.
🔄
Revocable
Delete the file, passphrase dies. No account suspension workflow, no support tickets.
✂
Partial
Section-level encryption. Only the viewed content decrypts — the rest stays sealed.
⚡
Offline-First
Works without network. No server ping. No session. Just a browser and a passphrase.
The Roadmap: From Publish to Capsule OS
The category builds as a ladder, not a leap. Each stage adds a capability layer.
| Stage | Function | Status |
|---|
| Publish |
Whole-artifact encryption and static delivery |
✓ Live |
| Shield |
Section-level encryption, AI-assisted scanning, reduced plaintext surface |
✓ Live |
| Trace |
Per-recipient forensic fingerprinting, multi-channel watermarks, leak attribution |
Building |
| Capsule |
Multi-file apps, asset bundles, policy manifests, expiry controls |
Designed |
| Vault |
Long-lived recovery bundles, cold storage, inheritance workflows |
Planned |
| Studio |
Templates, issuance, analytics, distribution, marketplace |
Vision |
Use Cases
Encrypt anything. Sell anywhere.
Any content that can be an HTML file can be a product. The architecture is domain-agnostic — the bytes don't care what they represent.
Online Courses
Encrypt each module as a .8zv. Sell via Stripe. Deliver passphrase on payment. Students decrypt in browser. No LMS, no hosting costs, no piracy via URL sharing.
Trading Tools & Dashboards
Encrypt live trading scanners, calculators, paper traders. Already in production — the author uses this daily for SM and ZZ traders on chessbest.org.
Music & Audio
Encrypt HTML audio players with embedded tracks. Fans buy a passphrase, decrypt, listen. No streaming service, no 30% Apple cut, no takedown risk.
Premium Newsletters
Free tier on your blog, premium tier as .8zv. Replace Substack's 10% with Stripe's 2.9%. Own the customer relationship entirely.
AI Agents & Custom Personas
Package custom AI workflows, trading bots, therapy agents, or game NPCs as protected capsules. The entire agent bundle — UI, logic, prompts, knowledge — encrypted and monetizable.
B2B Partner Delivery
Pricing tools, distributor bundles, onboarding kits, sales enablement packages. Capsules replace heavyweight portals with recipient-specific protected packages.
Legal & Executive Handoff
Board materials, M&A review packs, audit documents. Time-bound, recipient-specific, and traceable — without spinning up a data room.
Private Family Content
Photo albums, family histories, personal journals, video memories. Encrypted and shared with a passphrase. No cloud service, no privacy policy, no account needed.
Cold Storage & Inheritance
Recovery kits, estate instructions, "open only if needed" bundles. Offline-survivable, long shelf life, no dependency on any service existing in 20 years.
Honest Security
What 8Z does — and what it doesn't claim.
The strongest version of this system doesn't need to overclaim. Clear boundaries build more trust than vague promises of invincibility.
What 8Z delivers
- AES-256-GCM encryption at rest and in transit — before unlock, content is indistinguishable from random noise
- Section-level decryption: only the viewed section enters the DOM, the rest stays sealed
- Per-customer forensic fingerprinting across multiple channels (ZWS steganography, synonym swaps, honey-links)
- Leak attribution with confidence scoring — identify the source copy when content surfaces
- Lightweight revocation: delete the file, revoke the access. No admin panel required
- Offline operation: no server ping, no session, no heartbeat. Just a browser and a passphrase
- 10M-iteration PBKDF2 + XorShift64Star Software PUF: brute-force costs measured in centuries, not hours
What no client-side system can do
- Guarantee perpetual secrecy after a legitimate user has viewed the content
- Prevent screenshots, screen recording, or manual retyping
- Replace all forms of server-side trust for every use case
- Provide perfect DRM in adversarial-client environments
- Beat hardened public API auth as a universal standard for mass consumer apps
- Prevent key sharing between users who trust each other
The Right Security Objective
The goal is not "make plaintext impossible forever." The goal is: minimize exposure surface, personalize every copy, attribute leaks forensically, and make revocation atomic and free. That's a real and achievable security posture — and it's stronger than what 95% of digital products have today.
Architecture
Three components. Zero dependencies.
The entire system is three things: an encryptor, a decoder, and encrypted files. All static. All portable. All permanent.
🔐
Encryptor
Browser-based or Python CLI. Gzip + AES-256-GCM with the 8Z key derivation pipeline. Produces .8zv files.
🔓
Decoder
5 KB self-contained HTML. Zero dependencies. Uses Web Crypto API. Wrong passphrase = blank page, no error oracle for attackers.
📦
.8zv Capsules
Encrypted content capsules. Host on any static server. Portable, permanent, platform-independent. One capsule per product or per customer.
Future Horizons
Where the architecture leads.
The same encryption pipeline that protects an HTML page can protect anything that's bytes. The system generalizes further than the current tools show.
GPU-Level Protection
Lazy decryption extended to GPU compute shaders — model weights encrypted in VRAM, decrypted only during inference, zeroed after each layer pass.
Capsule Format Standard
A recognized container format for controlled digital objects — as natural as .zip or .app, but with built-in encryption, policy manifests, and lifecycle hooks.
Peer-to-Peer Distribution
WebRTC swarms where encrypted capsules propagate without servers. The encryption makes the transport layer irrelevant — the content is self-protecting.
Domain Explosion
Medical records with consent-gated decryption. Military briefings on USB sticks. Family archives that survive 50 years without any service dependency. The same architecture, applied recursively.
Most existing solutions solve only one layer. File encryption solves protection. SaaS solves lifecycle. Static hosting solves delivery. Capsules combine enough of these layers to create a new operational model — software objects rich enough to sell as products, light enough to ship without becoming an operations company.
Companion Research
Four LLMs. One framework.
This paper synthesizes insights from four independent AI analyses of the 8Z framework. Each brought a distinct lens — read the originals for the full perspectives.
Get Started
Encrypt your first file in 30 seconds.
No install. No sign-up. No server. Open the browser encryptor, drop a file, enter a passphrase, download your .8zv.