Skip to content
CapkaCapka Docs

Cloud and Local Models in Capka

Capka is model-provider independent: use a provider you already pay for, an OpenAI-compatible endpoint, or local models served through Ollama.

Two paths from Capka to a model
Your Capka instanceChats, files, and tools
HTTPSCloud modelContent needed for inference goes to your configured provider
LANLocal modelOllama can keep inference inside your infrastructure

Supported connection patterns

  • Anthropic models with your own API key.
  • OpenRouter with your own account and billing.
  • OpenAI-compatible endpoints, including compatible self-hosted gateways.
  • Local models exposed through Ollama.

Choose a model for the work

File-heavy jobs may need long context, reliable tool use and enough output capacity to plan multi-step work. A smaller local model can be a good fit for private or routine tasks, while more complex document analysis or code changes may benefit from a stronger cloud model.

Validate the complete workflow rather than a single chat response: attach a representative file, let the agent use its tools, and inspect the returned artifact.

Privacy and cost

Uploads and result files stay on the Capka instance. Content required for inference is sent to the model provider you configure. With a local model, inference can stay entirely inside your infrastructure.

Capka adds no model markup or per-seat subscription. Provider usage and server resources are billed directly to you, and administrators can see token spend by user without reading private conversations.

Capka source code · Full documentation for LLMs