Prepaid credit
A wallet per company: reserve before every request, settle on measured usage. Credit arrives only once payment is confirmed.
The components and the features included, on your Kubernetes cluster.
Portal, gateway, billing and data run on your Kubernetes. Models are cloud or local, behind the same policy and accounting boundary. Manage everything from the portal or with venticli and declarative manifests.
Teams, quotas, credit, keys, model catalogue, remote agents, audit and API lab.
Chat Completions, Responses, Messages, FIM, token counting, embeddings, vision, speech and transcription, with unbuffered SSE.
A CLI for declarative resources with browser or device sign-in; an OpenCode launcher with a dynamic catalogue of authorised models.
Encrypted conversations, MCP and private search, bound to the tenant; it keeps its own branding and licence.
Identity, tenants, catalogue, policies, API keys, remote agents and runtime jobs from a fixed catalogue.
Native protocols, routing and choice of the most suitable model among authorised candidates, ranked by exact Decimal cost.
Wallets, reservations, a balanced ledger, top-ups by Stripe or bank transfer, invoices and reseller commissions.
Local detection of personal data in text, reversible placeholders and encrypted maps.
CloudNativePG with Barman backups in the bundled profile, or external services; Valkey for rate limits and ephemeral state.
Traefik, Nginx with ModSecurity CRS, cert-manager certificates; default-deny NetworkPolicies.
OIDC sign-in with Google, passkeys and TOTP; secrets and infrastructure credentials held in OpenBao.
A Rust agent for Linux and Windows: outbound WSS connection, pairing with a 15-minute invitation, administrator approval.
Strata and llama.cpp are tested; vLLM, Ollama and SGLang are accepted but not yet certified.
Compute pools and deployments through OpenTofu with approved plans, routing and authorised autoscaling. One VM, one complete replica.
Cloud models with public names, permissions and prices managed in the catalogue; verified tariffs and FX kept apart from public prices.
An Ed25519-signed lease of at most 72 hours. On expiry new requests stop, but settlement, reconciliation, export and erasure remain available.
Sign-in and invitation email, data archive and backups, online payments: provider integrations.
The chart does not install cluster operators (KEDA, cert-manager, Traefik, CloudNativePG): the cluster administrator provides them. An installation uses four namespaces and does not consume an extra licence per replica or Job.
A wallet per company: reserve before every request, settle on measured usage. Credit arrives only once payment is confirmed.
Allowances for people and groups, recurring allocations, reseller commissions calculated on settled usage.
Allowed models, per-request maximum, budget, expiry and revocation. Current policies also apply to clients holding an old catalogue.
Placeholders before the model, originals restored in the stream. Optional, text only: images and audio need specific policies.
Chooses among authorised models by suitability, effort and exact Decimal cost. Selection calls are accounted for.
Runtimes on your hardware over outbound WSS, with approval and explicit consent before sharing with other companies.
Compute pools and deployments with OpenTofu, leastBusy, weighted or failover routing, and autoscaling within approved limits.
Customer companies as application tenants, reseller delegation and commission agreements, without a cluster per customer.
Open WebUI with encrypted conversations, OpenCode with a dynamic catalogue, venticli for declarative resources.
Encrypted content, JSON export, erasure requests and an optional archive of future inference to the company's S3.
OpenTelemetry metrics, logs and traces, Perses dashboards filtered by company and an append-only activity log.
A signed Licman lease of at most 72 hours. On expiry inference stops; settlement, export and erasure remain.
Performance, mission-critical reliability and cybersecurity are not add-ons for later: they ship with the install. The code is fast and safe by construction, scales horizontally, and traffic goes through a web application firewall that is already configured.
Gateway, control plane, billing, worker, the agent on GPU servers and venticli are written in Rust, the language chosen for the critical components of operating systems, browsers and clouds.
Every request to portals and APIs goes through Nginx with ModSecurity and the OWASP Core Rule Set, configurable from the admin console.
Ventic is designed for mission-critical workloads: it carries sustained traffic from whole teams of developers, agents and applications calling models all day long, stays up when a node or provider fails, and grows by adding replicas instead of buying bigger servers.
We help you install Ventic on your infrastructure and start directly from the workload you want to put in production.