​

Billing

The Billing section lets administrators manage their organization’s subscription, view usage against plan limits, and update payment information.

​

Plans

Neural Factory SaaS offers two plan types:

​

Viewing usage

The billing dashboard shows:

• Current plan — Your active subscription plan
• Billing period — Current billing cycle dates
• Usage — How much of your plan limits you’ve used:
  • Messages sent
  • Documents indexed
  • Storage consumed
  • API calls made
  • Tokens consumed by agent tasks

​

Agent task billing

Each turn you send runs as an agent task on the server, and it is billed for the model tokens and tools it actually consumed. Three consequences are worth knowing:

• Closing the tab doesn’t stop the meter — or lose the answer. The task keeps running server-side, its result is saved to the conversation, and it is billed once. Leaving the page neither cancels the work nor avoids the charge.
• Stopped and failed tasks still bill for work already done. Stopping is the right move when a task is going nowhere, but it refunds nothing already spent.
• A task is billed exactly once. Reconnecting, reloading, or watching the same task from several places doesn’t multiply the cost. Sending the same message again, however, starts a second task with its own bill.

​

Managing your subscription

​

Upgrading your plan

1. Navigate to Billing in the sidebar
2. Click Upgrade Plan
3. Select the new plan
4. Confirm and update payment if needed

Upgrades take effect immediately. Usage limits are increased right away.

​

Updating payment

1. Navigate to Billing
2. Click Payment Method
3. Update your card or payment details

Payment is processed through Paddle, our payment provider.

​

Cancelling

1. Navigate to Billing
2. Click Cancel Subscription
3. Confirm the cancellation

Your access continues until the end of the current billing period. After that, your organization enters a read-only state.

​

Usage limits

When you approach or reach a plan limit, you’ll see warnings in the interface. If a limit is reached:

• Message limit — Users cannot send new messages until the next billing cycle or an upgrade
• Storage limit — New document uploads are blocked
• API limit — API calls return rate-limit errors
• Parallel agent tasks — Starting another task is refused until one of the running tasks finishes

The first three are quota limits: they measure consumption over the billing period and reset when it rolls over. The last is a concurrency limit — a ceiling on how many agent tasks one user (and, for organizations, one organization) may have running simultaneously. It doesn’t accumulate and it doesn’t wait for the billing cycle: it clears the moment a running task finishes. Tasks paused waiting on a person don’t count toward it. Because a concurrency limit is hit at the moment of sending rather than approached gradually, users see it as an error on send — “You’ve reached your limit of parallel agent tasks” — with no advance warning. If your users hit it often, raise the allowance with an upgrade rather than treating it as a fault. Monitor the billing dashboard regularly and upgrade proactively to avoid disruptions.