Give your team access to local models

​

What you get

• OpenAI-compatible API endpoint — any client that speaks OpenAI SDK works out of the box
• Per-person API keys — each teammate gets their own sk-tok-… key, scoped to specific models
• No networking headaches — the connector dials out, so it works behind CGNAT, Starlink, 5G, apartment ISPs, corporate firewalls
• Model routing — serve multiple models (Ollama, vLLM, llama.cpp) through one endpoint
• Per-key revocation — remove one person’s access without touching anyone else’s

​

Set it up in 5 steps

curl -fsSL https://tokios.com/downloads/install/linux | sh -s -- --code TKS-XXXX-XXXX

curl -fsSL https://tokios.com/downloads/install/macos | sh -s -- --code TKS-XXXX-XXXX

irm https://tokios.com/downloads/install/windows.ps1 | iex

​

Use it from any client

curl https://api.tokios.com/v1/chat/completions \
  -H "Authorization: Bearer sk-tok-YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "team-llama",
    "stream": true,
    "messages": [{"role": "user", "content": "Hello from the team laptop"}]
  }'

from openai import OpenAI

client = OpenAI(
    base_url="https://api.tokios.com/v1",
    api_key="sk-tok-YOUR_KEY",
)

response = client.chat.completions.create(
    model="team-llama",
    messages=[{"role": "user", "content": "Hello from the team laptop"}],
)
print(response.choices[0].message.content)

import OpenAI from 'openai';

const client = new OpenAI({
  baseURL: 'https://api.tokios.com/v1',
  apiKey: 'sk-tok-YOUR_KEY',
});

const response = await client.chat.completions.create({
  model: 'team-llama',
  messages: [{ role: 'user', content: 'Hello from the team laptop' }],
});
console.log(response.choices[0].message.content);

​

Key management for teams

• Scope access to specific models (a developer gets team-llama and team-qwen, a tester gets only team-llama)
• Revoke one person’s access without disrupting everyone else
• Track usage per person (if request logging is enabled)

​

Networking: how it works without the headaches

• CGNAT? Works. Your ISP puts you behind carrier-grade NAT (Starlink, 5G, apartment buildings)? The connector dials out, so it doesn’t matter — see Serve a local LLM from behind CGNAT for why that’s a router setting you can’t fix yourself.
• Corporate firewall? Usually works. The connector only needs outbound HTTPS (port 443). If your IT team blocks outbound WebSocket, you’ll need an exception — but most corporate firewalls allow it.
• Remote teammates? Works. Your teammate can be on the same LAN, across the country, or on a different continent. They call https://api.tokios.com/v1 with their API key, and the request routes through the tunnel to your local model.

​

Tokios vs Tailscale vs Cloudflare Tunnel

• Tailscale alone is great for personal multi-device access, but it doesn’t give you per-user API keys, model scoping, or OpenAI-compatible protocol translation. Every device on your tailnet has the same raw access to the runtime. See Tokios vs Tailscale for the full comparison.
• Cloudflare Tunnel works but has SSE buffering and timeout issues that break streaming responses — see Tunnels and streaming for the gory details.
• Tokios is purpose-built for team access to local models: per-user keys, model routing, protocol translation, and a tunnel that handles streaming correctly.

​

When to use Tokios

• You have a local model and your team needs to call it via API
• You want per-person authentication and model scoping
• You’re behind CGNAT or can’t open inbound ports
• You want an OpenAI-compatible endpoint without the networking plumbing

• You’re air-gapped (no internet at all) — the tunnel needs outbound internet
• You’re in a regulated environment that requires on-premises-only infrastructure
• You already have a mature API gateway stack and just need a tunnel — use Cloudflare Tunnel or Tailscale instead
• You only need personal multi-device access — Tailscale alone is simpler

​

FAQ

​

Next steps

• API keys reference — full details on scoping, sharing, and revocation
• Model routing — serve multiple models through one endpoint
• Tokios vs Tailscale — detailed comparison
• When to use Tokios — decision framework
• Compatible clients — find your client (Open WebUI, Continue, Cline, etc.)