Plans and limits
Your plan, usage, credit balance and any open notices are on the Billing tab of org settings. Current prices are on sloose.com/pricing.
This page explains what each limit does.
What the tiers are banded on
Section titled “What the tiers are banded on”Three things you can see and we can count: the systems you connect, how many imports you run each month, and how big one import can be.
Not how many people use Sloose. Everybody in the org can use it on every plan — the seat count is not what you are paying for. And not how many rows you write in a month: imports run in your browser, so that number would be your browser’s word, and we would rather not bill on it. Rows per month applies to server-run imports only, when those arrive.
| Free | Team | Business | Enterprise | |
|---|---|---|---|---|
| Connectors | 1 | 2 | 5 | unlimited |
| Import runs per month | 5 | 50 | 500 | unlimited |
| Rows per import | 500 | 10,000 | 100,000 | 500,000 |
| Modules | 1 | 3 | unlimited | unlimited |
| AI credits included | 0 | 300 | 1,500 | 5,000 |
| History kept | 7 days | 30 days | 365 days | 365 days |
| Sandboxes | 0 | 0 | 1 | 2 |
| CRM users up to | 3 | 10 | 50 | unlimited |
| Schedules | 0 | 0 | 5 | 5 |
| Rows per month (server-run imports) | 1,000 | 10,000 | 100,000 | 500,000 |
| Row overage per 1,000 (server-run) | — | $2.00 | $1.50 | $1.00 |
Features by plan
Section titled “Features by plan”| Free | Team | Business | Enterprise | |
|---|---|---|---|---|
| Shared projects | · | ✓ | ✓ | ✓ |
| Helper libraries | · | ✓ | ✓ | ✓ |
| Server-run imports | · | · | ✓ | ✓ |
| Scheduled imports | · | · | ✓ | ✓ |
| MCP (agents) | · | · | ✓ | ✓ |
| Rollback | · | · | · | ✓ |
The limits, one at a time
Section titled “The limits, one at a time”Connectors
Section titled “Connectors”The systems your org is connected to. Your Zoho CRM is one; a sandbox CRM is counted separately
under Sandboxes. CSV files you upload are not connectors and never count. Connecting past the
plan’s number is refused with LIMIT_CONNECTORS.
Import runs per month
Section titled “Import runs per month”An import run counts when it writes its first row. Everything is checked once, when the run is
authorised, so a run that starts always finishes. Things that never count: dry runs, retries of
failed rows within a run, a run you cancel before it writes anything, and a browser tab that is
lost. When the period’s runs are used up, a real run is refused with LIMIT_RUNS; dry runs keep
working, and the Billing tab shows how many runs are left.
A sandbox has its own runs, a tenth of the plan’s, so testing never eats production runs. Enterprise runs are unlimited under fair use.
Rows per import
Section titled “Rows per import”The most rows one import set may contain. Checked against the file you have already loaded, before
anything is written, and refused with LIMIT_ROWS_PER_RUN. Split the file, or narrow the row range
on the Import step, or move to a plan with a larger set.
CRM users — a warning, never a block
Section titled “CRM users — a warning, never a block”Measured from the last discovery: how many active users your CRM has.
If that exceeds your plan’s band you get a warning to upgrade at renewal. Nothing stops working. A fifty-seat CRM where two people import is still a fifty-seat CRM, and we would rather tell you than break your import over it.
Modules
Section titled “Modules”How many modules can be enabled at once. Enabling one beyond the cap is refused with
LIMIT_MODULES — disable one you are not using, or upgrade.
Schedules
Section titled “Schedules”How many schedules an org can hold. Zero on Free and Team. Note that schedules are stored but not yet executed.
History
Section titled “History”How long run history is kept before it is retired automatically. History records what happened, never your data.
Row overage
Section titled “Row overage”Server-run imports only, and only on plans that price it. A browser import is never refused on rows per month and never billed overage — its rows are counted on the Billing tab for your own information. When server-run imports arrive, overage will be off by default: a run that would exceed the monthly allowance is refused, or, switched on, written and billed per thousand beyond the allowance.
The trial
Section titled “The trial”A new org starts a Business trial on first sign-in. Once per org and once per billing account, so a second org on the same account does not get a second trial.
When it ends, the org falls back to Free — nothing is deleted, but limits tighten and features above Free stop being available.
Past due and suspended
Section titled “Past due and suspended”When a payment fails, the subscription goes past due and a grace period starts. Everything keeps working, and you get a notice you cannot miss.
If the grace period ends without payment, the org is suspended:
- Reads keep working. You can sign in, look at your configuration, read your history.
- Writes do not. A run is refused with
STATUS_SUSPENDED.
Nothing is deleted while suspended. Settling the account restores it.
What a refusal looks like
Section titled “What a refusal looks like”Every limit and status refusal carries a code from a closed set, so a client can act on it rather than parsing a sentence:
LIMIT_RUNS, LIMIT_ROWS_PER_RUN, LIMIT_CONNECTORS, LIMIT_ROWS (server-run imports),
LIMIT_MODULES, LIMIT_SCHEDULES, LIMIT_CRM_USERS, LIMIT_SANDBOX, FEATURE_*,
CREDITS_EXHAUSTED, STATUS_SUSPENDED, STATUS_PAST_DUE.
Each is listed with what to do about it in Error codes.
Changing plan
Section titled “Changing plan”The Billing tab lists every plan you can move to, with what each includes. Choosing one opens Stripe Checkout in a new tab; you come back to a page that confirms what changed.
Upgrades take effect immediately. Downgrades take effect at renewal, and the tab shows the scheduled change in the meantime.
Two things the tab is honest about rather than hiding:
- A plan is only offered when it can actually be sold here. Monthly and annual are listed separately, and each appears only once its Stripe price exists on this deployment.
- Enterprise is billed by invoice, so it does not go through Checkout at all.
Manage billing opens the Stripe customer portal, which is where a card is changed, an invoice downloaded, or a subscription cancelled.