Opik hosting

Open-source evaluation and monitoring for LLM applications.

Gateways & LLM opsApache-2.0from $11.99/mo

In short

Opik hosting at AIHostBox means a dedicated, single-tenant Opik instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $11.99 per month and the admin account, the data and any API keys are yours.

LLM judgesExperimentsTracesDatasetsCI integration

Opik is an open-source platform from Comet, the company behind the Comet ML experiment tracker, for tracing, evaluating and monitoring LLM applications. It records every call and nested step of an agent as a trace, then lets you score those traces with heuristic metrics or LLM-as-a-judge metrics such as hallucination, answer relevance and context precision. Datasets and experiments sit alongside, so a prompt or model change can be compared against a fixed set of examples before release.

The Python and TypeScript SDKs cover dozens of frameworks, including LangChain, LlamaIndex, CrewAI and the OpenAI and Anthropic clients, and anything else can send OpenTelemetry. That traffic has to land somewhere permanent and shared: trace volumes grow quickly and evaluation history is only useful if it is still there next quarter. A server gives Opik’s ClickHouse store room to grow and a single address that every developer, notebook and CI runner can reach.

Opik hosting plans

PlusRecommended minimum

4 GB RAM · 2 vCPU · NVMe

$11.99/mo

Order

ProTeams & heavier load

8 GB RAM · 3 vCPU · NVMe

$18.99/mo

Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Opik

Opik’s official docker-compose deployment: frontend on port 5173, Java backend, Python backend for evaluators, MySQL, Redis, ClickHouse with ZooKeeper, and MinIO for attachments.

What we configure for you

Frontend served on your subdomain with TLS, and access restricted because the open-source build has no login
Persistent volumes for ClickHouse, MySQL and MinIO data
AI provider keys for the prompt playground and online evaluation rules
Guardrails services left disabled unless you ask for them, to save memory
SDK connection details (instance URL, workspace default) handed over for your developers and CI

Which plan fits

Plus (4 GB) runs the whole stack for one developer or a small project with modest trace volume. Pro (8 GB) is the better choice for a team, sustained production tracing or frequent experiment runs, since ClickHouse and the Java backend both benefit from memory.

The honest limits

No built-in user accounts or per-project permissions in the self-hosted build. Comet labels its Docker Compose install as a local deployment and recommends Kubernetes for production scale, so very high trace volumes are better served by a larger dedicated setup.

What people run Opik for

Ship prompts with evidence

Score a change before it reaches customers.

Regression gates in CI

Fail a build when quality drops.

Production hallucination watch

Online evaluation rules score live traces with an LLM judge and flag the bad ones.

Tracing a Dify app

Point Dify’s built-in Opik integration at your instance and see each workflow step.

Licence and version policy

Item	Position
Upstream licence	Apache-2.0
Sold as managed hosting	Yes
Tenancy	Single tenant — one customer per instance
Patching	Critical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Reading on Opik

ComparisonLiteLLM vs OpenRouter ComparisonLangfuse alternatives for LLM observability

Works well with Opik

More Gateways & LLM ops we host

Questions

Opik hosting: your questions

Does self-hosted Opik have user accounts?

No. Comet states that self-hosted Opik includes the full feature set but not user management, which is reserved for Opik Cloud. Anyone who reaches the interface can use it, so we do not leave it open: access is restricted at our proxy, and you decide who on your team gets the credentials.

How do I send traces from my code?

Install the opik Python or TypeScript SDK and run opik configure, pointing it at your instance’s URL instead of Comet’s cloud; the setting is stored in ~/.opik.config for that machine. Framework integrations and the @track decorator then log every trace to your server, and CI runners use the same configuration.

Which models run the LLM-as-a-judge metrics?

Judges call a model you configure, through LiteLLM-style provider settings in the SDK or the AI provider settings in the UI. That can be OpenAI, Anthropic or an OpenAI-compatible endpoint such as your own LiteLLM or Ollama plan. Judge calls are billed to your provider key, not by us.

What data does Opik store, and where?

Traces, spans, feedback scores and experiment items go into ClickHouse. Project metadata, dataset and prompt definitions with their versions, and automation rules live in MySQL. Attachments and uploaded dataset files go to MinIO object storage. All three sit on persistent volumes covered by the nightly off-box backup.

Is Opik free to use commercially?

Yes. Opik is Apache-2.0, backend included, so running it for your own company carries no licence fee. Comet sells Opik Cloud and enterprise deployments with extra features such as user management; the open-source platform does not need them to trace and evaluate.

Run Opik without running a server

A dedicated Opik instance, deployed and maintained by us. Month to month, cancel whenever.

Browse the catalogue Talk to a human