Plans, seats and billing

A plan is the one thing in Plexus you can pay for — an optional monthly subscription on top of a free account — and it unlocks seven things:

• Cross-device sync — your settings, workspaces and projects following you to every machine you sign in on.
• Prompt templates saved to your account — a prompt you wrote on one machine, available on the next.
• The workspaces an organization shares — a workspace somebody in your organization set up once, with its repositories already attached, arriving in your sidebar.
• The settings an organization manages — a setting value somebody in your organization published once, recommended on your machines or enforced and locked there.
• The prompts an organization publishes — a prompt template somebody in your organization published as a numbered revision, in your template list beside your own and updated for everybody when the organization publishes the next one.
• The open issues of a project's tracker — a project's GitHub issues listed inside Plexus, fetched from your own GitHub account, each one a click away from a session that is linked to it — and the same for a Plnnrly project's work items, board and sprints, from your own Plnnrly organization.
• Stacks & ordered merging — sessions stacked on each other's branches and kept in sync, and a stack — or a list of pull requests — merged in order with one click.

The first two reach across your own machines. The next three reach across a team, and they are the ones a seat carries inside the organization that bought it. The last two reach nowhere but your git provider: they run between your machine and your own account, and they are the things on this list that are not a service we operate — a plan unlocks the fetching of the issue list and the automation of a stack, while attaching a tracker, the link a session carries, the Closes #123 line, basing a session on another session's branch and opening a pull request against any branch you like are free.

What a plan is

Not buying anything is the free plan, and it is where every install starts. On top of it there are two paid ones, both billed monthly:

• An individual plan belongs to your own Plexus account.
• An organization plan belongs to one organization and is billed per seat — you choose how many seats it has, and that is what it costs.

You can hold both. They are separate purchases with separate invoices, and deliberately so: a company name, a VAT number and an invoice address belong to the organization, not to whoever happened to press Buy. Putting them on one invoice would put a company's VAT number on a personal one.

Plans start immediately and renew each month until they are cancelled. There is no annual option, no trial, and no coupon to enter.

Prices are shown on the checkout page, in the currency and with the VAT that applies to you, before you pay for anything. The Billing page on the web panel shows the plan's current price too, read from the invoicing provider's own product rather than typed into Plexus, with VAT added at checkout. Plexus never quotes you a price it worked out itself — see Invoices, VAT and payment details.

Everything below lives on two Settings pages. Your own plan is the Plan row of Settings → My account. An organization's plan, its seats and its people are on Settings → Organizations, under Plan, seats and people: pick the organization from the organization picker at the top, and that row — like the rest of the page — is about that one. Picking it is also the moment Plexus goes and reads any of it; nothing about an organization is read until it is the one on screen.

Buying a plan

Buying always finishes in your browser, wherever you start it: the payment page is hosted by Moneybird, the accounting service we bill through, so the tab that opens is on moneybird.com.

1. Fill in the billing details first. Your company name, VAT number and invoice address are edited in the Plexus web panel (the Billing information form on its Billing page), not in the app — they end up on every invoice, and your country and VAT number are what decide the VAT.
2. Tick the acknowledgement. A plan starts the moment it is paid for, so the app asks you to say that out loud: "Start straight away. The plan begins the moment it is paid for, so the 14-day right to withdraw doesn't apply — you can cancel any time and it runs to the end of the period." The box starts unticked and the purchase is refused without it: in the app the Buy button does nothing until you tick it, and on the web panel it is in the Start your plan dialog that Subscribe opens. Our Terms set out what you are agreeing to.
3. Buy. Buy a plan for your own account, or Buy seats on an organization after setting the number you want — on the web panel the button is Subscribe, on a card that also shows the current price. A browser tab opens showing the plan, the price and the VAT for your country. Pay there — and if you pay by a method that supports it, the same step sets up the direct debit that collects later months automatically.
4. Come back to Plexus. A finished checkout has no way to tell the app it is done, so Plexus re-reads what it is showing whenever its window comes back to the front, and what the plan unlocks follows within seconds of the plan changing. Give it a moment after switching back rather than restarting the app — and if it still shows the old state, press the Reload button (the circular arrow) beside the plan's status: it asks the invoicing provider for the plan's current state right now. The web panel's Billing page has the same button as Refresh. The payment page itself sends your browser back to the web panel's Billing page, which checks the plan as it opens and says either "Payment received — your plan is active." or that the payment is still being confirmed; if what you bought was seats for an organization, it takes you on to that organization's Billing page.

While a purchase is being confirmed the status reads Waiting for confirmation; once it lands it reads Active — renews 18 Sep 2026, with the real date.

Seats

A seat is one assignable membership on a paid organization plan. It is not a device — those are Signed-in devices and they cost nothing — and it is not the same thing as being in the organization.

A seat reaches everything an individual plan reaches, so giving somebody a seat gives them cross-device sync on their own machines. Buying seats for a team is how a team gets it without everybody buying a plan of their own, and nobody pays twice.

A seat also reaches two things an individual plan cannot: the workspaces this organization shares and the settings it manages. Those are the capabilities a seat carries inside the organization rather than on the seat-holder's own machines, and they are why an organization with more members than seats has to choose who receives them.

What a seat does not give you is any sight of what that person syncs. Sync is attached to their personal account, never to your organization, so paying for the seat buys them the feature and shows you nothing — there is no admin view of it, by design.

That leaves an organization with two numbers, shown together as 2 of 5 seats in use: how many seats it pays for, and how many of those are assigned to members.

