Use Plan to manage your subscription, usage balance, payment method, and invoices. Your seat subscription pays for Para itself; usage pays for the services Para uses to carry out work, drawn at cost from a prepaid balance. See Usage for what consumes your balance.
Getting started
There is no free trial. Para needs a plan and a usage balance before it starts any work. In the welcome screens an organization administrator first invites the people who will use Para, then pays for seats and a starting usage balance in one checkout; the Plan page offers the same checkout. Checkout is hosted by Stripe and Para never sees the card number. Seats start on Standard, which runs Core Lightning; choosing a model comes with a Pro seat or Enterprise. Each invitation becomes a seat when it is accepted. Until an organization has a plan, new assignments are refused and Para’s reply links to the Plan page.
Plans and seats
| Plan | Includes | Billing |
|---|---|---|
| Standard | Your own Para for every seat, every channel, projects, automations, skills, and meetings, running on the Core Lightning model. | Monthly, per seat. |
| Pro | Everything in Standard, plus the choice of any model, including frontier models such as Claude Opus, and direct support from the CaseMark team. | Monthly or annual, per seat, where annual billing is offered. |
| Enterprise | Everything in Pro, plus company single sign-on, your own AI provider keys, and a signed agreement. | Seats and usage on one annual agreement. |
Seats are per person, and you can mix tiers: choose who gets Pro and leave others on Standard. Checkout bills a seat for everyone currently in the organization. People who join later are added on Standard with a prorated charge. Annual billing puts every seat on Pro. Prices are shown on Plan. For company sign-in, enterprise agreements, and BAA eligibility, see Enterprise.
After you subscribe
Usage is prepaid, and checkout includes the starting balance. Once Stripe confirms the payment, usually within a minute, the balance appears on Plan and on-demand usage is on. Unless you unticked it at checkout, Para adds the same amount again whenever the balance runs out; change that amount or set a monthly limit on Plan. Later top-ups never change those settings.
Usage balance
Your organization shares one prepaid balance. Reported service costs reduce it at cost, with no markup. An administrator can select Top up now at any time, turn on automatic top-up (a fixed amount charged to the card on file whenever the balance runs out), and set a monthly spending limit for the organization. New assignments need an active subscription, on-demand usage turned on, money in the balance, and room under any spending limit. Costs can arrive after work finishes, so the balance is not a live meter. See Usage for examples and spending controls.
Enterprise organizations have no usage balance. Usage is covered by the enterprise agreement, so Plan shows no balance or top-up controls, and administrators set only per-person spending limits on Team.
Low-balance and spending-limit emails
Para emails the organization’s owners and administrators before it stops for money. These are the only billing warnings it sends:
- Low balance: on-demand usage is on, automatic top-up is off, and the balance falls below 20% of the most recent top-up, or below $10 when no top-up has been recorded. The email states the remaining balance.
- Spending limit: spending this billing period reaches 80% of the organization’s monthly limit. The email states how much has been spent against the limit.
Each email links to the Plan page and is sent once per crossing. The low-balance email can come again only after a new top-up; the spending-limit email can come again in the next billing period or after the limit changes. Each one sent is recorded in the Audit log. With automatic top-up on, the balance refills itself, so there is no low-balance email.
Who sees what
Owners and administrators see the usage balance, invoices, and everyone’s spending and limits on Plan, Usage, and Team. Members see their own spending and personal limit for the current period: on Plan under Your usage, on Usage, and on their own row of the Team table. Members don’t see colleagues’ spending, the organization’s breakdowns, or the balance.
If a payment fails
If Stripe can’t collect a subscription payment, Para pauses new work for the organization and Plan shows a banner. Administrators select Update billing to fix the card in Stripe, and Para takes new work again once the payment goes through. Members see that Para is paused until an administrator updates billing. If an automatic top-up fails, Plan says why, for example that the card was declined, under Usage balance.
Payment and invoices
Under Billing & invoices, administrators use Manage beside Payment method to update the card in the Stripe portal. Invoices are read-only here; open any invoice for its Stripe receipt. Recent usage can be exported to CSV. The usage balance and invoices appear once you have a paid plan, and only administrators see them.