Concepts Overview

Understanding the core concepts behind Norrix will help you get the most out of the platform.

Key Concepts

Fingerprinting

How Norrix tracks native dependencies to ensure OTA update compatibility.

What gets fingerprinted
How fingerprints are computed
Runtime fingerprint files

OTA Compatibility

Rules for determining when OTA updates are safe vs when a store build is required.

What can be updated via OTA
What requires a store build
Compatibility checking flow

Pricing & Entitlements

How plans, usage limits, and metered billing work.

Plan comparison
Usage tracking
Overage billing

How Norrix Works

Build Flow


Local Project → Upload → Cloud Build → Artifacts → S3 Storage
                              ↓
                     Fingerprint computed
                              ↓
                   Build record created

Update Flow


Local Project → Compute fingerprint → Bundle JS → Upload → S3 Storage
                        ↓
              Compare with build fingerprint
                        ↓
              Update record created

Runtime Flow


App Launch → Check for updates → Compare fingerprints → Download if compatible
                                         ↓
                             If incompatible: requiresStoreUpdate

Architecture

Cloud Build System

Norrix uses GitHub Actions with WarpBuild for cloud builds:

macOS runners for iOS/visionOS
Linux runners for Android
Builds triggered via repository_dispatch

Storage

Artifacts: S3 with presigned URLs
Updates: S3 with presigned download URLs
Database: PostgreSQL via Prisma

API

Next.js API Routes: All endpoints
Authentication: AWS Cognito + API keys
Webhooks: HTTP callbacks with HMAC signatures

OTA Check API Fingerprinting