Anvil Serving

Operate, qualify, and expose local AI capabilities through explicit, reviewable contracts.

One package and release line for Model Serving, the Capability Gateway, Evaluation & Evidence, Anvil Voice, Anvil Media, and Control Plane & Fleet. Each family has an explicit authority boundary and ordered CLI journey. There is no hidden model substitution.

Browse benchmarks Get started

Choose your path

Start with the outcome you need. Each path leads to current guidance, not a historical implementation record.

Evaluate Compare measured models, hardware, and qualification evidence. Operate Run serving, gateway, voice, media, and fleet workflows safely. Integrate Connect through explicit APIs, aliases, protocols, and contracts. Verify Confirm authority, safety, and evidence boundaries before exposure.

Local services, one private network

Keep model, voice, media, router, and controller processes on each owning device's loopback interface. Tailscale supplies private device reachability and identity policy; Tailscale Serve publishes only the reviewed front doors.

Manage host servicesDiscover, adopt, inspect, start, and stop services through Anvil. Use Docker on Windows and Linux, or native MLX and Docker on macOS. Set up private networkingUnderstand device roles, identity, grants, MagicDNS, mobile access, and the Serve-to-loopback pattern. Place roles across devicesSeparate primary inference, harness, voice, media, and operator ownership without exposing machine identity.

Anvil Connect — one credential for every local surface

The newest product family publishes local applications to browsers through a self-hosted edge: your own TLS certificate authority, the OIDC provider you already run, an outbound-only data plane, and applications that stay loopback-bound and unchanged. Exposure is one declaration, enrolled through an invitation, redemption, and human fingerprint approval — never an implicit publish.

Anvil ConnectThe product story: the access problem, how the pieces fit, one identity three ways, and the boundary it holds. Application access guideDeclare a resource, render and review the plan, activate, enroll, and approve. Connect commandsQualify, validate, render, up, down, status, init, identity, and admin verbs.

Current benchmark evidence

Model occupants and measurements change faster than capability contracts. Their dated evidence stays discoverable without becoming product documentation or a claim about the currently deployed operator state.

Latest qualified native reference — GLM-5.3-Flashv0.4.3 native Linux recipe: 524,288 shared tokens with C4 four-request scheduling (from 393K/C1), decode +20.5–33% and 4K time-to-first-token −31% versus the previous Windows/WSL2 serving (controlled Sep 8 A/B), unchanged ormandj W4A16/NVFP4 weights, FP8 KV, adaptive EAGLE. 14/14 Pi gates, retrieval through 497,724 measured tokens, human-gated promotion. Boundaries are stated in the dossier. Model comparisonEvery measured configuration in one table. Benchmarks overviewHardware-first recommendations and evidence labels. Model dossiersStatus, recipe, and decision boundary by model. Run catalogReproducible run identities and artifact links. Dated findingsSanitized evidence snapshots retained as published.

One product, six operating families

The families share one CLI, topology, safety contract, evidence policy, and release line. Each still owns a distinct operator outcome.

Model Serving Pin artifacts and recipes, manage lifecycle and reservations, and promote with a human gate. Open model lifecycle Capability Gateway Expose exact authenticated aliases with translation, readiness, admission, and streaming. Open the gateway Evaluation & Evidence Run preflight and comparison-safe benchmarks, then retain the evidence behind each decision. Review evidence Anvil Voice Operate STT, TTS, realtime proxy, profiles, and reproducible voice qualification. Open voice Anvil Media Run bounded named image and video workflows with durable jobs and artifacts. Open media Control Plane & Fleet Resolve topology and ownership, dispatch typed operations, and keep fleet state explicit. Open fleet operations

The operating contract

Configuration, runtime state, qualification, and exposure are separate facts. Anvil Serving keeps those transitions explicit.

1. Declare Define models, aliases, policies, and authority boundaries as configuration.
2. Operate Run serving, gateway, voice, media, and fleet workflows inside those boundaries.
3. Qualify Measure with preflight and benchmarks. Evidence never auto-promotes.
4. Expose Publish only approved capabilities through explicit, authenticated contracts.

Reference

Use these pages when you need exact contracts, commands, or failure guidance.

ArchitectureComponents, authority planes, and deployment shapes. Product mapFamily boundaries and ordered user journeys. ConfigurationRouter, serve, voice, media, and fleet contracts. Command indexEvery command family, policy, and option. TroubleshootingDiagnose aliases, serves, authentication, and preflight. TerminologyShared vocabulary for routes, serves, topology, and evidence.