Naia
Table of Contents
  1. 1Video Manual
  2. 2Naia OS Live USB
  3. 3Installation
  4. 3.1Naia OS Installation (ISO)
  5. 3.2Linux App Installation
  6. 4Getting Started
  7. 4.1Naia Model Pricing
  8. 4.2naia-0.9-omni-24g Realtime Multimodal Module
  9. 4.3Live Demo
  10. 4.4Naia Model Download
  11. 4.5Naia Model — Developer Guide
  12. 4.6Naia Model Online (planned)
  13. 5Main Screen
  14. 6Chat
  15. 7Conversation History
  16. 8Work Progress
  17. 9Skills
  18. 10Channels
  19. 11Agents
  20. 12Diagnostics
  21. 13Workspace
  22. 14Browser
  23. 15Panel Management
  24. 16Voice Chat
  25. 17Settings
  26. 18Tool Details
  27. 19Naia Account
  28. 20Troubleshooting
  29. 21Open Source Usage & Contribution

4.4. Naia Model Download

Naia is an open-source project built on "owning your own AI on your own computer." Instead of handing your conversations to a big-tech cloud, you download the model and run it directly on your own GPU. The model is not limited to Naia OS (the shell) — it's usable generally through an OpenAI-compatible API: any OpenAI SDK, tool, or app works by just changing the endpoint, and you can build new apps on top of it. A license to use the Naia model is offered to individual subscribers (enterprise / multi-seat → contact us), and is activated with a subscription key. Subscription fees go toward improving the Naia open-source project and running the service.

  • Ownership — the model lives on your device. It keeps working even with no internet during the subscription period.
  • Privacy — voice and conversations are processed locally and never leave your machine.
  • Flat rate — no per-token or hourly billing: $10 / month (individual). Revenue funds Naia open-source operation and improvement.
  • Free to use — not limited to naia-os (the shell). It exposes an OpenAI-compatible API, so any OpenAI SDK / tool / app connects by just changing the endpoint, and you can build new apps on top of it. (Developer details → 4.5 Model details (dev))
  • Safety — The model is powerful enough to be misused (e.g. for voice phishing), so we apply voice-watermarking technology for traceability, letting you use it with peace of mind.

The model you'll download is naia-0.9-omni-24g (multilingual real-time voice conversation). Try the 30-second free demo first. If you don't have a GPU, online use (4.6) is also planned once the GPU pool is expanded.

Recommended spec: one 24GB-VRAM GPU (RTX 3090 / 4090, etc.). Prerequisites: NVIDIA driver + podman (or docker) + nvidia-container-toolkit (CDI), ~30GB free disk.

Proceed right below — ① Download → ② Issue subscription key & run → ③ Release & reinstall (switch device).

1. Download

Public image — just pull it. (Licensing is enforced by the token in step 2, not by the download.)

podman pull ghcr.io/nextain/naia-0.9-omni-24g:latest
2. Issue subscription key & run

One click issues a token and builds the run command with it. Please log in first.

Log in

On boot the container uses this token for subscription check + activating this device + decryption (active subscription only). Validity = subscription period, 1 subscription = 1 active device.

First boot takes a few minutes (model loading). Check readiness:

curl -s http://127.0.0.1:8892/health

Active device

None yet. Activates automatically when the container connects with the token above.

Restart / pause (same device)

To briefly stop/start on the SAME device, the command below is enough — the cert persists in the volume, so it reboots offline (no gateway) as the same device (no re-issue, no 409). Don't use step 3 (release) unless you're switching devices or ending the subscription.

podman restart naia-omni

First boot/restart takes a few minutes (model loading) — wait until the health check (step 2) shows ready:true. Connection failures (refused/1006) before that are normal.

3. Release & reinstall (switch device)

To switch devices or reinstall, run the command below — (1) release inside the container (reported to the server, active device freed), (2) remove the container, (3) remove the license volume (clears the released marker = reinstall-ready). Then issue & run again with a new subscription key in step 2.

If you delete the container without releasing (or lose the device), the server's active device is not freed, so new activation is blocked until the subscription period ends (auto-freed at expiry). Release only frees the active-device slot — to finish switching, run step 2 (issue & run) again on the new device.

