Software Factory
Administration

Usage & Billing

Manage seats, track organization token usage, and handle billing.

Organization Admins manage seats, track usage, and handle billing from Settings → Organization.

Seats

8090 Software Factory offers two seat types:

SeatPriceBest for
Full$200 per seat / monthMembers and Admins who create and edit across the modules their project role allows.
View$0Stakeholders who only need to view and comment.

Full and View seats are separate pools with separate counts. Change either count from Settings → Organization → Members under Manage → Manage Seats. View seats cost $0, but you still add them in Manage Seats before you can invite someone with the View role. Seat changes are prorated on your next invoice.

A pending invitation holds a seat. Expired and revoked invitations release it. Manage Subscription, in the same menu and under Settings → Organization, opens your subscription in Stripe. Enterprise organizations are billed under their agreement and have no seat limit.

Included usage

Each active member on a Full seat adds a monthly included usage allowance to the organization's shared pool. A member who joins partway through a billing period adds their allowance when they join.

Seats that are purchased but not filled add nothing, and neither do pending invitations or View members. Unused allowance does not carry over to the next billing period. Included usage applies to self-serve plans. On Enterprise plans, usage is covered by your agreement.

Usage

Open Settings → Organization → Usage to see token consumption and cost across the organization. Only organization Admins can open this page.

  • Choose how to Group the table: Project, User, Agent, or Model.
  • Set a Start Date and End Date. The range starts at the current billing cycle by default.
  • Search the table, open a row's breakdown for detail, and select Export CSV to download it.

When you group by User, usage that no person started is combined into one Background Agent row.

On-demand usage

Usage beyond the included allowance is billed as on-demand. Self-serve organizations see an Included Usage meter and an On-Demand Usage meter at the top of the Usage page.

The on-demand limit defaults to 0, so agent usage stops at the included allowance until an Admin raises the limit with Set On-Demand Limit. When the organization reaches its limit, agent requests stop with a message to contact an organization Admin.

Per-user limits

Members have no individual limit until an Admin sets one. To cap one member's usage, use Configure Usage Limit in that member's row on Settings → Organization → Members. Admins see each member's Usage and Limit in the Members table. On Enterprise plans, the Usage page also shows how many members have a limit.

Automations run as the person who created them, so their usage counts toward that person's limit. When the person reaches their limit, their automations stop as well.

How you're charged

Every agent request is metered by the token counts the model provider reports, and each count is multiplied by that model's rate per one million tokens. Self-serve plans add a 20% platform fee on top. Enterprise agreements set their own terms. The Usage page reflects what you pay. Rates for every model, including long-context and US-hosted rates, are on Model Pricing.

Continue to Model Pricing.

On this page