> ## Documentation Index
> Fetch the complete documentation index at: https://oximy.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use cases

> Common reasons companies start with Oximy and how each path expands.

Companies rarely begin with a platform-wide transformation. They begin with a visible problem: an inference bill, unknown AI usage, or a need for a company-owned AI workspace.

## Understand AI usage and spend

Start with Visibility when you need to answer:

* Which AI tools and accounts are in use?
* Which teams are adopting AI, and for what work?
* How much is the company spending across subscriptions and model traffic?
* Which licenses are idle, duplicated, or personally expensed?
* Where are policy, access, or data-handling risks appearing?

Visibility establishes a baseline without requiring every tool to expose the same data or every application team to add instrumentation.

## Reduce model cost without lowering quality

Start with Relay when inference cost is increasing or engineers are choosing models manually.

Relay can replay decisions against historical traffic, compare candidate models, and route each request to the least expensive model that meets the company’s requirements. Teams keep control of candidate models, provider accounts, fallbacks, and policy.

## Give employees a company-owned AI workspace

Start with Sidekick when employees need one place to work with AI across models, tools, and environments.

Sidekick turns individual conversations into shared work. Teams can collaborate in threads, preserve artifacts and memory, connect company tools, require approvals, and package proven workflows into reusable skills or agents.

## Standardize successful AI work

Visibility can identify recurring workflows and high-adoption teams. Sidekick gives those teams a place to refine the work together, while Relay controls the models used underneath it.

A typical loop is:

1. Visibility identifies a recurring workflow.
2. A team works on it collaboratively in a shared Sidekick thread.
3. Corrections, approvals, artifacts, and context become part of the workflow.
4. The proven workflow becomes a reusable skill or agent.
5. Relay selects an appropriate model when the workflow runs.
6. Visibility measures adoption, cost, and operational results.

## Maintain provider independence

Use the platform when the larger goal is to avoid dependence on one model or application provider. Oximy separates company context and workflows from the underlying model, and supports multiple ways to observe, route, and run AI.

Provider independence is incomplete without portability. Review [Ownership and continuity](/docs/platform/ownership-continuity) for the architecture, migration, and business-continuity model.