Legal · Aurora Rate Card
TAIGA AURORA RATE CARD
Version 1.0 · Effective 6 September 2026 · Published 6 September 2026
The notes in the margin explain the clauses. Only the clauses bind.
Contents
1. WHAT THIS DOCUMENT IS
In plain language
The meter. What each step gives you, what we count, how we measure it and what one Aurora is. Aurora follows real consumption, so it moves with the market in both directions.
This Rate Card states the Aurora Pool of each step, what is metered, how consumption is measured and the basis on which it is converted into Aurora. It is incorporated by the Order Form in the version published on the date of the Order Form. Aurora tracks what an operation actually consumes, so the Aurora cost of the same operation moves with third-party model and infrastructure prices in both directions. A new version is published as clause 4.6 of the Master Service Terms provides: not less than ninety days' notice with the grounds stated where what is metered, how it is measured or the conversion basis changes, and a right for the Customer to end the affected Service without charge. A movement in a provider's own prices is not a new version.
2. STEPS AND POOLS
In plain language
The pool is what your step buys each month.
| Deliver + Operate step | Monthly fee, EUR | Aurora Pool per month |
|---|---|---|
| Start | 4,000 | 1,000 |
| Scale, per unit, stackable up to eight units | 10,000 | 5,000 |
| Portfolio, the ceiling | 100,000 | 80,000 |
Above eight units of Scale the next step is Portfolio. Aurora unused at the end of the month expires.
| Learn step | Products | Monthly fee, EUR |
|---|---|---|
| 1 to 10 | 1–10 | 2,000 |
| 11 to 100 | 11–100 | 5,000 |
| Unlimited | unlimited | 10,000 |
Within the scope in the Service Description, Learn consumes no Aurora.
3. WHAT ONE AURORA IS
In plain language
What one Aurora is. It follows the underlying bill rather than a price we set, so a cheaper model makes your pool go further.
| Metered operation | Unit | Aurora |
|---|---|---|
| Build | per Build | The model-inference and runtime consumption the Build causes |
| Runtime Hour, Taiga-hosted mode | per application-hour | The runtime and model consumption the application causes in the hour |
One Aurora is one euro (EUR 1) of third-party model-inference and runtime consumption incurred on Taiga's cloud and model providers, measured from those providers' own billing data for the account or workload concerned. Aurora is therefore a measure of consumption rather than a price Taiga sets: when a provider's prices fall the same work consumes fewer Aurora and the Pool goes further, and when they rise it consumes more. Nothing is invoiced per Aurora; the Pool and the Account Cap in clause 4.3 govern what happens when consumption reaches the step's Pool.
4. HOW CONSUMPTION IS MEASURED
In plain language
The measure matters as much as the price, so it is written down.
A Build is one unit of work that runs from an accepted specification through the review and release checks to an implementation package. A Runtime Hour is one hour during which an application runs in Taiga-hosted mode, measured per application. A Product is one application or one repository; Products are counted at the end of each month for the Learn step. The Platform shows what an operation is expected to draw before it runs and the running total for the month. Consumption that clause 4.7 of the Master Service Terms says is not charged is restored to the pool in the month it was recorded.
Versions
Published 6 September 2026 · Version 1.0