Skip to content

Campus Intelligence

Campus Intelligence gives browser apps, workloads, and agents access to model inference without placing reusable provider credentials in application code.

Configure a model

Applications request an exact provider/model resource such as intelligence.use(provider:model). Campus combines that grant with account configuration, placement, model availability, budgets, and rate policy.

text
App → installation Gateway → policy metadata → CampusOS
    ← sealed credential envelope ← authorization and budget
Gateway → approved model provider

CampusOS receives bounded policy and estimate metadata—not the application prompt or provider response. The installation Gateway decrypts the credential envelope transiently and injects the provider authorization only for the approved target.

Browser and workload paths

Workloads use their installation-local Gateway credential. Browser apps cross an origin-pinned trusted-shell bridge and use a passkey-protected account recipient delivered directly to the exact Gateway.

See permissions and MCP for the public authority and tool contracts.

Software belongs to people. Campus gives it a durable place to run.