OZero Security — Now Available

Add Anti-Cheat × Anti-Piracy in minutesUnity Native C++ SDK

Combine Anti-Cheat × Anti-Piracy into one layer
MOD APK redistribution, SpeedHack, memory tampering, Injection, build tampering, save tampering, and Steam bypass launches
then detect and respond to those major threats through policy. A commercial Unity security SDK built around Native protection for Android · iOS · Windows · macOS · Linux · Steam, with limited WebGL protection.

Features View Manual Tech Proof
Standard $129 · permanent license · expand with Plus/Pro Add-ons
If Plus/Pro expires, shipped apps keep running quietly under Standard protection.

Zero-Config Integration

Install and configure in under 3 minutes

Import the package, open OZero Security > Config & Dashboard from the Unity editor menu, toggle the modules you need, and save the asset. No scene hierarchy management or manual component placement required.

  • Automates global threat response (force quit, logging, etc.)
  • Auto-creates all enabled modules as DontDestroyOnLoad GameObjects at runtime startup — before any scene loads, no manual placement needed
  • Detailed developer-friendly comments in all functions and classes
  • build-setting protection, runtime validation, and a Native C++ guard layer work together after release
  • 4-path defence: built-in handler / user receiver / internal fallback / native abort run independently — patching any one still leaves three armed
  • One-click Low / Standard / Strict presets — each preset now applies genuinely distinct thresholds and toggles across every module
Full Installation Guide
OZero Security Config & Dashboard
Security Modules
Build Integrity Validator
Speed Hack Detector
Injection Detector
Physics Hack Detector
Status: Active on [OZeroBuildIntegrityValidator]
✓ All enabled modules auto-created at runtime

Multi-platform Unity support: Android, iOS, Windows, WebGL, Unity Editor, Steam

iOS 12.0+
Android API 21+
Windows Standalone
macOS Limited
Linux IL2CPP/Mono
Steam Anti-Piracy
Dedicated Server Windows/Linux
WebGL Runtime
Unity 2020.3 LTS+
10
Security Modules
0
GC Allocation
C++
Native Engine
9+
Platforms

Quick View

Jump straight to the sections you need

Intro Demo Features Validation License FAQ

Layered runtime protection

From launch to live play, multiple layers validate together

OZero combines build integrity, runtime configuration, native protection, and operations telemetry. Developers can apply consistent detection and response policies without writing complex security code themselves.

1

Build trust baseline

Signed release baselines help verify that the player is running the intended build configuration.

Signed build baseline
2

Build integrity

Checks release files and runtime environment signals to reduce use of modified builds.

Build integrity
3

Automatic initialization

Enabled modules are prepared at runtime without placing security objects in every scene.

Zero scene setup
4

Native C++ guard layer

Native protection assists runtime validation outside the managed code layer.

Native runtime guard
Why layered protection?

A single check is rarely enough for live operations. OZero separates build, runtime, memory, and server telemetry observations to improve both defensive quality and operational visibility.

Build integrity event Runtime threat event Operations telemetry
Verification order
Trust Anchor →
Manifest Validator →
Bootstrapper →
Native Guard

Layered Security Coverage

10 security modules — running on a self-verifying boot chain

Detect the major paths of game hacking across multiple layers and respond through configurable policy.

Build Integrity Validator

Detects tampering with major DLLs and data files.
C++ native integrity cross-validation raises the cost of modified builds and MOD APK redistribution.

Install Source Validator

Verifies if the app was installed via authorized stores like Google Play. Prevents sideloading through black markets or APK sharing.

Device Binding

Extracts unique hardware fingerprints to bind save data to the device. Prevents copying and sharing save files across devices.

Speed & Time Hack Prevention

Multi-thread timer and web timestamp cross-validation instantly detects TimeScale manipulation and system clock tampering.

Multi-endpoint round-robin · no public time-server dependency

Physics Engine Hack Prevention

Precise distance algorithms compensating for network latency block abnormal movement (teleport) and wall hacks.

Memory Injection Detection

Observes abnormal runtime modules, hook indicators, and suspicious execution states, then responds with telemetry or blocking based on policy.

