Get started

Plans and billing

What your plan decides, how to change it, how each plan is paid, where invoices are, and how the data processing agreement is recorded.

Costfluent has four plans: Free, Pro, Business and Custom. Each plan includes everything the plan below it does. Pro and Business are bought in the product; Custom is set up with Costfluent. The pricing page lists prices and limits; these pages do not repeat them.

Before you start

Open Settings, then Billing & plans. Every member of the organization can see the plan, its limits and what has been used against them. Tracked spend, its three-month average and the band alert show only to the organization's Owners and, in an organization a partner manages, to the partner's managers. Changing the plan or the payment method, and the Billing email and Invoices cards, need an organization Owner; anyone else reads "Changing the plan or the payment method needs an organization owner."

Each organization has its own plan. If you own several, each one is billed on its own; see How Costfluent works.

What a plan decides

The Billing & plans page with the Your plan, Payment and Invoices cards

Billing & plans for an organization on Custom, with the Plans and This month cards left out; the pricing page lists what each plan covers.
  • Limits. The This month card shows each limit beside what you have used: Tracked spend, Provider connections and Cost history, and it counts Cost rows this month and Stored provider data this month as well. No plan limits provider connections, cost rows or stored provider data, so those read "Unlimited" unless a limit is set for your organization. A limit set for your organization is marked "Set for your account". When a provider corrects a month Costfluent has already collected in full, Costfluent reads that month again, and that read adds to Stored provider data this month but not to Cost rows this month.
  • Features. A few features start at a given plan; their pages say which, for example curated findings on Business or an exchange rate policy only on Custom. A feature already set up keeps working after a move to a lower plan where its page says so.
  • Cost history. How far back reports reach. A range that starts earlier is cut back, never filled with zero, and a comparison whose days start earlier, as the same period last year can, is left out rather than counted as zero.

Three-month average tracked spend under Your plan is the measure a plan's spend ceiling is compared with. When three months of tracked spend put the account above what the current plan covers, the page names that plan, for example "Your usage is in the Business band", and offers to move to it. The plan moves on its own by a different count, single months rather than the average: after two completed months in a row above what the plan covers, a paid plan moves up to the plan that covers the second month's spend, at a renewal at least 14 days after the owners are told, so it can move to a plan other than the one the page names. Cost in a custom provider counts toward this too, and a move up can rest on it: on the day the move takes effect, each of the two months is measured again with the cost its custom providers hold then, and when either is no longer above what the plan covers, the move is withdrawn, nothing is charged, the count of months starts again, and the owners are told in the console. Removing that cost before the date, by deleting the upload or the custom provider or by replacing the lines sent through the Public API, withdraws the move, provided the removal has finished by then. Cost Costfluent collects through any other connection is not measured again, so deleting such a connection withdraws no move. A move resting on a month measured before Costfluent measured custom provider cost on its own is charged as before. A Free organization stays on Free: its owners are told after the first such month, and after the second its collection pauses until it moves to a paid plan. Cost that arrives after its month was counted, such as a disabled connection catching up, still counts, so a later count can pause collection or move the plan without an earlier notice for that month. When that month's spend is above what Business covers, Costfluent gets in touch instead of moving the plan, and a Free organization's collection pauses all the same. Whenever collection is paused, the page says "Cost ingestion is paused" with the reason; existing data and reports are unaffected. On Free it adds "Moving to a paid plan resumes collection." When Costfluent paused collection itself, the page says "Contact us to resume collection." instead, on Free too, and offers no plan: ask through the contact form. The pause follows the cloud account: for up to a year, while it lasts or after a Free organization whose spend is above the band is deleted, the same account cannot be connected to another organization on Free, and a connection to it made there earlier collects nothing; on a paid plan it can. Another organization's pause holds only what that organization collected, so your connection keeps collecting when an account it covers was paused elsewhere: an AWS management account whose member account another organization collected, or an Azure connection that also reaches a subscription the paused organization did not. For Google Cloud, the same account means the same billing export: the same billing account's export in the same project and dataset.

Tracked spend is a month's cost counted with the product's own defaults: amortized, with credits, refunds and corrections left out and tax included (see Cost amounts); Kubernetes cost never counts toward it. The Your plan card says the same under the average, with a link back here. When part of a month's cost is in a currency without an exchange rate, the month counts toward the band on the rest of its cost once that alone is above the ceiling. Each connection's costs count from zero in each currency: its negative amounts net its own charges but never lower what other connections track.

Set the billing email

The checkout receipt and every invoice go to the organization's billing email, and a checkout cannot start without one. In the Billing email card, below Payment, enter the address and select Save billing email; "Billing email saved" confirms it. Only an organization Owner sees the card, and only an Owner can change the address.

