Skip to main content

Get started

How Novie works

The four parts of Novie Control, and what happens to a single AI request from the moment your app sends it to the moment it is paid for.

Novie Control gives your company one place to decide who may use AI, for what, with which models, and with how much money, and to see what actually happened. It is built from four parts that share one model of your organisation.

PartWhere it runsWhat it does
ControlWeb appOrganisation, members and roles, budgets, workloads, policies, approvals and reporting.
AI gatewayNovie cloudOne OpenAI-compatible endpoint for every approved model. Checks key, workload, policy and budget before each call and meters the result.
MCP gatewayNovie cloudAn MCP endpoint that lets AI tools such as Claude or Codex read and manage Control, with the permissions of the person using them. In v1.2 it serves Control's own tools. In the next release it becomes your company's single, policy-governed MCP gateway for all tools.
DaemonYour employees' computersWatches local AI coding tools (Claude Code, Codex, GitHub Copilot in VS Code), applies quota and policy locally, and reports privacy-filtered usage.

The workload is the unit of governance

Everything in Novie hangs off a workload: a project, product, team initiative or agent that uses AI. A workload is either Run (a running application that spends through one Application Key) or Build (people building with AI, each spending through a personal Novie Key). It has an owner, members, a budget drawn from its department, and the policies inherited from the organisation tree above it. Usage, cost and prompt records are always attributed to a workload, which is what makes reports and chargeback meaningful.

Organization (root)
 └─ Department / business unit      ← funds flow down, policies inherit down
     └─ Workload                     ← owns budget, members and keys
         └─ Requests                 ← metered, audited, attributed

The life of a request

  1. A running app calls the AI gateway with its workload's Application Key (Run workload), or a developer calls it with their personal Novie Key (Build workload).
  2. The gateway resolves the key to its workload and confirms the workload is approved, active and funded. For a Novie Key it also confirms the person is a current member.
  3. Policy is evaluated along the path from the organisation down to the workload. The model must be in the intersection of the organisation catalogue, the effective policy and the workload's allowed models.
  4. Funds are reserved, the request is sent to the provider, and the response streams back.
  5. When the response finishes, actual usage is settled against the reservation and recorded with the price that applied at that moment.
  6. The request appears in Usage, rolls up into Overview, and becomes evidence for Insights and the Assistant.

If a step fails before the provider is called, nothing is charged. Once a response has started streaming, Novie never silently retries it on another model.

Identity, permissions and policy

  • Identity is authoritative for who someone is and which organisation and role they hold. Novie integrates with your existing sign-in.
  • Permissions come from roles and from where a person sits in the organisation tree.
  • Policies add business rules on top: allowed models, approval requirements, MCP access, automatic top-ups. A child node may tighten a parent's policy but never loosen it, and no policy can grant access a role does not already allow.

Data you can trust

  • Every money movement is a balanced ledger entry, and every change is audited.
  • Reports distinguish no data, delayed data, partial coverage and failure, rather than showing an empty chart as zero.
  • Prompt content is only collected where a reporting policy allows it, and only people with a dedicated permission can read it.