Plans and compute units
PULSE is sold on its own, with its own plans. A PULSE subscription does not include FACE, and a FACE subscription does not include PULSE. PULSE charges per seat, plus compute on the Lite plan. It has no per-action or outcome fees.
Plans
| Plan | Where PULSE runs | Seats | Price per seat per month | Compute units |
|---|---|---|---|---|
| Lite | Runink’s shared hardware, spot-style | 1 to 9 | $49 billed yearly, or $59 month-to-month | 10,800 CU per seat per month, pooled across the account |
| Dedicated | Runners in your own cloud: Google Cloud, Databricks, or Snowflake | 10 or more | $99, billed yearly | Unlimited |
| Enterprise | Your premises or your own cloud | 10 or more | Custom quote | Unlimited |
Prices are the US-dollar list. See Currency and billing periods for how your invoice is priced.
Lite runs in the spare capacity of Runink’s shared hardware, the way spot capacity works on a public cloud. That is why it is the lowest price, and why it is the only plan that meters compute.
Dedicated runs PULSE’s work on runners in your own cloud account. The compute is on your cloud bill, so it is not metered in compute units. Runink adds a fee of 1% of those runners’ cloud cost. There is no node fee.
Enterprise is quoted to fit the deployment. On-premises runners carry no runner fee.
Compute units
A compute unit (CU) is one second of model-slot time: the time a request holds the model while it generates. 3,600 CU is one slot-hour.
- Lite includes 10,800 CU per seat per month, which is 3 slot-hours. The allowance is pooled: a 5-seat account has 54,000 CU to share.
- Past the allowance, Lite is billed $0.10 per 100 CU, in whole blocks of 100 CU. Work is never refused for going over.
- Dedicated and Enterprise are unmetered. The Billing page shows them as “unmetered”, never as a number, and they are never billed overage.
How PULSE records compute
- The model router measures the slot time of every generation and returns it with the response. PULSE records that exact figure, in milliseconds. Conversion to CU happens once, on the total for the period.
- Each record goes to the account that pays for the work, resolved from the signed-in person’s verified session. On an instance shared by several customers, each customer’s usage stays on that customer’s account.
- Each record carries an idempotency key, so a retried write never counts twice.
- A generation whose slot time was not measured records nothing, and is counted
in
pulse_metering_unmeasured_total. PULSE never estimates a charge. - Work that cannot be tied to a paying account is recorded under the platform
account, which is never billed. Each case writes an audit line and is counted
in
pulse_metering_unattributed_total.
Currency and billing periods
- There is one US-dollar price list. You are invoiced in your regional currency, converted with the European Central Bank euro reference rates.
- The rate for a month is the last ECB publication before the 1st. It stays fixed for the whole month.
- Seat prices round to a whole unit of your currency. Overage and fees round to the currency’s smallest unit.
- Billing periods run from your subscription’s start date (anniversary periods), not from the calendar month.
For how the numbers reach the Billing page of a deployment, see Billing.