Pricing
Overview
Axis pricing is designed for enterprise-scale visual production systems.
Pricing is designed around predictable cost per generated output, not per user seat. There is no seat-based licensing and no pricing driver tied to individual users.
Commercial terms use a two-layer model: a monthly platform fee (volume band + SLA/orchestration access) plus usage-based generation billing per completed output.
Billing, metering, and generation execute on StudioAxis. WorldAxis documents the commercial framework only.
Ranges below are indicative. Final terms are agreed per engagement.
Two-layer model
Layer 1 — Platform fee
The platform fee covers orchestration access, enterprise infrastructure, SLA, and support. It is not charged per user.
The fee is aligned to monthly generation volume bands (committed or estimated production throughput):
| Monthly generations | Indicative platform fee |
|---|---|
| < 10k | €500 |
| 10k – 100k | €1,000 – €2,500 |
| 100k – 500k | €2,500 – €5,000 |
| 500k+ | Custom |
Includes:
- API access and organization provisioning
- Authentication and org isolation
- Usage logging and billing infrastructure
- SLA and support coverage
- Cinematic orchestration systems access
- Ongoing model and pipeline improvements
Band placement is reviewed against actual production volume. Moving bands adjusts the platform fee — not the number of users on the account.
Layer 2 — Usage pricing
Each completed generation is billed on usage, in addition to the platform fee.
Generation = one successful API output (v1 or v2), as recorded in usage logs. This is the external billing unit — not seats, not internal compute units.
Indicative range per generation
| Production profile | Indicative range (per generation) |
|---|---|
| Low volume integrations | €0.05 – €0.15 |
| Medium scale production | €0.03 – €0.10 |
| High volume enterprise | Custom (volume discounted) |
These ranges are indicative. Effective cost depends on resolution, orchestration depth, and contract structure. They are not a public commodity SKU or consumer per-image menu.
Premium multipliers
On top of the base generation rate, multipliers may apply when orchestration complexity increases:
- Cinematic mode (v2 semantic + creative direction stack)
- Visual identity context (org-configured in organization settings)
- Higher resolution or future capabilities (video, multi-frame)
Multipliers are defined per engagement — not published as a fixed rate card.
Why pricing is structured this way
Axis is not a model API. It is an orchestration layer for visual production systems.
| Layer | What you pay for |
|---|---|
| Platform fee | SLA, support, orchestration access, infra — scaled by volume band |
| Usage | Per generation — predictable unit economics at scale |
Pricing reflects infrastructure usage, creative direction, enterprise reliability, and integration complexity — not raw provider token cost alone.
| You are buying | You are not buying |
|---|---|
| Orchestration + reliability | Per-seat SaaS licensing |
| Predictable cost per generation | Commodity “per image” playground pricing |
| Volume-aligned platform access | User-count-based billing |
| Managed pipeline evolution | Gemini/OpenAI API price comparison |
Commercial principle
We optimize for:
- Predictable platform cost — banded by production volume, not headcount
- Scalable usage pricing — per generation, with clear premium rules for cinematic/brand
- Enterprise alignment — contracts sized to integration, SLA, and automation — not consumer API benchmarks
Contact info@studioaxis.io for a scoped proposal.
What we do not publish
Internal StudioAxis commercial mechanics stay off public docs, including:
- Internal ledger or compute unit definitions
- Provider cost breakdowns (e.g. underlying model unit economics)
- Infrastructure margin formulas
Public docs use generation as the external unit only.
Related
- Enterprise — SLA, security, scaling, pilot → production
- API reference — technical integration surface
- API Examples — v1/v2 workflows
- Why Axis — orchestration vs model APIs