Home (Overview) ANTRX (Sovereign Modules) CipherXOS (Web OS) Developer Portal Contact & Inquiries Privacy Policy → Terms of Service →
[ SOVEREIGN CLIENT-SIDE COMPUTING ]

Run compute on your users' devices.
Not on your cloud bill.

Cipherlook builds sovereign, local-first execution technology. Workloads run on the client, data stays under the user's control, and your infrastructure spend drops.

Book a Technical Demo →
Built on open web standards: WebAssembly • WebGPU • OPFS • Web Workers • WebCrypto
Sovereign Architecture: Code and data execute locally on hardware your user owns, reducing third-party cloud compute exposure.
FOR PRODUCT & ENGINEERING TEAMS

Cipher ANTRX

The sovereign client-side compute engine

54 modular APIs that move compute, storage, AI inference, auth, and media processing into the user's browser. Integrate with one SDK and cut backend load where it's heaviest.

  • ✓ Lower infrastructure cost on suitable workloads
  • ✓ User data stays on-device by default
  • ✓ Low-latency execution with no network round trip
Explore ANTRX →
FOR DEVELOPERS, TEAMS & INSTITUTIONS

CipherXOS

A desktop-grade OS and smart IDE, in a browser tab

A full multi-window workspace with a code editor, terminal, Python runtime, and encrypted local file system. Nothing to install and no server to provision. Built entirely on ANTRX, proving the engine in production.

  • ✓ Zero-install coding environment for classrooms and teams
  • ✓ Files stay on the user's device, encrypted
  • ✓ Free community edition, dedicated team plans
CIPHERXOS: THE LIVING PROOF

The proof is a full operating system running in your browser.

CipherXOS is a desktop-grade workstation with windows, a taskbar, a code editor, a terminal, a Python runtime, and an encrypted file system. All of it runs on the user's own hardware with no server compute for the workspace itself. If ANTRX can run this, it can run your product's workloads.

CipherXOS Sovereign Workstation • Client-Side WebAssembly Runtime
LIVE DESKTOP GUI
CipherXOS Operating System in Browser
Launch Live Interactive Demo →
Multi-Window Desktop GUI
Window snapping, dock taskbar, floating manager, and responsive window management on the client thread.
Monaco Code Studio
Monaco-based editor, the engine behind VS Code, running client-side with syntax parsing, Git diffs, and project trees.
Encrypted NVMe VFS Storage
Direct hardware file I/O using Origin Private File System (OPFS) with AES-GCM client-side encryption.
Local Nano Terminal & P2P Mesh
Shell execution, client WebAssembly tools, and WebRTC-based encrypted peer-to-peer file distribution.
Available Operating System Editions & Flexible Plans
Community Sandbox: Free Forever  |  Professional Developer: Dedicated Storage  |  Enterprise Teams: Multi-Seat & Priority Mesh
Explore OS Features → View Seat Pricing →
WHY CLIENT-SIDE

The server compute model was built for a world before modern client chips.

Every user connecting to your product is sitting behind a multi-gigahertz processor and a gigabyte-class browser sandbox. Traditional architectures ignore that and rent the same capacity back to you by the hour. Cipherlook moves the right workloads to where the hardware already is.

Lower Cost

Shift compute-heavy workloads off your servers and cut recurring cloud spend by up to 60–80% on suitable workloads.

Stronger Data Control

Sensitive data is processed locally on the client device, dramatically shrinking what you store, transmit, and expose in a breach.

Faster Experience

Execution happens directly on-device with no network round trip for local reads, transforms, and inference.

HOW IT WORKS

How ANTRX Works in 3 Steps

Integrate once. Delegate heavy compute to user hardware with automated cloud fallback.

STEP 01
Integrate the SDK

Add the lightweight ANTRX client runtime with a few lines of code. Configure permissions, OPFS storage budgets, and target modules.

STEP 02
Execute Locally

Sandboxed Web Workers run SQLite queries, code compilation, and image processing directly on the user's CPU and GPU, with no server round trip.

STEP 03
Sync Only What Matters

Transmit only finalized outputs and state diffs to your central server. If client hardware is constrained, ANTRX delegates back to cloud seamlessly.

FINOPS ECONOMICS

Where client-side execution changes your cloud bill

Cloud costs scale directly with your user count. Client-side costs mostly don't. The model below shows an illustrative scenario for a product with 100,000 active users.

Workload (100k Active Users) Traditional Cloud (est. monthly) With ANTRX Typical Reduction
User Code Execution & Sandboxes $40,000 / mo Runs on user device 70–90%
Media, Video & 3D Processing $12,000 / mo Runs in-browser 60–80%
Storage & Local Databases $8,000 / mo Local-first, optional sync 60–80%
Static Web Asset Delivery $2,000 / mo CDN cache (still required) ~0–30%
ESTIMATED BLENDED TOTAL ~$62,000 / mo ~$12,400 / mo (incl. license + orchestration) Up to 60–80%
*Illustrative model. Assumes 100,000 monthly active users, mixed compute workloads, and centralized cloud benchmark rates. Results vary by workload and device mix. Auth, licensing, optional sync, and CDN still require minimal server infrastructure. Blended estimate. Range reflects workload mix and device variability.
Request a Custom Workload Audit →
ARCHITECTURAL BOUNDARIES When ANTRX is NOT the right fit

Client-side sovereign execution cuts infrastructure spend dramatically, but it is not a silver bullet for every workload. We advise keeping these on your central servers:

