TL;DR: NeuralTrust warns that Luna’s apparent 20-times token savings shrink to about 12 times at the task level because it outputs more. Routing and governance need per-workload limits, or lower tiers can cost more in production than they first appear to.
Editorial analysis by NHI Mgmt Group, based on content published by NeuralTrust: “GPT-6 Sol vs Luna: Security, Cost, Routing”.
By the numbers:
- Luna is 20 times cheaper per token, but only 12.6 times cheaper per benchmark run.
- OpenAI reports instruction hierarchy defender success of 99.97% for Sol and Luna and 99.99% for GPT-6.1 Sol.
- SonarSource found 285 vulnerabilities per million lines from GPT-6 Sol against 178 for Astra.
Key questions
Q: Why can a cheaper model still cost more in production than a stronger one?
A: Because task cost includes more than token price.
Q: What breaks when model safety and performance are judged only at the family level?
A: Model-family approval hides differences in tool behaviour, cyber posture and output quality between tiers.
A: Security and platform teams should use a routing layer that evaluates each request against policy, rather than hardcoding one default model.
Practitioner guidance
- Define routing rules by workload class Separate simple, repeatable tasks from multi-step agent work and route each to a default tier before developers choose a model ad hoc.
- Gate higher-tier models behind policy Require approval or policy evaluation before workloads can move from Luna to Sol or from Sol to GPT-6.1 Sol when tools or sensitive data are involved.
- Red team each model tier separately Re-test prompt injection, tool misuse and code-generation risk whenever the workload changes model or starts using a new capability such as function calling.
Bottom line: Cheaper model tiers still need explicit routing rules because task complexity, retries and escalation can erase the expected savings.
Glossary terms: Model routing policy, Delegated Access, Escalation Rate, Tool-Enabled Model
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Model tiering has become a governance control, not just a cost lever. When one model is cheap but another is stronger on agent work, routing policy determines how risk is distributed across the programme. That makes model selection part of control design, especially where tools, external search and delegated actions are involved. The practical conclusion is that teams need policy-based routing, not ad hoc developer choice.
A question worth separating out:
Q: What should teams do when an AI system can call privileged tools?
A: Teams should apply least privilege at the tool layer, require strong parameter validation, and log every action to an auditable identity trail. The model should never be able to widen its own scope based on phrasing or conversation context. If a tool can export data, delete records, or modify accounts, its permissions need explicit governance.
👉 Read our full editorial: GPT-6 Sol and Luna require workload-specific governance and routing