Estimator methodology
The homepage calculator uses documented scenario presets. It is intentionally simple, client-side, and explicit about what it assumes.
Preset profiles
Budget
Cheap-first preset.
Typical reduction
81%
Max savings, highest variance.
Balanced
Default mixed-lane preset.
Typical reduction
63%
Default tradeoff between savings and quality.
Quality
Higher quality-floor preset.
Typical reduction
42%
Higher quality floor, lower savings.
What the estimator models
- Monthly spend models a team's current spend before Astrolabe routing.
- Profiles map to a fixed lane mix assumption rather than live telemetry.
- Estimator outputs round to whole dollars and stay within the documented preset multipliers.
Disclaimer
Savings vary with prompt mix, fallback rates, provider outages, token counts, and any routes you pin manually.
Scenario table
| Profile | Reduction | Baseline | With Astrolabe |
|---|---|---|---|
Budget profile Max savings, most variance. | 81% | $1,000 | $190 |
Balanced profile Default tradeoff. | 63% | $1,000 | $370 |
Quality profile Higher floor, lower reduction. | 42% | $1,000 | $580 |
Pricing sources
Snapshot date: March 6, 2026
- Astrolabe routing-reference and configuration docs for lane and fallback behavior.
- Astrolabe model-roster pricing snapshot updated March 6, 2026.
- Homepage estimator presets shown on astrolabe.run for OSS onboarding.
Representative lane mix
| Lane | Budget | Balanced | Quality |
|---|---|---|---|
Budget lane summaries, lightweight extraction, classifier traffic | 70% | 45% | 25% |
Standard lane reasoning-heavy text work, longer synthesis, tool-aware chat | 22% | 40% | 45% |
Premium lane high-stakes actions, confirmations, or escalation retries | 8% | 15% | 30% |
Implementation notes
- Pricing references come from Astrolabe's published model-roster docs snapshot.
- Profile assumptions reflect representative route mixes across routine, standard, and high-stakes traffic.
- The estimator is intended for directional planning, not for finance-grade forecasting.