• More members than seats is normal. A member without a seat is a full member: they are in the organization, they hold their role, and they use Plexus exactly as they did before. No session, worktree, review, hook or pull request in the app refuses to work for want of a seat. What a seat adds is cross-device sync and saved prompt templates on that person's own machines — which someone holding their own individual plan already has — and the workspaces this organization shares and the settings it manages, which no individual plan can give them, because they are this organization's to hand out.
• Assigning is one button. In the people list, Give a seat hands a member one of the free seats and Take back seat hands it back. The count moves in the same breath, without a reload, because the app is told the new member row and the new seat count in one answer rather than counting them itself.
• Removing a member frees their seat. There is no second step to remember and no seat left stranded on someone who has gone.
• Changing how many seats you pay for is a different action, and a different permission: handing out a seat that already exists is an assignment, while changing the count is an invoice line, so the owner can grant one without the other. Set the number in the Seats field and press Update seats. Adding seats takes effect straight away and Moneybird raises a one-off invoice for the rest of the current month; releasing them lowers what you are billed from the next invoice onward. You cannot drop below the number currently assigned — the app says which people hold one rather than failing halfway.
• Zero is a legal number. Setting the count to zero is how an organization gives its seats up without being deleted; everyone stays a member, the app keeps working for all of them, and what they lose is sync between their own machines and any further updates to the workspaces this organization shares and the settings it manages. The workspaces they already joined stay on their machines, with everything under them, and a setting already enforced keeps its last known value — see What needs a seat, and what never stops and the same section for managed settings.

You can also end up with more seats assigned than paid for — seats can be released in the payment provider's own portal while people still hold them. The app says so plainly ("More people hold a seat than this plan pays for. Take one back, or add seats.") and nothing is taken from anyone in the meantime.

Inviting people

Invite someone takes an Email address and a Role. The app offers two of them — Member, or Admin — and the account panel on the web offers every role the organization has bar Owner, including Maintainer, Restricted and any role you wrote yourself. Owner is not a role you can hand out from either; every organization keeps the owner who created it, and handing one over is done against a member who has already joined.

What happens next:

• The invitation is emailed to that address and is valid for 14 days, single use. The link is in the email and nowhere else — it never appears on a screen, in a list or in an invoice.
• It shows in the people list as invitation pending, and it does not take a seat. Seats are for people who have actually joined.
• Remove on that row withdraws the invitation, and says so — "Withdraw this invitation?" rather than "Remove this person?". Sending the same invitation again (Send again) is in the account panel on the web.
• The person you invited needs a Plexus account of their own. The link in the email opens a page asking Join organization?, with Join and No thanks; joining adds them with the role the invitation carried.
• Giving them a seat is a separate step afterwards, and there is no rush: they can work without one.

Who may do which of these is decided by roles, and the line falls in a different place for the two halves. The plan is the owner's — buying it, changing how many seats it pays for, opening the billing portal, reading its invoices and cancelling it. The people and the seats already paid for are the owner's and the admins': inviting, removing, and giving or taking back a seat.

Anybody who holds neither sees the same state with the controls replaced by one line — "You do not have permission to change Acme's plan or seats." Plexus asks the account service what you are allowed to do rather than working it out from your role, and it asks on every request with nothing cached, so a role change takes effect the next time the page loads.

In the app, and in the browser

Plexus shows you the state natively and hands off anything that ends in a payment form or a PDF:

Buy and Manage billing are the two buttons that open your browser, and the account panel on the web can do all of it.

Invoices, VAT and payment details

Manage billing in the app (Payment method & invoice PDFs on the web panel's Billing page) opens the payment provider's customer portal — the same one-hour link rule as checkout, minted when you press it. From there you can change how you pay, update the mandate, and open every invoice the plan has raised, each downloadable as a PDF carrying the billing details you entered. Invoices are also emailed to the invoice address on the account.

You do not need the portal for the PDFs themselves. The Billing page lists every invoice, and each issued one has a Download PDF button on its row that saves the file straight from the panel, named after the invoice number. A draft has no number yet and no button.

We do not calculate your VAT and we do not store a rate. Moneybird derives it from the country, address and VAT number on the billing details, which is why filling those in accurately matters: a business in another EU country with a valid VAT number is invoiced at 0% under the reverse charge, a consumer is invoiced at their own country's rate, and outside the EU no VAT is charged. If the VAT shown at checkout looks wrong, fix the billing details before paying rather than after.

If a payment fails

The usual causes are an expired card or a mandate cancelled at your bank, both fixed under Manage billing. A plan only ever ends by being cancelled, or by an invoice being written off as uncollectible after every reminder has gone unanswered — and even then the app keeps working exactly as it does now.

Cancelling a plan

Cancel with Cancel plan on the web panel's Billing page, or from the customer portal under Manage billing. The plan then reads Cancelled — ends 18 Sep 2026 and runs to the end of the period you have already paid for: seats stay assigned and the people list is untouched. A cancellation cannot be taken back, so once the plan is cancelled the Billing page offers no second Cancel plan and no Resume — when the period runs out, Subscribe starts a fresh plan.

On the day it lapses, the only things that change are the five a plan unlocks: your machines stop sending and receiving cross-device sync and Settings → Sync goes back to showing what the feature does and how to get it; the prompt library stops saving new templates to your account; the workspaces your organization shares stop updating; the settings your organization manages stop arriving, while every enforced value already on a machine keeps applying; and the prompts it publishes stop arriving, while every one already on a machine keeps listing and running. Every setting, workspace, project and session on every machine stays exactly as it is, nothing is deleted from your account, and starting a plan again picks up where it left off.

Deleting your Plexus account cancels any plan it holds. You have to delete or hand over the organizations you own first, which the panel tells you up front — see Deleting your account.

Next: Cross-device sync for the one thing a plan unlocks, Roles and permissions for who in an organization may do any of this, Your Plexus account for organizations, devices and what leaves your device, or the Privacy Policy and Terms for the full picture.