podman exec naia-omni bash /app/release.sh
podman rm -f naia-omni
podman volume rm naia-omni-license

Connect from naia-os (or any app)

Point naia-os's gateway/backend URL at the running container. Give just the base URL — the path (/v1/realtime) and default model are applied automatically:

  • Same PC: ws://127.0.0.1:8892
  • Another device (Tailscale, below): ws://<tailscale-ip>:8892
  • The explicit form also works: ws://<host>:8892/v1/realtime?model=naia-0.9-omni-24g

The subscription key is used only once, at run time (activation) — for the subscription check and license issuance. Once activated, the container self-verifies the license locally, so clients like naia-os just need to connect to the URL above (127.0.0.1 on the same PC, Tailscale from another device). There is no separate connection key. (If exposing remotely, put a VPN/tunnel in front.)

To use it from code (OpenAI-compatible chat / TTS / STT / embeddings / realtime API) → see 4.5 Model details (dev).

Remote access — Tailscale (recommended)

The easiest way to securely reach your home GPU from naia-os on another laptop/phone:

  1. Install Tailscale on both devices and sign in with the same account.
  2. Find the GPU PC's Tailscale IP: tailscale ip -4 → e.g. 100.x.x.x.
  3. Set naia-os's gateway URL to ws://100.x.x.x:8892/v1/realtime?model=naia-0.9-omni-24g.

Both are on the same private overlay network, so no port forwarding or public IP is needed, and traffic is automatically encrypted. Works from home or away.

Other remote options (alternatives)

MethodNotes
WireGuardSelf-hosted VPN. The manual version of Tailscale (exchange keys yourself).
Cloudflare Tunnel (cloudflared)Public domain + automatic TLS, no port forwarding.
SSH tunnelssh -L 8892:127.0.0.1:8892 user@gpu-pc — 1:1, simple.
Same LANInside your router, just ws://<lan-ip>:8892.
ngrok / frpTemporary public tunnel (demos/tests).

The wrapper is plain ws. When exposing it to a public network, always put a tunnel/VPN's TLS + auth in front. Tailscale / WireGuard / SSH are encrypted by themselves.

License details

  • Validity = subscription period — the license is valid for the subscription period. It runs offline during that period; internet is only needed at renewal. When it expires the container shuts down automatically — renew and reactivate (step 2) to keep using it.
  • 1 subscription = 1 active device — only one device is active at a time, and while a device is active you cannot issue a new subscription key (normally just one key).
  • Switch device = release (step 3 above) + reactivate on the new device — releasing in the old device's container is reported to the server automatically and frees the active device. Then issue & run again on the new device (step 2). Release alone only frees the slot.
  • Deleting the container without releasing does NOT free the active device — if you remove the container with podman rm (or lose the device), the release isn't reported to the server, so the active device stays and new activation is blocked until the subscription period ends (auto-freed at expiry). Always run the step-3 release before deleting the container.
  • Stop auto-renewal (web) — disabling a subscription key's renewal on the web doesn't void it immediately; it stops renewing, so the active device falls off at the subscription period end (no re-issue until then). To free the active device now, use the container release. Use only if the key leaked.
  • An individual subscription may be used to monetize your own creative work (e.g. VTubing). Enterprise / multi-seat / kiosk / exhibition / resale / product embedding are by separate agreement.
  • Generated audio carries an identifying watermark — the output speech embeds a traceable identifying signal, so misuse such as impersonation, non-consensual voice synthesis, deepfakes or fraud can be traced back to its source. Such illegal or deceptive use is prohibited and may result in subscription termination and legal liability.

Upcoming models

  • naia-0.9-coding-24g (24GB, coding/agents) — planned
  • naia-0.9-omni-48g (48GB, larger omni) — planned
  • Naia-OS bundled extension — planned as an offline extension that drops straight into the naia-os app. It will auto-detect your GPU, pick the matching model (tier), download and install it in one step (no command line).

All will be offered under the same $10 / month subscription (individual). B2B adoption by separate agreement.