External power on demand
Load spikes, demos, or a one-off high-cost job: route to OpenRouter without redesigning your stack. The panel stays the control point.
Extension · OpenRouter
External providers
Xeretron is integrated with OpenRouter to use external power when you need it and giant models when they are truly required and worth it. Local remains the default; external is a deliberate exception.
Why it exists
Your node. An escape hatch when the work demands it.
Junior, Developer, Turbo, Titan, and Omega cover day-to-day on your GPU. OpenRouter steps in when you need more power than fits in the rack — or a Frontier model that does not make sense to host permanently.
Giant models, with judgment
When the case truly requires it and the ROI justifies it — not for fashion. Big frontiers for big problems; everything else returns to the node.
OpenRouter integration
One bridge to many providers and models. You set credentials and policy; Xeretron does not force you to live in the cloud.
Local first
Privacy, predictable cost, and rack latency. External is an extension — not the product’s center of gravity.
Worth it — or not
If the work fits Titan or Omega locally, it stays there. OpenRouter for what your hardware cannot reach or does not justify buying.
Data with policy
Every external hop means data leaving the node. Use it with clear policy: what leaves, what does not, and who authorizes the provider.
How it fits
Same panel. Two worlds, one decision.
You work with the Xeretron catalog and HF locally. When an agent, bench, or delivery needs a model that does not fit (or should not live) on your GPU, you choose the OpenRouter path from the same ecosystem.
- Default: local catalog models and HF downloads.
- Extension: OpenRouter for power or giant models.
- Criterion: only when needed and worth it.
- Back to the node as soon as the work allows.
Lives with the catalog
- Junior → Omega on your infrastructure
- + HF downloads for experimentation
- + OpenRouter when the case demands it
- Without leaving the Xeretron panel
Next step
Local by default. External with intent.
We evaluate with you when OpenRouter adds value — and when your GPU already covers it.