SEC01/ARRIVAL
MOTHERSHIP NOMINAL
10:52:03·
SHIP I OF THE FLEET — AN ANDROID-FIRST, HARDWARE-AWARE DEPLOYMENT LAYER FOR LOCAL AI
HANGAR 01
LOKIAI · WHAT IT IS

Deploy compatible AI workloads onto supported hardware.

LokiAI is an Android-first, hardware-aware deployment layer for local AI. It combines workload requirements with a device profile to identify, package, deploy, and validate a compatible model and runtime path.

LOCAL INFERENCE
HOW IT WORKS

After activation, supported workloads can run on the device without requiring a remote model API in every inference request path.

Provisioning, model retrieval, and optional management may use a network. Activated inference is designed to run locally. Android is the first proving ground — compatibility expands through measured evidence.

CAPABILITIES
WHAT IT CAN DO
07 CORE FEATURES
  • Wireless pairing

    Scan a QR code, the phone downloads and installs the app via browser, opens it, scans a second pairing QR, and the phone reports its own real hardware specs (RAM, CPU arch, storage, Android version) to register itself. No USB, no ADB at any point.

  • Natural-language model selection

    An AI assistant ("Loki") takes a request like "I want real-time object detection" or "give me an offline chatbot", searches HuggingFace for real candidate models, filters them down to what actually fits the paired phone's RAM budget, and explains the top picks in plain English — it will honestly say "nothing fits" rather than hallucinate a model that doesn't exist.

  • One-click wireless deployment

    Pick a model, hit Deploy, and the backend pushes a download instruction over WebSocket; the phone pulls the model file directly from the HuggingFace CDN itself. The backend never stores or touches the model file — only URLs.

  • Three on-device inference modes

    Camera (TFLite — live object detection/classification with on-screen labels), Chat (GGUF via llama.cpp — real token-by-token generation), Voice (TFLite audio — mic-based sound/speech classification).

  • Offline after deployment

    Once a supported model is on the device, the inference path is designed to run without internet access, verified in airplane mode during development. Activated inference does not require a remote model API per request.

  • Fleet dashboard

    See all your paired devices, their live specs and connection status, deployment history, and a chat panel for the assistant, all backed by real data (no mock/demo content anywhere).

  • Production-grade accounts

    Email/password signup with OTP verification, forgot/reset password, and hardened JWT auth with short-lived access tokens, httpOnly refresh cookies, rate limiting, and locked-down CORS.

COST MODEL
PRICING INTENT

LokiAI does not intend to charge per inference. Customers still carry hardware, power, storage, maintenance, and operational costs.

INFRASTRUCTURE
TECH STACK
ARCHITECTURE LAYERS
Backend
FastAPI (Python), asyncpg, python-jose (JWT), bcrypt, slowapi (rate limiting)
Database
PostgreSQL (Railway-hosted)
AI assistant
NVIDIA NIM API (Llama 3.1 8B/70B — a fast intent-classifier + a grounded JSON selector)
Model discovery
HuggingFace Hub API (search + metadata) — unauthenticated public API
Model delivery
HuggingFace CDN — phone downloads directly, backend never stores model files
Dashboard
Vite + React + TanStack Start/Router + TanStack Query + shadcn/ui + Tailwind
Mobile app
Flutter (Dart) — tflite_flutter for vision/audio inference, fllama (llama.cpp FFI) for chat, mobile_scanner for QR
Real-time
Native WebSocket (deployment push, download progress, heartbeats)
Email
Direct SMTP (OTP codes, password reset links)
TARGET AUDIENCE
WHO IT'S FOR
06 KEY PERSONAS
PERSONA 01

A maker or hobbyist who wants to turn a spare Android phone into a dedicated camera that labels objects, with zero ML or app-dev experience.

PERSONA 02

Someone who wants a private, local chatbot — no data leaving the device, useful when traveling or in low-connectivity areas.

PERSONA 03

Field or inspection use cases — detecting hazards or objects on-site where connectivity can't be relied on, and the phone needs to keep working once the model's on it.

PERSONA 04

A developer or researcher who wants to quickly try a HuggingFace model on real mobile hardware without writing a mobile app around it.

PERSONA 05

Anyone managing multiple phones each running a different on-device task, watched from one dashboard instead of juggling several devices by hand.

PERSONA 06

Accessibility use cases — local sound or speech classification running on-device.