Memory Tampering Prevention (Secure Types)

Protects core values such as HP, gold, and speed through Native C++ Secure Types while keeping most gameplay logic unchanged.

Local File Encryption (Secure File)

Fast and secure encryption/decryption of save data and important asset files. Uses device-unique authentication keys.

PlayerPrefs Security

Replaces Unity's default PlayerPrefs. Obfuscates and encrypts both keys and values to prevent data theft via registry dumps.

Steam Guard / Anti-Piracy

Checks Steam App ID, launch path, ownership/DLC, Build ID, and release steam_appid.txt hygiene to detect non-Steam launches and known emulator traces. Server-side ownership verification is available in Pro.

Live Demos

Watch Real Hacking Tools Being Stopped

Real hacking tools vs OZero Security — watch each security module block real attacks live.

Click to Play Demo
🔐Secure Types
vs Cheat Engine
▶ Play

Cheat Engine Scan: 0 Results

Attempting to find in-game Gold and HP values with Cheat Engine — comparing before and after OZero in real time.

Click to Play Demo
⚡Speed Hack Detector | Android
vs Speed Hack App
▶ Play

Speed Hack Detection (Android)

The moment a speed hack app triples the game speed, OZero's 3-layer native detection system fires immediately.

Click to Play Demo
🛡️Injection Detector
vs Frida
▶ Play

Runtime Injection Signal: Policy Response

OZero detects abnormal runtime injection signals and responds with telemetry or blocking according to your configured security policy.

Click to Play Demo
🛡️Injection Detector
vs CE Debugger
▶ Play

Cheat Engine Debugger: Injection Blocked

A process injection attempt via Cheat Engine's debugger feature — instantly detected and blocked by OZero's injection monitor.

Click to Play Demo
💾Save File Protection
vs Hex Editor
▶ Play

Save File: Tamper-Proof

When HxD hex editor directly modifies a save file, message authentication verification instantly detects the tampering.

Click to Play Demo
📱Device Binding
vs Save Copy
▶ Play

Save Copy: Cryptographically Blocked

Copying a save file to another device is immediately invalidated by key-derivation function device binding.

Click to Play Demo
⚡Speed Hack Detector | Windows
vs Speed Hack App
▶ Play

Speed Hack Detection (Windows)

On Windows Standalone, the moment a speed hack app is launched, OZero's multi-thread timer cross-validation fires instantly.

Why Native C++?

Native C++ Protection: Proven in Practice

See the structural difference proved by memory scan simulation — what C# alone cannot protect against.

Legacy C# (Vulnerable)

Algorithm Exposed in Source Code

C# security solutions embed the protection algorithm directly inside the C# code. Because C# can be decompiled using free tools, an attacker can read the algorithm, understand how it works, and reverse the encryption in minutes.

AddressDecimalComment
1B101765E18   1101936768   // CryptoKey
1B101765E1C   1101936202   // HiddenValue
1B101765E20   3786         // FakeValue
> Hacker XOR: 1101936768 ^ 1101936202 = 3786
> Full bypass achieved in under 1 minute.
OZero Security (Stronger Defense)

Native C++ Zero-GC Masking

OZero Security never stores raw values in C# managed memory. All data lives exclusively in native C++ heap, encrypted with per-instance dedicated encryption keys. The token returned to C# shifts every frame — making memory scanners return 0 results by design.

AddressHexComment
7FF76397A0C0   ?? ?? ?? ??   // Native C++ heap — inaccessible from managed memory
7FF76397A0C4   ?? ?? ?? ??   // Key and ciphertext separated in memory
7FF76397A0C8   ?? ?? ?? ??   // Token rotated every frame
> Cheat Engine scan attempt...
> Result: 0 Results Found. Scan and reverse-engineering blocked.

C# Heap-Free

Raw values never enter managed memory. IL2CPP or Mono — the data stays native.

Per-Instance OZero proprietary cipher

Each variable gets its own encryption key. Cracking one reveals nothing about others.

Dynamic Frame Masking

The C#-side token changes every frame. Static memory scanners see a constantly shifting target.

Zero-GC Performance

