All Integrations

better-cmdk self hosted ai endpoint integration

Self-hosted endpointIntegration Guide

Use a self-hosted endpoint when data residency, private networking, or compliance controls are required.

Implementation Notes

This approach keeps inference traffic on infrastructure you control. better-cmdk still handles command/search/chat UX while your endpoint enforces policy and model access.

Best For

  • - Organizations with private network or compliance boundaries
  • - Apps that must keep prompts and context on controlled infrastructure
  • - Teams running open-weight models in dedicated environments

Quick Setup Checklist

  1. 1. Expose a stable internal chat endpoint with streaming support.
  2. 2. Secure endpoint access with auth, origin checks, and request limits.
  3. 3. Connect CommandMenu through chatEndpoint or an adapter layer.
  4. 4. Instrument latency and error metrics before opening to broad traffic.

Integration FAQ

Can self-hosted still use the same UI components?

Yes. better-cmdk UI stays the same as long as the endpoint contract remains compatible.

What is the minimum production hardening?

Authentication, rate limiting, structured logs, and server-side action permission checks.

Should I expose the endpoint publicly?

Only if required. Most teams keep it behind application auth and controlled network access.

Related Integration Guides

better-cmdk modifywithai integration

modifywithai.com

Use modifywithai.com when you want AI chat that can execute real app actions, not just answer questions.

better-cmdk vercel ai sdk integration

Vercel AI SDK

Use this path when you want a clean streaming chat endpoint and full control over model/provider selection.

better-cmdk custom externalchat integration

Custom ExternalChat

Use a custom ExternalChat adapter when your organization already has an internal chat orchestration layer.