KoboldCpp hosting

A single-binary GGUF server with its own UI and a KoboldAI API.

LLM runtimesAGPL-3.0from $13.99/mo
In short

KoboldCpp hosting at AIHostBox means a dedicated, single-tenant KoboldCpp 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 $13.99 per month and the admin account, the data and any API keys are yours.

GGUFBuilt-in UIKobold APIOpenAI-compatibleContext shifting

KoboldCpp is a single-file model server maintained by LostRuins (concedo) that wraps llama.cpp with the KoboldAI Lite interface. You point it at a GGUF file and get three things at once: a browser UI for chat, adventure and story writing, the KoboldAI API that role-play front-ends expect, and an OpenAI-compatible /v1 endpoint plus an Ollama-style API for everything else. Context shifting lets long sessions continue without reprocessing the whole prompt, which is the reason writers and character-chat users keep choosing it over plainer servers.

It also bundles optional extras in the same binary: image generation, Whisper transcription, text-to-speech, embeddings and vision through an mmproj file. On a laptop it only works while the lid is open and the fan is spinning. On a server it becomes an endpoint that SillyTavern, a phone or a script can reach from anywhere, protected by an API key and running the same model all day without tying up your own machine.

KoboldCpp hosting plans

Starter7-8B GGUF (Q4)
8 GB RAM · 4 vCPU · NVMe
$13.99/mo
Order
Plus13B GGUF (Q4)
12 GB RAM · 6 vCPU · NVMe
$24.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 KoboldCpp

We run the upstream KoboldCpp release as a single process on port 5001 with one GGUF model loaded from local NVMe storage; there is no database, and settings live in a .kcpps config file.

What we configure for you

  • --model pointing at your chosen GGUF file, downloaded or uploaded over SFTP
  • --password (KCPP_PASSWORD) so every text endpoint needs your API key
  • --threads matched to the plan’s vCPUs and --contextsize matched to its RAM
  • --multiuser so several clients, such as SillyTavern and a script, can queue requests
  • A saved .kcpps config so the same settings come back after every restart or update

Which plan fits

Starter (8 GB, 4 vCPU) fits a 7-8B GGUF at Q4 with a moderate context, typically 5-15 tokens per second on CPU. Plus (12 GB, 6 vCPU) fits a 13B Q4 model, which reads better for fiction but generates more slowly. Larger models, or long contexts on top of 13B, need more RAM than either plan offers.

The honest limits

Everything runs on CPU, so the image generation, speech and video extras are possible but slow enough that we do not recommend them on these plans. KoboldCpp’s own help notes that --password does not protect the image endpoints.

What people run KoboldCpp for

SillyTavern backend

The most common local pairing for character chat.

Long-form generation

Context shifting keeps long sessions coherent without a full re-prompt.

Private OpenAI-compatible endpoint

Point any tool that accepts a custom base URL at /v1 and keep prompts off third-party APIs.

Interactive fiction

Use the built-in story and adventure modes in KoboldAI Lite without installing a separate front-end.

Licence and version policy

ItemPosition
Upstream licenceAGPL-3.0
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical 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.

Works well with KoboldCpp

More LLM runtimes we host

Questions

KoboldCpp hosting: your questions

Which models can I run?
Any GGUF model that llama.cpp supports, which covers Llama, Mistral, Qwen, Gemma, Phi and most community fine-tunes on Hugging Face. On our CPU plans, stick to Q4 quantisations: 7-8B models on Starter and 13B on Plus. Tell us which file you want and we download it, or upload your own over SFTP.
How do I stop strangers using my instance?
KoboldCpp has a --password option, also settable as the KCPP_PASSWORD environment variable, which makes every text endpoint require that key. We set one for you and give it to you with your login details. Clients send it as a bearer token, the same way they would send an OpenAI key.
Can other apps use it like the OpenAI API?
Yes. KoboldCpp serves an OpenAI-compatible API under /v1 alongside its native KoboldAI API, and it also answers Ollama-style requests. Open WebUI, LobeChat, SillyTavern and most scripts that take a custom base URL work without a plug-in.
How long a context can I use?
You set it with --contextsize. Longer contexts need more RAM for the KV cache, so on the 8 GB plan with a 7-8B Q4 model a context of around 8k tokens is the comfortable choice, with more on the 12 GB plan. Context shifting then trims the oldest text instead of reprocessing everything when a chat overflows.
Is AGPL-3.0 a problem for me?
Not for using it. The AGPL obliges whoever modifies KoboldCpp and offers it over a network to publish those changes. We run upstream builds unmodified, and your prompts, outputs and characters are yours. If you fork and change the code yourself, the source-sharing duty applies to you.

Run KoboldCpp without running a server

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