No heap allocations during encrypt/decrypt. Security that doesn't tax your frame budget.

Core Differentiators — Boot Chain & Key Operations

Pinned
4-path violation response — 1 fails, 3 still work
Default handler · user Receiver · Internal Fallback · native Abort run independently. If any one is patched, the other 3 paths remain alive — security response is preserved.
Pinned
Encrypted build Config
Security config is encrypted at build with OZero proprietary encryption and shipped as oz_cfg.bin. Plaintext config is never exposed to players.
Pinned
Native protection & zero scene placement
Core runtime checks work with the Native C++ layer. All modules are auto-spawned at runtime startup — no scene placement.
Zero-GC, Zero Performance Cost
Atomic counter nonce generation, shared buffer pooling, and stackalloc mean zero GC allocations even at 60,000+ encryptions per frame.
License-Free Encryption
Cryptographic primitives implemented fully independently. No OpenSSL dependency.
Transparent Inspector Integration
Custom PropertyDrawers render OZeroSV_Int and OZeroSV_Float identically to standard fields.

Why OZero

Compared line-by-line against other security-solution categories

Without targeting any specific product, this summarizes what each category of security SDK guarantees — and what it does not. Every row is verifiable against OZero's code and manual.

Criterion OZero Security Memory-protection-focused SDKs Server-side anti-cheat services
Self-verifying boot chain (4 stages) ✓Layered validation combining Trust Anchor, Manifest, Bootstrapper, and Native Guard ✗Disable a single entry point and the whole thing falls ~Server-side verification only; no client boot-time self-check
Native runtime response ✓Runtime threat response assisted by a layer outside managed code ✗Primarily depends on managed-code callbacks ✗Server verdict first; local client response requires separate setup
Per-variable keyed memory encryption ✓Native C++ memory + per-variable key + Zero-GC ~Mostly XOR/masking, shared key, GC allocations possible ✗Client memory protection is out of scope
Build integrity signature verification ✓OZero authenticated signature signatures ~Checksum-based, weak key separation ✓Server-side verification possible, but requires network
Dual-fingerprint zero-downtime key rotation ✓Expected + Previous fingerprints both accepted — no forced update ✗Single fixed key — rotation requires forced update for all users ~Server-side rotation possible, requires client cooperation
Time-tampering defense (multi-endpoint) ✓Multiple webTime endpoints — round-robin + quorum (majority) verification ~Single time-server dependency ✓Server clock authoritative; client cannot verify alone
No public time-server dependency ✓Register your own webTime endpoints freely — zero external dependency ✗Public time-server hardcoded ~Uses your server clock, but you bear the operating cost
Hooking-tool detection (Frida etc.) ✓Native memory scan + C# layer cross-checks ~C#-level detection only; native hooks undetected ✗Hook detection is out of scope
iOS build-time guard ✓BuildFailedException blocks the build if the iOS native bridge is missing ✗Manual check required; no build-time guard N/A
Server infrastructure dependency ✓Offline-capable — all verification runs on the client ✓Standalone-capable ✗Server/network required — not viable for offline games
Pricing model ✓$129 perpetual (Standard) / $399/year (Plus Add-on) / $1,499/year or $399 first month then $149/month (Pro Add-on) ~Per-asset pricing varies; major-version upgrades may require repurchase ✗Monthly subscription or MAU-based metered pricing
Server telemetry (optional) ✓Pro tier: OZA Attestation · Cloud Telemetry · Auto-block ✗Not supported ✓Required — cannot operate without server connection
Serverless mode ✓Fully serverless on Standard tier — no key, zero external dependencies ✓Standalone-capable ✗Not supported — server/network required

This comparison reflects the typical implementation patterns of each category and does not target any specific product. ✓ meets / ~ partial / ✗ does not meet, or out of category.

Live Ops

5 operations tools for after launch

An SDK isn't only needed on launch day. Key rotation, post-mortem analysis, time verification, build guarding, and cloud telemetry (optional) — the tools live ops actually relies on.

Key Rotation

Dual-fingerprint key rotation

Expected + Previous key fingerprints enable zero-downtime key rotation. Old and new builds coexist on the same server without branching — no forced update required.

