Getting started.

Alluqi Bridge is in private early access. Here is how access works today — for individuals running Bridge locally and for organizations planning a deployment.

Individual local use — free

Running Bridge Desktop locally is free. You need three things:

1. Suitable hardware you control. Private or local inference always needs a physical, GPU-capable workstation or server somewhere.
2. A supported runtime. Connect Bridge to a runtime such as Ollama or vLLM. See models + runtimes.
3. An Alluqi account. The account establishes product identity, device authorization, access lifecycle, and a secure path to optional remote features.

Signing in

Sign-in is passwordless: you receive a one-time sign-in code by email. There is no password to create, reuse, or phish.

A signed-in account is not the same as remote authority. Remote features — pairing a phone, viewing sessions away from the desk — are separately gated. See Bridge Mobile and the security model.

For organizations

Organizations work directly with Alluqi through four stages:

1. Assess. Map one useful workflow, the data it touches, the people who review it, and the infrastructure it can use.
2. Configure. Set up models, runtimes, approved tools, permissions, and workspace policy around the agreed environment.
3. Validate. Prove the data path and the workflow before anything rolls out.
4. Launch. Staff rollout, training, and ongoing support.

Start with one defined use case, prove the data path, then expand deliberately.

What to prepare

• One defined use case — the workflow you want Bridge to carry.
• The data boundary — what the workflow may touch, and what it must never touch.
• The reviewers — the people who stay in control of decisions.
• The infrastructure — existing hardware, network constraints, and the model strategy you are considering. See deployment options.