1. Secrets & Tamper-Proof Logic
Payment processing, private API signing secrets, and entitlement checks must always remain on your backend authority.
2. Massive Multi-Gigabyte Models
Heavy 70B+ LLMs or multi-gigabyte training sets exceed client browser RAM limits and should run on central GPU clusters.
3. Legacy / Low-Spec Fleet Dominance
If your user base predominantly runs pre-2018 devices with single-core CPUs, heavy multi-threaded WASM should fall back to cloud.
* During our 30-Day Workload Pilot, our first deliverable is an honest workload-fit audit so you only move workloads where the numbers make sense.
[ CIPHER ANTRX: 54-MODULE SOVEREIGN SDK ]
UNIFIED CLIENT RUNTIME

One SDK. Fifty-four modules.
Start with the eight that matter most.

Each module runs on the client, so there's no compute backend to build or scale. Move your heaviest workloads to user hardware with one unified integration and reduce infrastructure costs on suitable workloads.

Core Flagships (Top 8 of 54 Modules):
AntrxSQL
OPFS PERSISTED
A real database, on the user's device
Embedded SQLite persisted to local storage. Millisecond reads with no query traffic hitting your servers.
AntrxCompute
WASM WORKERS
Serverless compute without the server
Run Python and WebAssembly workloads in multi-threaded workers, with no containers or VMs to manage.
AntrxAI
ON-DEVICE INFERENCE
On-device local inference
Speech-to-text and document OCR running locally via WebGPU, so audio and documents never leave the device.
AntrxAuth
FIDO2 / PASSKEYS
Passwordless, hardware-backed login
Passkey authentication using Face ID, Touch ID, or security keys with FIDO2/WebAuthn standard.
AntrxMedia
WEBCODECS
In-browser media pipeline
Image optimization, WebP conversion, and video processing on client, cutting transcoding costs.
AntrxRecord
LOCAL CAPTURE
Screen and meeting recording
Local HD capture and hardware encoding with no per-minute cloud recording fees or third-party storage.
AntrxHardware
WEBUSB / BLE
Direct device integration
Connect printers, scanners, and peripherals over WebUSB and Web Bluetooth with no local desktop agent.
AntrxCrypto
AES-256-GCM
Zero-knowledge encryption
Client-side AES-256-GCM encryption, so plaintext never reaches your servers. Helps reduce compliance surface.
View All 54 Modular APIs →
SECURITY ARCHITECTURE

Security & Data Control Architecture

Browser-enforced isolation designed for sensitive data and enterprise environments.

Sandboxed Workers
Every task runs in isolated Web Workers with no DOM access and strict origin boundaries.
AES-256-GCM at Rest
Client database and VFS storage can be encrypted at rest via WebCrypto standard APIs.
FIDO2 / Passkey Auth
No passwords or shared secrets stored on your servers. Public-key authentication backed by device hardware.
Server-Side Validation
Critical entitlement tokens and state transitions validate server-side; client handles compute, not authority.
FREQUENTLY ASKED QUESTIONS

Frequently Asked Engineering Questions

Direct, technical answers to common architectural and security inquiries.

Is ANTRX just WebAssembly in a wrapper?
No. WebAssembly is only the bytecode runtime. ANTRX provides a complete client-side execution runtime: persistent Origin Private File System (OPFS) drivers, SQLite query management, multithreaded worker hypervisors, client-side encryption, and automated graceful server fallback when device quotas are constrained.
What happens on low-end or constrained client devices?
ANTRX performs an instant capability benchmark on load (available hardware concurrency, memory heap, and WebGPU availability). If a device falls below configurable thresholds, jobs automatically route to standard cloud APIs with zero interruption to the user experience.
What happens if the user clears their browser cache or data?
For compute and rendering workloads, processing is ephemeral by nature. For persistent databases, ANTRX uses Origin Private File System (OPFS), which does not clear under routine cache purges. For mission-critical records, ANTRX provides background delta-sync to your backend storage.
Can malicious users tamper with client-side execution?
Client compute is designed for data transformation, document export, rendering, and fast local query indexing. Business authority, financial writes, and access tokens must always be validated on your backend server. ANTRX maintains strict separation: heavy processing runs on the client, trust authority remains on the server.
How does the 30-Day Workload Pilot work?
We collaborate with your engineering team to select a single high-spend workload (such as PDF generation, local SQL caching, or client sandboxes). We integrate in days and benchmark latency and actual cloud bill reduction side-by-side for 30 days with no upfront commitment.
[ BENCHMARKS ] METHODOLOGY PREVIEW
Reproducible FinOps Benchmarks

Comprehensive latency and cloud compute bill comparison across AWS, Cloudflare, and on-device execution.

[ ARCHITECTURE ] DOCS
Developer Documentation

Quickstarts for OPFS SQLite databases, multithreaded WASM workers, and zero-knowledge AES-256 client crypto.

[ LIVE DEMO ] INSTANT SANDBOX
Live Interactive Demo

Test the full multi-window OS live in your browser tab right now. No registration or credit card required.

[ 30-DAY WORKLOAD PILOT ]
Questions? Talk to an engineer, not a salesperson.

Start with one workload.
Prove the savings in 30 days.

Pick your heaviest client or backend bottleneck (PDF generation, data transforms, SQLite caching, or local AI). We integrate in days and benchmark real cloud reduction side-by-side.

Start a 30-Day Pilot → Talk to Engineering →
No upfront commitment • Written results report • Workload-fit assessment included