Ruba product infrastructure

Bill the team. Deliver access to each member.

Separate the person who pays from the people who claim product access.

One billing manager purchases capacity, then assigns it to teammates. Ruba keeps quantity, invitations, claims, benefits, and proration connected.

Architectural boundaries

The buyer and the member have different jobs

Billing manager

Chooses the paid seat quantity
Assigns, resends, or revokes invitations
Changes subscription quantity and receives prorated adjustments
Does not consume access unless assigned a seat

Seat recipient

Receives an email or external-ID assignment
Claims the individual seat
Receives product benefits only after claim
Loses those benefits if the assignment is revoked

Capability matrix

Choose the commercial contract

Recurring team plan

Quantity can change

The subscription stays aligned with the active team and applies proration when paid quantity moves.

Perpetual team license

One-time grant

A claimed seat keeps its benefits; additional capacity is purchased through another order.

Capability matrix

Price the quantity in one of three ways

Fixed per seat

One rate

Every seat uses the same unit amount.

Graduated tiers

Each range keeps its rate

The total combines the quantity billed inside every tier range.

Volume pricing

One rate from total quantity

Crossing a threshold applies its rate to every seat in the purchase.

Execution workflow

Follow a seat from assignment to reuse

01
Assigned
The manager selects an email address or external customer ID.
02
Pending
An invitation exists but the recipient has not accepted it yet.
03
Claimed
The member accepts and Ruba grants the product benefits.
04
Revoked
Access is removed while the paid slot remains available for reassignment.
05
Quantity reduced
The paid seat count falls and the unused cycle portion receives a credit.

Claim links

Onboard recipients from email or your own member flow.

Prorated quantity

Charge additions and credit reductions within the current period.

Customer Portal

Let billing managers administer their team directly.

API and webhooks

Drive assignments and synchronize product permissions.

Connect seat events to your permission model

List and mutate assignments through the API. React to seat.claimed, seat.revoked, and subscription.updated without polling Ruba for changes.

A subscription supports up to 1,000 seats and arbitrary seat metadata. Seat-based pricing is currently beta and can be enabled from Settings → General → Features.

Build with Ruba

Create a team product

Choose the contract and pricing model, then let customers assign access.