Reason Codes

Reason codes for post-mortem analysis

Telemetry includes module, layer, risk score, and event state so operations teams can classify patterns and track trends.

Multi-endpoint Webtime

Multi-endpoint time verification

Multiple webTime endpoints called in round-robin; only the quorum (majority) result is trusted. Verification keeps running if one endpoint goes down, with no public time-server dependency.

iOS Build Guard

iOS build-time guard

If the iOS native bridge is missing, BuildFailedException blocks the build. The accident of shipping an unprotected build to the App Store is caught at build time.

Cloud Telemetry

Cloud Telemetry (Optional)

Enabled from the Pro tier — violation events aggregate on the server so you can analyse abort-code distribution, device distribution, and violation trends. If the server goes down, graceful degradation keeps core security fully alive.

Key Rotation

Zero-downtime Server Key Rotation (Pro)

Pro-tier feature — the SDK trusts an Ed25519 signing keypair through an active + previous dual-key model. Operators trigger a rotation from the customer portal's Server Keys page, run a grace window, then explicitly retire the old kid — no forced SDK update required.

Operating modes

Serverless vs server-bound — both fully supported

Standard completes client-side protection with no server. Plus blocks attack reuse with per-customer Native Variants, and Pro adds server attestation, telemetry, and auto-block to harden live-service operations.

Serverless mode (A)

Rock-solid client SDK

All verification completes on the client. Zero external infrastructure dependency.

  • ✓10 security modules + 4-stage self-verifying boot chain
  • ✓Secure value protection + Native C++ runtime guard
  • ✓Offline license — no key, no server activation
  • ✓Multi-endpoint webTime with quorum (majority-vote) verification

Recommended use cases

  • · Offline / single-player titles
  • · Teams that don't want to run server infrastructure
  • · Projects built in air-gapped corporate environments

→ Standard tier covers this fully

Server-side security (Pro)

Server verification + operations alerts + automatic blocking

Everything in Plus, plus server verification, an operations dashboard, real-time alerts, and automatic threat-blocking policies.
Respond to tampered builds, repeat-risk devices, and risky-country traffic through live operations policy.

  • +Includes everything in Plus
  • +Stronger security — Build Integrity + Steam Guard server verification
  • +Operations dashboard & alerts — telemetry, Discord alerts, blocking reports
  • +Automatic blocking — policy blocks, Variant blocks, vulnerable-version blocks, edge country blocks

Recommended use cases

  • · Live games / IAP / leaderboards
  • · Operations that need violation-pattern analysis & post-mortem monitoring
  • · Teams that need automatic blocking, stronger security, and the customer portal

→ Pro tier

Plus — Native Variant Isolation

A different binary per customer game, rebuilt on every release

OZero Plus/Pro doesn't ship one shared security binary to every customer. It defends along two axes — distribution (space) and renewal (time) — so an attack analyzed on one game can't be reused as-is against another target or the next version.

Distribution — spatial defense

Binaries are distributed from a carefully engineered pool of native Variants. This structurally lowers the chance that a bypass or auto-patch technique found on one game can be reused as-is against another target.

Renewal — temporal defense

Every regular SDK update rebuilds and refreshes the native Variants. The defense surface shifts before analysis is complete, so even a bypass that worked once is quickly neutralized.

Pro Operations

Pro connects server verification, alerts, and automatic blocking

OZA attestation verifies build and Steam evidence on the server side, while the dashboard and Discord alerts make risk visible. Teams with a game server can validate tokens directly, while teams without one can delegate allow/warn/block decisions to OZero Managed Verification.

OZA Attestation

Your game server or OZero Managed Verification checks the token for tampered builds, Steam ownership, and blocked-build state.

Automatic blocking

Block repeat-risk devices, blocked Variants, vulnerable build versions, and risky-country traffic through server and OZero edge policy.

Risk Score / Audit

Aggregate threat events by module, platform, SDK version, and device, then keep the evidence operators need.

Remote config

Override key SpeedHack and Injection parameters per license.

Graceful degradation guaranteed — gameplay never stops when the server goes down

