Billing

Billing is managed per billing owner — your personal account, or an organization you own or administer. You manage it in Settings → Billing; if you manage an organization, a context switcher lets you view its billing separately from your own.

The top of the page shows your credit balance, with any credits on hold for operations still running and the date your next credits expire, beside your plan and two buttons: Get more credits with Manage plan if you pay for a plan still on sale by card or direct debit, or with Your plan for any other plan; on a free trial or with no plan, See plans comes first, then Get more credits. The rest of the page is on tabs:

• Overview — where your credits come from, by grant source, and your plan; on your personal billing, what covers you under Covered for you; and, for an organization you administer, a summary of its team.
• Plans — your plan and the plans you can choose, with their prices, your free trial, and plan changes.
• Get credits — Need more credits?, which weighs top-ups, a larger plan and launch credits against what you plan to do over the next year, and the Top-ups packs.
• History — Recent usage and Recent billing activity, and, on your personal billing, the credits still settling from recent actions.
• Team — for an organization you administer: Spending caps and seats, Credit delegation rules and Member credit usage.

What things cost, beside the tabs (at the foot of Overview on a phone), opens a list of what each action costs in credits.

Free trial and plans

• Free trial — you get one, and so does each organization. Starting it saves a card with Stripe; the card is not charged and nothing renews on its own. It includes 250 credits for 30 days, one community and up to 200 profiles in it. The Plans tab shows Free trial — N days left, and when it ends its remaining trial credits expire.
• Plans — subscribe through Stripe checkout; manage or cancel in the Stripe Customer Portal from the same page. Organization plans are bought from the organization's own billing, so your personal billing does not list them: while one is on sale, a line under your plans says to choose the organization at the top of the page or, if you administer none, links to Create an organization, which brings you back here with the new organization selected.
• Top-ups — buy a pack of extra credits from Top-ups on the Get credits tab. You can top up your personal balance at any time. An organization can buy them only while it has a plan or a free trial, since it could not spend them until then.

The plans come in four kinds:

• Free — nothing to pay and no card. A verified account that was active the month before gets 5 credits a month, which expire at the end of the month. It cannot own a community.
• Plus — 60 credits a month, for searching regularly without a community of your own.
• Pro — from 200 credits a month (Pro 200) to 10,000 (Pro 10K), with communities of your own: up to 5 on Pro 200, up to 10 on Pro 500, and as many as you like from Pro 1K up.
• Organization — from 200 credits a month (Org 200) to 50,000 (Org 50K) in one shared wallet, with up to 5 communities on Org 200 and as many as the organization likes from Org 500 up, and from 5 to 1,000 seats.

Paid plans are billed monthly or once a year, upfront. On annual billing, a Pro or Organization plan gives the whole year's credits at once, at the start of each year: twelve times its monthly credits (2,400 on Pro 200), ready to spend whenever you need them. They last until the end of that year and do not roll over. If you run out before then, upgrade your plan or buy a top-up. Plus gets its credits month by month on annual billing too, as every plan does on monthly billing, and credits that come month by month roll over for a month if unused.

The Plans tab of Settings → Billing lists the plans you can choose, with their prices. The public price list is on the pricing page.

Changing plan

A plan paid by card or direct debit is changed from the plan cards on the Plans tab of Settings → Billing. On Overview, Change plan opens it, or Plan details on a plan that is no longer sold:

• Upgrade to … applies at once. The difference for the rest of the period is invoiced now, and the upgrade, with the extra credits for the rest of the period, applies when that invoice is paid.
• A smaller plan (Switch to … at renewal, Change plan size at renewal) or a change of billing cycle takes effect at the end of the current period. Until then you keep your plan and its credits, and Keep my current plan cancels the booked change. A smaller plan's community and seat limits apply from the booking, though: until the change takes effect or is cancelled, creating a community, receiving one by a transfer, link or unlink, or unarchiving one is refused past its community limit, and accepting an invitation to the organization or Give seat past its seats.
• A smaller plan is refused while you own more communities than it allows, or, for an organization, while more members hold a seat than it includes. Transfer, archive or delete communities, or free seats, first.

