Skip to content

Billing

Settings → Subscription (/settings?tab=subscription) is the shared Runink billing page from org-runink/ui. It is its own tab, beside Account and never inside it: plan, seats, usage and purchases live here and nowhere else, and the Account tab shows none of them. PULSE serves its API, runink.ui.billing.v1.BillingService, over the org-runink/billing library, with PULSE-specific hooks. The page lists and prices PULSE’s own plans, never another product’s. For the plans, prices, and the trial’s daily task limit, see Plans.

Where the subscription comes from

PULSE runs one deployment per tenant. The subscription is read from environment variables that Runink TIDE’s operator projects onto the pod:

VariableMeaningWhen missing
TENANT_IDThe tenantNo subscription on record
SUBSCRIPTION_TIERThe plan tier: trial, cloud, or on_premises. A value written before 2026-11-12 (lite, dedicated, enterprise) is migrated on read and logged.trial
SUBSCRIPTION_SEATSNumber of seats1
SUBSCRIPTION_STATUSSubscription statusactive
SUBSCRIPTION_PERIOD_ENDEnd of the current billing period (RFC 3339)No period shown
SUBSCRIPTION_ANNUALtrue for a yearly subscriptionMonth-to-month

The tier, seat, and status defaults apply only when TENANT_ID is set. Without TENANT_ID, the tab shows that no subscription is on record. It does not invent a plan. A subscription whose SUBSCRIPTION_STATUS is not active, trialing, or past due grants nothing: it is shown as suspended, never degraded to a free tier.

The page derives the current period from SUBSCRIPTION_PERIOD_END, running from your subscription’s anniversary date. With no period on record, it shows no period and prices the month-to-month rate. A Dedicated plan is sold yearly only.

Several purchasers on one instance

On an instance shared by several customers, RUNINK_ACCOUNTS_FILE (the member-to-purchaser file TIDE’s operator projects) maps each signed-in person to the purchaser who pays for their seat. A purchaser’s own row sets their plan and seats, so a TRIAL purchaser’s seats get the daily task limit and a Dedicated or Enterprise purchaser’s do not. People with no row fall back to the instance’s SUBSCRIPTION_* variables.

Where the daily task count is kept

The trial’s daily task count lives in the usage bucket TIDE’s operator gives the pod (RUNINK_USAGE_*), as append-only records. When a deployment has no usage bucket, as in local development, tasks are not counted and the page says that daily usage is not tracked on this deployment.

What each part of the page does

FeatureIn PULSE
Plan catalog and price quotes (ListPlans, QuotePlan)Work. Pricing is arithmetic, done on the server, from PULSE’s catalogue.
Overview of your subscription (GetOverview)Works, from the variables above.
TodayOn a trial, “Today: X of 10 fast tasks” for the viewer’s seat, and the reset time once the limit is reached. Cloud and On-premises show no daily count.
EstimateEvery line is either computed or says why it cannot be.
CurrencyThe page shows US-dollar list prices and says so. Invoices are in your regional currency; see Currency and billing periods.
Checkout and the billing portal (StartCheckout, OpenPortal)Subscriptions are bought through Runink, so both answer “not configured” and nothing on this page can charge.
Seats (ListSeats, AssignSeat, RevokeSeat)Seats come from the subscription; the page shows no seats section.

Billing actions are logged to the process log as billing audit lines.