📊 Plans and Limits

Every organisation is on a plan. The plan sets how many seats, robots, apps, app users and live-video hours you have, how long history and the audit log are kept, and which features are open to you. Basic costs nothing, and Pro can buy more of what it includes.

The console’s Plan & billing page shows the plan you are on, and Usage & limits shows what you have used against each limit and what would lift it.

An upgrade, an add-on or a change of payment method is paid on Mollie’s checkout, and every charge gets its own invoice. The owner starts it from the console; see Paying.

The plans

Prices are in euros for organisations billed in the EU and in US dollars elsewhere. The dollar price is the euro price times 1.15, rounded up to the next whole dollar. Prices exclude VAT for companies; persons see them with VAT where VAT applies.

Yearly billing takes 15 % off twelve months: Plus is 295,80 € ($341) a year, Pro is 1.519,80 € ($1,748) a year.

Enterprise means your own instance or region, SSO and SCIM for developers, a data processing agreement and an SLA. It is sold on request.

Add-ons

Add-ons exist on Pro only. On any other plan they count as zero, and moving off Pro sets them to zero.

What is counted

The limits count across the whole organisation, not per app.

• Seats are developers, owners included, plus pending team invitations.
• App users are the app users of every app, plus pending app-user invitations.
• Live video is this UTC calendar month’s live video of app users. A console session never counts.
• Asset storage is the sum of the assets of all your robots, measured against the robots times the per-robot allowance.

Not limited and not billed: API calls (shown as usage only), the history you store in gigabytes (only the number of days is limited), and the live video you watch in the console.

At a limit

A request that would pass a limit is refused before anything is written, with 409 plan_limit. The refusal names the limit, what you have used, the ceiling, and what lifts it: the next plan up, or the add-on that raises this limit on your plan. Nothing is charged automatically.

Refused requests write nothing, so you can retry once you have freed room or changed the plan.

Live video works differently once it is running. When the month’s total reaches the limit, an app user’s live session ends, and the viewer is told that the live video limit of the plan is reached for this month. The next session cannot start either, and console sessions are never ended by it.

Features the plan does not have

Some features need a plan. Using one below that plan is refused with 403 plan_required, which names the feature, your plan and the cheapest plan that has it. The gated features are:

• MCP for app users, and the app’s MCP endpoint;
• identity providers (OIDC) for an app;
• a hosted logo on an app’s pages;
• two-factor for developers, and requiring it for the organisation;
• the audit log CSV export.

Keeping history and the audit log

Each plan keeps history and the audit log for its number of days, shown in the table above. Fleetless purges older entries automatically, so an entry older than that is gone.

Moving to a smaller plan

A downgrade or a cancellation that would put you over the limits of the plan you are moving to cannot go through as it is. The owner first chooses what stays on the Choose what stays on <plan> page:

• per kind, up to the target plan’s limit: robots, apps, app users and developers;
• nothing is ticked in advance; a helper per list only ticks the entries you name (the people who signed in last, for instance);
• the owner always stays and is never in the choice.

Everything you do not choose is deleted for good when the period ends: a robot with its configuration, history and assets; an app with its roles and app users; a developer’s membership. The history older than the target plan’s days is deleted for what stays too, so export what you need first. The page asks for the organisation’s name typed out before it saves the choice.

Until the period ends you can change the choice or withdraw it with Keep <plan>, and the deletion does not run before then. Within the target plan’s limits no choice is needed: cancelling then only tells you that the history will be shortened.

Paying

Payment is Mollie’s hosted checkout, so no card or bank details reach Fleetless. You pay by credit card, PayPal or Apple Pay, in euros or US dollars. Fleetless takes no SEPA direct debit.

The owner chooses who the payer is: a company (name, country and VAT ID) or a person (full name and country). Who may pay, and the VAT:

Fleetless never charges another EU country’s VAT. Companies see net prices and a VAT line; persons see gross prices. Pro costs 149,00 € net for a German company, which is 177,31 € with 28,31 € VAT; a German person pays 177,31 €.

The currency is fixed at the first payment: euros when the billing country is in the EU, US dollars otherwise. It does not change afterwards.