A plan paid by invoice or under a contract is changed by JOGL: the page says so.

Invoices and receipts

Start from Settings → Billing. For an organization, choose it at the top of the page first; only its owners and admins see its billing. Where your invoices are depends on how the plan is paid:

• By card or SEPA Direct Debit — Manage plan, at the top of the page, opens the Stripe Customer Portal, where you view and download your invoices and receipts. On a plan that is no longer sold, the button is Manage subscription, on the Plans tab.
• By invoice (the Plans tab shows Invoice (bank transfer) under Billing) — Stripe emails each invoice to your billing email address, and Billing history opens the same portal.
• Under a contract (the Plans tab shows Contract) — JOGL invoices you directly under your contract, outside the app, and the page says the plan is Managed by your account team. A Billing history button appears if the account has also used Stripe (a free trial, a top-up or an earlier plan paid by card or direct debit), and lists any receipts from it.

After a plan paid by card or direct debit has ended, Manage billing, on the Plans tab, still opens the portal for your past invoices.

What needs a trial or plan

• Creating a community requires a live free trial, plan, or contract — app administrators excepted, who are exempt from this and from the plan's community limit (see Create & configure). The plan also caps how many communities you can own (one on the free trial, none on Free and Plus, and the Pro limits above), and the free trial caps each community at 200 profiles. Pro and Organization plans set no profile limit. Archived communities do not count.
• Importing members from the admin console (CSV, LinkedIn and CRM imports) and Smart Enrich stop once a community's plan has lapsed (see When a plan or trial ends).

When a plan or trial ends

When your plan or free trial ends and you take no new one, each community you pay for becomes read-only for a year:

