Community Edition · Free, no expiry

Run the full control plane, free.

Vidai Community is the same Rust binary that runs in regulated production. Self-serve in two steps, runs inside your perimeter, on anything with a CPU. Free for personal, evaluation and non-commercial use; commercial use is by approval, granted case-by-case.

1

Sign in

At portal.vidai.uk. Generate your vidai.license file and your free rate-card credentials.
2

Download

The latest release tarball and the cosign signature from github.com/vidaiUK/vidai-quickstart.
3

Run

Verify the signature, drop your licence file in, run ./setup.sh and ./vidai start. Dashboard at http://localhost.

What you get

The full production gateway, not a stripped trial.

Community is the same binary that runs in paying customers' regulated production deployments. Your vidai.license file decides which features unlock; the Community licence unlocks the gateway and cost-engine essentials.

Gateway & routing

Multi-provider with fallback. Bidirectional native translation across OpenAI, Anthropic and Google SDKs. Routing rules.

Cost engine

Every request priced the moment it returns and attributed to the user, key, team, app and model that spent it. Per-team budgets and spend circuits.

Guardrails

Regex guardrails: block, mask, redirect, log-only. ML guardrails are an Enterprise feature.

Teams & rate limits

Teams, applications, API key issuance, per-key and per-team rate limits.

Rate-card server

Free public rate-card service, refreshed on a standard cadence, credentials in the portal alongside your licence. Best-effort SLA.

Request logs

Every request logged with the everyday audit surface. Compliance routing and the full audit-grade ledger live at Scale.

For the full feature breakdown across Community / Scale / Enterprise, see pricing.

If your organisation needs more

Same binary. Different needs.

Community is complete for its persona: developers, evaluators, non-commercial use. The paid tiers are not "Community plus extras"; they are the same binary licensed for organisations whose AI traffic has to answer to a CFO controlling spend across teams, an auditor or regulator asking for evidence, or a CISO who needs a contract behind every feature.

Scale

For organisations serious about cost control and compliance evidence.

Full audit-grade ledger with point-in-time replay (rerun a month of cost after a rate-card change), compliance-led routing that produces evidence as a by-product, BI tables and HMAC-signed webhooks for your own analytics stack. The right fit when AI spend across teams has reached the point where the CFO wants real attribution, or when you need one-click evidence against frameworks like ISO/IEC 42001, EU AI Act Article 12 or DORA.

What Scale includes →

Enterprise

For highest assurance and your own ML guardrails.

VidaiGuard ML guardrails for prompt-injection, toxicity and PII detection with bring-your-own-model support, your own rate-card server (or premium-SLA service), enterprise identity via SSO and LDAP, plus priority support and SLA. The right fit when Vidai is in your critical path and a CISO needs a contract behind every feature.

What Enterprise includes →

Scale and Enterprise are contact-led. Start a conversation at /contact.

Runs anywhere with a CPU

25 MB. One binary. Inside your network.

Your VPC, on-prem, a laptop for evaluation, even a Raspberry Pi if you really want to. Provider-agnostic, framework-agnostic, no phone-home. Cost attribution, inline policy and audit happen on your perimeter, with the prompt content never leaving your network to make those decisions.

Install instructions on GitHub

Download, cosign-verify, drop in your vidai.license, run ./setup.sh. Full reference inside the tarball and at docs.vidai.uk.

The fine print, plainly

Commercial use is by approval.

Vidai Community is free for personal, evaluation and non-commercial use without further approval. Commercial use (by or on behalf of a business, or in connection with a commercial product or service) requires our prior written approval, which we grant case-by-case. Email [email protected] with a sentence about your use case.

The full licence text lives at /legal/community-licence and ships in every distribution tarball as LICENSE-COMMUNITY.