Server maintenance, network failure, and expired/suspended/revoked licenses quietly downgrade Pro features to the Standard/serverless path instead of closing the game. Confirmed security states such as build tampering, blocked builds, injection/hooking, or debugger detection follow the configured threat-response policy. The client cache is protected with a device-bound key and uses a default 7-day TTL.

Pro telemetry dashboard preview

OZero Pro telemetry dashboard preview
OZero Pro remote configuration preview

Remote config

Adjust detection strength and policy refresh cadence per license, then apply it on the next client config sync.

OZero Pro telemetry dashboard analytics preview

Dashboard analytics

Review events, platforms, SDK versions, and risk scores in one place to track attack patterns after launch.

OZero Pro device blocking preview

Device blocking

Block repeat-risk devices through server policy and apply the decision on relaunch or device policy heartbeat.

OZero Pro injection whitelist preview

Injection whitelist

Register reviewed modules by hash and signer while keeping suspicious modules visible for operator follow-up.

Protection model

OZero Standard vs Pro

Standard starts fast with local protection, while Pro adds server verification and operational control for live-service response.

Comparison item Serverless mode (Standard) Server-bound mode (Pro)
10 core security modules ✓Fully supported ✓Fully supported (identical)
External infrastructure ✓None ~Cloudflare Workers + D1 + KV
Cloud Telemetry ✗Not available ✓Available (graceful degradation)
Signed Time ✓Local time + multi-endpoint webTime quorum ✓Server-signed timestamps + quorum verification
Automatic blocking policy ✗Not available ✓Policy blocks, Variant blocks, vulnerable-version blocks, and edge country blocks managed server-side
Server keys / policy operations N/A ✓Server key rotation, blocking policy, customer portal management
Operations overhead No separate server to operate OZero provides the server features — no infrastructure for you to build.
Recommended pricing tier $129 (Standard · perpetual)
$399/year (Plus Add-on · app-specific Native Variant) - Standard required		 $1,499/year or $399 first month then $149/month (Pro Add-on) - Standard required

Deployment and validation cases

Validation cases after integrating OZeroSecurity

These cards summarize observable outcomes after protection was applied: delayed MOD APK updates, runtime coverage by platform, and clear protection boundaries.

Real-World Signal

A public MOD APK update flow was delayed after repeated releases

After protection was applied, an Android MOD maintained by a high-activity maintainer in a public MOD APK community was not immediately updated in a stable form. User crash and abort reports were observed, and the update flow was interrupted or delayed.

Verified Runtime Coverage

Field-tested around Windows, Android, iOS, macOS, and Linux

Windows IL2CPP and Android are the strongest primary protection targets. Runtime validation has also been completed on iOS, macOS, and Linux around Build Integrity, Injection, SpeedHack, and MemoryHack flows.

Clear Boundaries

Platform protection scope, without exaggeration

WebGL runs in a browser environment where the Native C++ security logic cannot operate, so it should be treated as limited protection with simple runtime checks and integrity hints.

3 Tiers · Scale by project needs

Pick the license that fits your project size and operations model

Standard is a perpetual license. Plus/Pro are Add-ons for projects with an active Standard license. Plus is annual-only, while Pro supports monthly or annual billing. Pro separates the 10K Telemetry Analysis Cap from the 100K MUAD scope for one project. If a project exceeds that scope or needs expansion, we review a Business or Enterprise plan change separately.

SERVERLESS · PERPETUAL

Standard

Serverless client SDK

All 10 security modules included

$129 / lifetime

One-time payment · perpetual license

A perpetual license. Use every local security module immediately after package import, with no added subscription.

All 10 security modules + fully serverless operation. No license key, no server activation.

Serverless Ownership

The baseline protection layer that runs inside your project without external server dependency.

  • ✓All 10 security modules (Build / Speed / Inject / Device / Source / Physics / Memory / File / PlayerPrefs / Steam Guard)
  • ✓No license key — activated by package import alone
  • ✓Offline standalone — zero external dependencies
  • ✓Unlimited projects (Unity Asset Store standard terms)
  • ✓Free updates within the current major version
  • ·Server features (Attestation / Cloud Telemetry / Auto-block) NOT included
Buy on Asset Store