• Whoever pays for it sees Plan lapsed: this community is read-only on the community, with the date it will be archived. Members can still browse and search it, but imports from the admin console (CSV, LinkedIn and CRM) and Smart Enrich are refused. So are guests from a connected event platform: the first import of an event is refused, and a re-sync or auto-sync imports nobody until the community is back, when the next re-sync imports the guests it skipped (see Events).
• The delegation rules you fund cover no one until you take a plan again.
• If you still have no plan on that date, the community is archived, with a banner saying it was archived because its plan lapsed. You cannot unarchive it yourself: taking a plan brings it back, while the plan has room, the most recently archived first. Read-only communities come back as soon as you take a plan, within its community limit (see the next point).
• If the plan you come back on allows fewer communities than you own, the most recently created ones beyond its limit stay read-only (Over the plan's community limit). Unless you upgrade, or archive, transfer or delete a community, before the date shown, they are archived, the most recently created first. Those that fit within the limit once you upgrade, or archive, transfer or delete a community, stop being read-only the night after, not at once.

If you never started your free trial, for example because you bought a plan straight away, starting it after the plan ends (Start free trial on the Plans tab of Settings → Billing) works like taking a plan for everything above, with the trial's limit of one community.

After an organization's plan or trial ends, its members can still spend its unexpired top-ups and its last rollover of plan credits, and nothing else of its balance.

What uses credits

AI-heavy operations consume credits — most notably search (in the app, from the chat bots, and through the API) and enrichment. Enrichment shows a credit estimate and an over-budget warning before you launch a run (see Enrichment). Who pays for a search is decided per search: by default you pay from your own balance. An organization that owns the community can cover your searches there in two ways:

• Standing funding — for any member of the owning organization who holds a seat, while the organization has a plan or a free trial or, after it ends, while its unexpired top-ups or its last rollover cover the search, within its per-member cap if its admins set one (see Spending caps and seats). The community's owner and admins are covered the same way for their searches in that community, without a seat, unless one of the organization's delegation rules applies to the search: the rule then decides, with its caps, as it does for a member. This takes none of the organization's seats, and it covers neither their other actions there, nor their searches across all their communities or in other communities, which still need a seat.
• A delegation rule — a budget the organization sets organization-wide, for a single community, or for a single event, optionally capped per member each billing month and in total. It covers the community's members whether or not they hold a seat.

A community billed to its owner's own credits covers your searches only through a delegation rule its owner funds. Such a rule covers that one community, and the owner's own actions are always billed to them without using it. A private community created on its creator's own credits gets one automatically: its members' searches and other member-paid actions there are paid from the owner's credits, up to 20 credits per member each billing month. Making the community public pauses the owner's rules on it; the owner can resume one on purpose. Any change of who pays for the community, such as a transfer of ownership or a link to an organization, pauses them too, and a rule covers members only while the person who funds it pays for the community: after a transfer, the new owner adds a rule of their own. A community's rules are listed under Delegation rules in its General section (see Create & configure), where the owner who pays for it personally, or the admins of the organization that pays for it, add and change them; an organization also manages its rules under Credit delegation rules, on the Team tab of its billing.

Whoever funds it, a delegation rule covers you only while it has room and its funder has credits:

• The composer badge shows the credits remaining in the budget. Read it as a ceiling, not a per-search guarantee: a charge is all-or-nothing against the budget, so the first search that would cost more than the remainder is billed to your own balance instead — which can happen while the badge still shows credits left. Once the remainder is below the price of one search, the badge reads Not covered · … has N credits left.
• A rule whose funder has no credits left covers no one: you pay from your own balance until the funder has credits again, as when the budget is used up. Nor does a rule whose funder no longer has a plan or a free trial.

The Overview tab of Settings → Billing lists what covers you under Covered by organizations and communities.

A search across all your communities is not covered by any community — but it is not automatically personal: it resolves against a global search wallet, which is your saved preference if you set one, else the earliest organization you joined, where you hold a seat, whose credits cover it, else your own balance. A saved preference is kept even when it has no credits left, so the search is refused rather than paid by another wallet. The exception is an organization you chose: it stops counting as your preference once you leave it or lose your seat, and, after its plan or trial ends, whenever its unexpired top-ups and last rollover no longer cover the search; the search then falls back to your organizations and your own balance as above. So an organization can end up paying for it without any community being involved. Enrichment is the other way round — a community enrichment run is always charged to that community's billing owner.

Spending caps and seats

An organization's owners and admins who hold a seat set these on the Spending caps and seats card, on the Team tab of the organization's billing:

• Per-member cap — the most one member may spend from the organization's credits in a billing month, enrichment runs billed to the organization excepted. A member past it pays from their own balance until the next billing month. The cap applies only while the organization has a paid plan, so during a free trial members have no cap.
• Seats — an Organization plan includes from 5 seats (Org 200) to 1,000 (Org 50K). A member who holds a seat can spend the organization's credits, and an owner or admin who holds one gets the shared admin rights described on Organizations. A member shown with No seat keeps the membership, and the cover of any delegation rule that reaches them, and nothing else. Admins hand seats out with Give seat and Remove seat, or move one from another member. When the plan includes fewer seats than are in use, the members who joined most recently lose theirs first; the owner never does. An invitation can be accepted only while a seat is free. During a free trial, or without a plan that counts seats, nobody can be unseated and an invitation needs no free seat, but a member who lost their seat under an earlier plan stays at No seat until an admin uses Give seat.

Every change is recorded with who made it.

Launch offer

While a community is getting started, whoever pays for it can buy launch packs of 100, 500, 2,000 or 10,000 credits at a launch discount. The window opens with the community's first member import and stays open for 30 days. Launch credits pay only for enriching that community and expire 90 days after purchase, and a community can buy up to 10,000 of them. The packs need a live paid plan: a free trial does not count. When the community's payer changes from one person to another, or from one organization to another, its launch credits move with it; between a person and an organization they stay with the former payer and pay for nothing unless the community comes back to that payer before they expire.

The offer appears on the creation wizard's Source step and on the Smart Enrich form when a run costs more than the balance. Launch credits, on the Overview tab of Settings → Billing, lists what is left.