Plans & billing

Your plan sets this account's hard limits — how many runners connect, how many people you can invite, how long the audit log is kept, and which features are on. Billing runs on Paddle; you manage it from the Billing page under Settings.

Plans and limits#

emisar has three plans. A new account is on Free until someone upgrades it, and the plan comes from your subscription — there's no separate plan switch on the account to drift out of sync. Each plan sets three hard limits.

Free is free and stays free — no card, no time limit. Team is billed per connected runner, monthly or annually, with annual running about two months cheaper than paying by the month; the checkout starts from the number of runners you're running now. Enterprise is a custom, sales-led plan with tailored limits. For the current per-runner price, compare the plans.

What each plan unlocks#

Beyond the limits, a few features are gated by tier. Free keeps the full product — the console, the audit trail, policies, approvals, runbooks; the paid tiers add the pieces most teams need once more than one person is in the account.

• — Single sign-on. OIDC sign-in through your identity provider. See single sign-on & SCIM.
• — Audit export. Every plan keeps the full audit trail in the console; taking the data out — the CSV download and the streaming NDJSON API a SIEM reads — is the paid surface. See audit & SIEM.
• — SCIM directory sync. Provision and deprovision members straight from your directory. Enterprise also includes a security and procurement review, deployment planning, and rollout support, set up with our team.

When you reach a limit#

The runner and member caps are enforced when you add the next one, not retroactively — so a plan never silently disables something you already have.

• — Runners. Enrolling a runner past your plan's cap is refused — the new host's registration fails with an over-limit error instead of half-joining. Runners already connected keep running and keep executing actions.
• — Team members. Inviting a member past the cap is refused the same way (Free allows one, so the second person needs Team); people already in the account keep their access.
• — Watch it before you hit it. The Billing page shows live usage against each cap — a runner meter and a member meter that turn amber as you approach the limit — so you see the wall coming rather than discovering it when the next install fails.
• — Audit retention is a cap too, but a duration rather than a count — events older than your plan's window are pruned. It behaves differently on a plan change; see below.

Upgrading and downgrading#

Anyone in the account can open the Billing page and read the plan, usage, and invoices. Changing the plan, updating the card, or cancelling needs the account owner or a member with the billing-manager role. Admins and operators see billing but can't change it. More on roles.

To upgrade, open Settings → Billing, pick Monthly or Annual, and choose a plan. Checkout opens in a Paddle overlay on the page; once payment clears you land back on Billing and the new plan — and its higher limits — take effect within a moment, as soon as Paddle confirms the charge.

Downgrading or cancelling isn't a checkout — that would open a second subscription. Use Manage billing to open the Paddle customer portal, where you can switch to a lower plan or cancel. Cancel, and the Billing page shows a "Cancels on …" note: you keep the plan through the end of the period you've already paid for.

Invoices and payment method#

Your recent invoices show right on the Billing page — date, amount, number, and status, each with a PDF download — so checking the last charge doesn't mean leaving the console.

For everything else — your full invoice history, the payment method on file, your billing address and tax details — open Manage billing. That's the Paddle customer portal; Paddle is emisar's merchant of record, and it owns the complete ledger and your card.

Manage billing appears once your account has a Paddle customer — that is, once you've been on a paid plan. On Free there's nothing to manage yet, so the button waits until your first upgrade.

If a payment fails#

A failed renewal doesn't lock you out. Paddle retries the charge on its dunning schedule and emails the billing contact, and through that window your plan and its limits keep working — emisar treats billing status as advisory and won't cut a running fleet off mid-cycle over a declined card.

To fix it, open Manage billing and update the payment method; the next retry settles the balance. If you actually mean to stop paying, cancel in the portal rather than letting a card lapse — cancelling ends the plan cleanly at the period you've paid through, instead of leaving it stuck in retry. Every plan change is written to the audit log.

Plan changes and audit retention#

Each audit event's retention horizon is fixed when the event is written, from the plan you're on at that moment — 7 days on Free, 90 on Team, 365 on Enterprise. A plan change only affects events written after it. So upgrading keeps more of your new history, and downgrading shortens the window for new events but never retroactively deletes the history you already have. Retention prunes run daily, and both the plan change and every prune are recorded in the audit log itself.