Recommended: offline / single-player titles

BEST STEP-UP
SERVERLESS · APP VARIANT ADD-ON

Plus

App-specific Native Variant protection

Add-on for Standard-licensed projects

$399 / year

one project · Standard add-on price (+$129 lifetime if not owned) · annual billing only · active Variant delivery · quiet downgrade to Standard on expiry

Adds a different Native Variant for each customer app. An attack analyzed against one game cannot be reused against another customer game as-is. If a Mod APK appears, rotating the Variant can invalidate the existing bypass patch.

Variant Isolation

Separates games so a bypass patch built for one game does not work against another as-is.

  • ✓Everything in Standard
  • +Different native binary per customer game
  • +Separates games so one bypass patch does not work across other games
  • +Up to 5 Variant build rotations every 30 days
  • +Neutralize an exposed Mod APK by applying a fresh Variant
  • +Apply Plus Variant without changing existing Standard code
  • +Unlimited latest-version updates while the license is active
  • +After license expiry, shipped apps quietly downgrade to Standard
  • ·Cloud Telemetry / Remote Config / server Attestation NOT included
Prepare Plus annual checkout

Recommended: indie and mid-sized games that need ModAPK reuse resistance

Server-bound · operations Add-on

Pro

Server-bound for live ops

Add-on for Standard-licensed projects

$1,499 / year

Setup fee waived

one project · Standard add-on price (+$129 lifetime if not owned) · 10K Telemetry Analysis Cap · 100K MUAD · $1,499/year or $399 first month + $149/month after · quiet downgrade to Standard on expiry

Annual billing waives the setup fee and saves $539 compared with monthly billing for one year. It is the strongest choice for long-term live operations.

Pro is scoped to one project and includes everything in Plus, plus stronger server verification, an operations dashboard, real-time alerts, and automatic blocking policies. The default scope is a 10K Telemetry Analysis Cap and 100K MUAD. If a project exceeds that scope or needs expansion, we review a Business or Enterprise plan change separately.

Stronger Security

Build Integrity and Steam Guard are verified again on the server side.

OZA attestation adds a server-side layer to local checks, connecting tampered builds, Steam bypass launches, and blocked build states to your game server or OZero Managed Verification policy.

  • ✓Everything in Plus
  • +Stronger security — Build Integrity + Steam Guard server verification
  • +Operations dashboard — telemetry analysis, security events, device and build status
  • +Alert system — Discord real-time alerts and blocking reports
  • +Automatic blocking — policy blocks, Variant blocks, vulnerable-version blocks, edge country blocks
  • +After license expiry, shipped apps quietly downgrade to Standard
Prepare Pro checkout View Pro portal demo

Recommended: live games / IAP / multiplayer

Low-friction purchase

Enter only company name, project name, Bundle ID, and confirm Standard ownership during checkout.

Selective verification

Proof of purchase is not required by default. We may request Standard entitlement confirmation only when needed.

Annual value

Plus is annual-only. Pro annual billing waives the setup fee and saves $539 compared with monthly billing for one year, making it the best value for long-term operations.

Security modules included across all 3 tiers

Secure Types (Memory Encryption) Speed Hack Detector (5-Layer) Injection Detector (Frida, DLL) Build Integrity Validator Device Binding Install Source Validator Physics Engine Hack Prevention Secure File (Local Encryption) Safe PlayerPrefs Steam Guard / Anti-Piracy

Core local security modules are included in all 3 tiers. Plus/Pro are Add-ons for projects with an active Standard license. The purchase flow starts with company name, project name, Bundle ID, and a Standard ownership checkbox. Proof of purchase is requested only when needed, and when the active period ends, shipped apps gracefully downgrade to Standard protection.

🔑
Permanent Ownership
Standard protection remains available. If the Plus/Pro active period ends, the app keeps running quietly under Standard protection.
📦
Latest Updates While Active
Plus/Pro receive latest-version updates while the license is active, regardless of major version changes.
🛒
Project-Based Growth
Start lightweight with Standard, then expand with app-specific Variants and server operations in Plus/Pro.

Frequently Asked Questions

Everything you need to know before buying.