On this page
01
Different Jobs, Same Traffic
Langfuse is a strong tool for tracing, prompt iteration, and general-purpose evaluation while you're building. Cloptima governs and accounts for the spend that traffic creates once it's in production: budgets, guardrail cost policy, response caching, and cost optimization tied directly to specific recommendations.
02
Keep Langfuse For Prompt Engineering
There's no reason to give up trace-level debugging, prompt versioning, or evaluation workflows you already rely on. Cloptima does not replace them.
03
Forward usage to Cloptima
Route production traffic through Cloptima's gateway (or forward usage from wherever it currently runs) so budgets, guardrail cost governance, and caching apply, while Langfuse keeps handling trace-level debugging and prompt iteration.
https://api.cloptima.ai/v1/ai/integrations/langfuse/events
# Authorization: Bearer clop_vk_dPXO67p…04
Add budgets, guardrails, and caching
Once usage is flowing, set model and provider budgets, enable guardrail profiles (and choose what happens if a provider scan cannot run), and turn on the exact or semantic response cache in Monitor only to see savings before serving.