Change your plan

  1. In the Payment card, select Change plan, or select Choose beside a plan in the Plans card.
  2. Pick the plan under Move to and confirm with Change plan. A move to a lower plan confirms instead with the button that names it, such as "Move down to Free".
  3. Without a payment method on file, a paid plan confirms with Continue to checkout instead, which opens the payment processor once the billing email is set. This includes the plan you are on when Costfluent set it for you and nothing bills it yet. Pro is paid by card there, and Business by card or SEPA Direct Debit. Your payment details, billing address, VAT ID and a promotion code, if you have one, are entered there; Costfluent never sees the payment details. Where paid plans cannot be bought yet, the dialog says "Paid plans are not open yet" instead, and the confirm button stays disabled.

An upgrade charges the prorated amount for the rest of the period at once, and its limits apply as soon as that payment succeeds. When the payment cannot be collected at once, for example because the card needs confirming or is declined, you stay on your current plan and the confirmation says the upgrade waits for its payment; settle it with Manage payment method in the Payment card. A downgrade takes effect at the end of the period already paid for, and the Payment card shows the move until then, for example "Moving to Pro". Pro is paid by card only, so while Business is paid by SEPA Direct Debit or bank transfer, a move to Pro is refused until a card is your payment method. If Business is paid by SEPA Direct Debit, make a card your payment method with Manage payment method in the Payment card first. If it is invoiced for bank transfer, a card added there does not change how the subscription is paid: ask through the contact form and Costfluent moves it to card payment, after which you can change the plan. Moving to Free ends the subscription at the end of the period, shown as "Subscription ending". Choosing a paid plan before then keeps the subscription instead: the end is withdrawn, and the dialog says the subscription renews on that plan before you confirm. An upgrade then applies as described above, and a downgrade at the end of the period. Collected cost is kept and shows again after an upgrade, but anomalies and measured savings older than the lower plan's cost history are deleted once it applies, and an upgrade does not bring them back.

Custom is set up with Costfluent rather than bought in the product: it has no published price, so Plans shows it as Quoted, and it is quoted for your organization, sold with an order form and a negotiated data processing agreement, and paid by bank transfer against an invoice. Choosing it shows "Custom is set up with us" and "Contact us", which opens the contact form; the confirm button stays disabled.

When a lower limit leaves too many rules or connections

A plan can limit how many allocation rules an organization has. No plan limits provider connections, so a downgrade keeps every connection collecting; only a connection limit set for your organization can pause one. When a downgrade leaves more rules than the plan allows, or a limit set for your organization leaves more rules or connections than it allows, nothing is deleted and you choose nothing:

  • Connections. The connections created first keep collecting, up to the limit set for your organization. The rest pause: they collect nothing new, and the cost they already collected stays in your reports. A paused connection is marked "Paused", and its page shows "Collection paused" and says to contact us to change the limit. A sub-account follows the connection it belongs to. A disabled connection still counts towards the limit when you add a connection, but takes no place among the ones that keep collecting, so disabling an older connection lets the next one collect. Kubernetes clusters do not count towards the limit and never pause. A paused connection's sync button is disabled, and a sync started through POST /v1/providers/{providerId}/sync in the Public API is refused with HTTP 422 and the error code limit_exceeded. See Manage connections.
  • Allocation rules. Of the rules that are switched on, the ones created first apply, up to the limit. The others stay saved and editable, but do not apply to cost reports, allocation or a rule preview until there is room again. A rule that is switched off takes no place, so switching off or deleting an older rule lets the next one apply. See Segments and allocation rules.

A higher limit resumes everything without any action: an upgrade lifts the rule limit, and a limit raised for your organization lifts either. Paused connections collect again at the next scheduled collection, and every rule applies again the next time cost is read.

How each plan is paid

PlanPayment
FreeNot billed
ProCard
BusinessCard or SEPA Direct Debit at checkout, or bank transfer against an invoice on request
CustomBank transfer against an invoice

Payment shows the Payment method and the renewal date under Renews on. Select Manage payment method to change it at the payment processor.

Invoices

Invoices lists every invoice issued to you, newest first, with its number, period, net, VAT, total and status, and a document to download. The VAT line names its treatment: "German VAT", "Reverse charge — VAT payable by the recipient", "Outside the scope of VAT", "US sales tax", or "Tax charged in another country". Only an organization Owner sees the card.

A partner manages your organization

When a partner manages your organization, the partner handles billing. Billing & plans then shows only "Billing for this organization is handled by the partner that manages it.", with no plan, usage, plans or invoices, whatever your role. Deleting the organization is refused as well: Settings, then Organization, reads "This organization is managed by a partner. Ask them to delete it."

Data processing agreement

Planned: negotiated data processing agreement

Not yet available in Costfluent.

Included in the Custom plan. Compare plans

On Custom, ask for the agreement through the contact form: it is negotiated with you from Costfluent's standard data processing agreement. The agreement is signed outside the product. On a plan sold with an agreement, Settings, then Organization, shows the Data processing agreement card as Costfluent has it on record: "In force" or "Not on record", the Document version, and who signed it, in which Role and on which date. Provider collection pauses while no agreement is in force, and the card says "Provider collection is paused". On other plans the card does not appear.