Home/Answers/Self-hosting
AI COST LAB / Self-hosting

Why Handle Self-hosting?

Handling Self-hosting is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach.

Updated 2026-11-01About 3 minLocal test
Quick answer

Handling Self-hosting is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach. Self-hosting has GPU/ops/utilization thresholds; only stable high utilization may be cheaper.

Why it matters

Different goals imply different formats, tools and quality settings.

GPU fixed cost.

Step by step

  1. Measure input, output and retry tokens per user/task.
  2. Separate cache, batch, embeddings and fine-tuning costs.
  3. Use 30 days of real requests for cost per user, then margin.
  4. Model prices change; baseline from official pricing pages and record the date.

Common mistakes

  • Estimating from input tokens only; output often costs more.
  • Forgetting retries, failures and tool calls.
  • Assuming cache hits by default.
  • Using stale prices for long-term margin.

Checklist

  • Input/output/cache/retry tokens are tracked separately.
  • Batch/async fit and latency requirements are clear.
  • Embeddings/fine-tuning/image/audio are separate.
  • Cost per user and margin use real usage.
  • Price date and fallback model are documented.

Key facts

  • GPU fixed cost.
  • Ops labor.
  • Utilization matters.

FAQ

Why should I handle Self-hosting?

Handling Self-hosting is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach. Self-hosting has GPU/ops/utilization thresholds; only stable high utilization may be cheaper.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: Nops