Apple Pay is charged like the card behind it. Mollie stores an Apple Pay payment as a card, so renewals and prorated charges are charged to that card, and the console shows the payment method as Apple Pay.

Changing the payment method is a payment of 0,00 € on Mollie’s page in the organisation’s currency. It pays no open invoice.

Billing periods

The billing period starts on the day of your first payment. Yearly billing is twelve months at 15 % off.

Each renewal is charged to the payment method on the same day of the month. In a month that is shorter than that day, the renewal falls on the last day of the month: a period that started on the 31st renews on 28 February and then on 31 March. The period date does not move, except when you switch from monthly to yearly.

Changes within a period

A change takes effect at once or at the period’s end, depending on whether it increases or reduces what you pay.

Amounts are rounded to the cent, before VAT. VAT applies to each charge, and each charge has its own invoice. Two examples: a robot bought on day 10 of a 30-day Pro month costs 19 € × 21 ÷ 30 = 13,30 € for the rest of the month; on a yearly plan, the same robot bought 100 days before the end of the period costs 193,80 € × 100 ÷ 365 = 53,10 €.

Invoices

Every charge is an invoice. Its number is FL-<year>-<n>, for example FL-2026-0142, counted per calendar year and without gaps.

The invoice shows the seller, the payer, the VAT and, where it applies, the reverse-charge note. You find the invoices and their PDFs under Plan & billing, and each payment is confirmed by email with its invoice attached.

While VIES does not confirm the VAT ID of a company in another EU country, a renewal is held back: it is a charge without an invoice number, because its VAT depends on the VAT ID. Once a valid VAT ID is entered and the charge is paid, the invoice is issued. Until then the renewal counts as a failed payment for the reminders and the lock below.

Failed payments

When a renewal or a prorated charge fails, its invoice stays open and Fleetless retries the charge on the third and the seventh day after it was due. The owners and the invoice email are told each time, and the console shows a banner.

On the fourteenth day the organisation is locked: bridges and every sign-in except the owner’s are refused. Nothing is deleted.

The owner then either pays the open invoice with Pay now, which unlocks the organisation and keeps the plan to the end of the period, or chooses what stays on Basic, which lifts the lock as described under Moving to a smaller plan. A payment that arrives after the lock unlocks the organisation.

When the organisation falls back to Basic because a renewal was not paid, its open invoice is cancelled with a cancellation invoice, and nothing more is collected. A renewal held back for the VAT ID lapses without an invoice. Basic shows no open invoice.

Chargebacks

When a card issuer or PayPal reverses a payment (a chargeback or a lost dispute), its invoice is open again. Fleetless does not charge the payment method for it again on its own: the owners and the invoice email are told, the console shows the banner with Pay now and Change payment method, and the organisation is locked on the fourteenth day after the chargeback unless the invoice is paid.

Cancelling

Cancelling takes effect at the end of the period. Nothing is refunded.

Within Basic’s limits, cancelling only tells you that the history will be cut to Basic’s 7 days. Over Basic’s limits, cancelling is possible only through Choose what stays on Basic, as described under Moving to a smaller plan. Until the period ends you can withdraw it with Keep Pro.

Locked organisations

An organisation can be locked. A locked organisation refuses bridges and every sign-in except the owner’s, and nothing is deleted.

The lock lifts when the open invoice is paid with Pay now, or when the owner chooses what stays on Basic. A failed payment locks an organisation on its fourteenth day (see Failed payments); the move to Basic described next locks it too, until the owner chooses.

Moving to Basic

When plans start, every existing organisation is moved to Basic. Fleetless tells the owners by email and by a banner in the console 30 days before the switch date. An organisation within Basic’s limits needs no choice.

One over them chooses what stays on Basic, or upgrades, before the switch date. One that has done neither is locked until it does. History and the audit log are cut to Basic’s 7 days at the switch date either way, and the same mail and banner say so.

Next

• Sign-in and Two-Factor — the two-factor options each plan has.
• Create an App — the OIDC providers and the hosted logo and accent colour, which need Plus.
• API reference — the plan errors and the /api/org/plan routes.