anz33 docs
Download

Sharing with your household

One computer in the house can run the models for everyone. Profiles let each person have their own settings — including a kid-safe mode and a local-only mode — without running six copies of anything.

Making profiles

anz33 profile add dad
anz33 profile add maya --kid-safe
anz33 profile add work --local-only
anz33 profile list
anz33 profile remove work
--kid-safeA stricter setup for a child's device.
--local-onlyThis profile never reaches a cloud engine, whatever the household setting is.

anz33 profile list shows each profile with its key. The key is what a device uses to say who it is.

Sharing over your home network

By default the router answers only its own computer. To let other devices use it:

anz33 serve --lan

Then, on the phone or laptop, point the app at http://<the-computer's-IP>:3300/v1. Find that address with ipconfig on Windows or ifconfig | grep inet on macOS and Linux; it usually looks like 192.168.1.42.

Turn on keys before you turn on the network. With --lan, anything on your Wi-Fi can reach the router — including a guest's phone and anything else connected to it. Requiring keys means only devices you gave a key to can use it.

anz33 profile require-keys on

Each device then sends its profile's key the way any OpenAI-compatible app sends an API key — paste it into the app's API key box. Requests without a valid key are refused.

require-keys on applies to the host computer too, which is the point: it means "no unidentified requests", not "no requests from elsewhere".

A setup that works

  1. Pick the machine that stays on

    The desktop, or the laptop that lives on a desk. Run anz33 install there so it starts at login.

  2. Measure it

    anz33 bench, so routing knows what this machine can do.

  3. Make a profile per person

    Kid-safe for the children, local-only for anything work-related.

  4. Require keys, then open it up

    anz33 profile require-keys on, then anz33 serve --lan.

  5. Give each device its key

    From anz33 profile list. Paste it into the API key box of whichever app that person uses.

What everyone shares, and what they do not

  • Shared: the engines, the models, the measured speeds. One download of a model serves the whole house.
  • Per profile: whether cloud is reachable, and the kid-safe setting.
  • Household-wide: the privacy rules and the kill switch. One anz33 policy offline stops the cloud for everybody.

Keeping an eye on it

The dashboard shows what has been running across the household — requests by hour, by engine, and the last twenty in detail. The audit log records every request that left the machine, whoever sent it.

Do not expose the router to the internet. --lan is for your own network. Forwarding port 3300 through a home router puts an AI endpoint on the public internet, and no key policy makes that a good idea.