Pay for what flows.
Metered units × your rate card, one monthly invoice, ACH-preferred. The rate card is set in conversation and fixed at onboarding; everything it multiplies is measured, shown and auditable in your portal.
Flow meter — estimate the quantities your stack produces
10k ————— 5M
Drag anything. The fabric responds in the same frame — and no dollar figure ever appears, because that part is a conversation.
Your rate card is set at onboarding. Invoices are monthly, ACH-preferred. Nothing to upgrade to.
Your configuration lives in this page's URL — copy the address bar to share it with whoever signs things.
Four unit families. That is the whole meter.
Everything on your invoice is one of these four quantities multiplied by your rate. There is no fifth line, no setup amortization hiding in a footnote, and no minimum that quietly becomes the bill.
Connector-syncs
One completed sync run of one connector. A connector on a 15-minute cadence produces 96 a day; an hourly one produces 24. This is the primary unit because it is the thing we actually operate.
Normalized records
Canonical records written to the hub — created or merged. A sync that finds nothing new writes nothing and costs nothing in this family. Merges count once, not once per upstream.
Active connectors
Distinct operated connectors that ran at least one sync in the period. Pause a connector and it stops counting in the next period — no notice, no negotiation, no partial-month arithmetic.
Unified API calls
Reads against the hub API — your dashboards, your warehouse loader, your internal tools. Webhook deliveries we push to you are not metered; we chose to send those.
Anatomy of an invoice.
This is the literal document our clients receive, with rates redacted. Pricing anxiety is mostly document anxiety — so here is the document.
Invoice APF-2026-0142
Billed to: Client hub · hub_9f21c4
| Unit family | Metered quantity | Rate | Line total |
|---|---|---|---|
| Connector-syncs | 1,236,480 | — per your rate card | — |
| Normalized records | 2,411,905 | — per your rate card | — |
| Active connectors | 9 | — per your rate card | — |
| Unified API calls | 918,244 | — per your rate card | — |
| Subtotal | — | ||
| Service credit · incident INC-2026-0731 | − credit applied | ||
| Total due | — per your rate card |
Beneficiary APIfl0w Inc.
Method ACH (preferred) · card on file accepted
Reference APF-2026-0142
Questions billing@apifl0w.com
Principles
- No seat pricing. Add every colleague you like; a dashboard viewer is not a unit.
- No platform fee surprises. There is no monthly minimum wearing a different name.
- Rate card fixed at onboarding, reviewed annually, in writing, with notice.
- Every unit auditable in your portal, down to the individual sync run.
- Nothing to upgrade to. There is one product and one rate card; growth changes the quantities, not the tier.
The six things everyone asks.
01What happens if we blow past our expected volume?
Nothing happens. There is no overage penalty because there is no allowance to exceed — quantities are simply higher and the invoice is correspondingly higher at the same rate. If a month is dramatically out of line with the prior three, we open a conversation before the invoice, not after it, because a 4× jump is usually a broken upstream sending duplicates rather than a good week.
02Can we change sync cadence mid-month?
Yes, on request or self-serve for connectors where the upstream allows it. Cadence changes take effect at the next window and are metered from that moment — connector-syncs are counted as they happen, so a mid-month move from hourly to 15-minute produces a blended count for that period with the change point visible in your usage view.
03What happens when we retire a connector?
We pause it rather than delete it. It stops producing syncs immediately and stops counting as an active connector from the next billing period. Its historical records, lineage and raw payload archives remain queryable for as long as you are a client, and are included in your export if you leave. Reactivating a paused connector takes minutes, not a rebuild.
04Is there a charge for getting our data out?
No. Full canonical export in JSONL with lineage, on request or at termination, at no cost — a position we are happy to put in the contract because retention-by-friction is a bad business to be in. Raw upstream payload archives are included wherever the upstream's licence permits us to redistribute them to you; where it does not, we say which system and why.
05What do the contract terms look like?
Twelve months initial, then month to month with 30 days' notice. The rate card is fixed for the initial term and reviewed annually with 60 days' written notice of any change. There is no auto-escalator, no minimum commitment, and no clause that makes leaving expensive. Operations commitments — acknowledgement times, notification windows, credit schedule — are in the agreement, not on a marketing page.
06Why do you prefer ACH over card?
Because card processing costs two to three percent of every invoice, and on a metered service that is a real number which ends up in someone's rate. We accept cards for teams whose procurement runs that way, and we keep a card on file as a fallback for ACH returns. ACH remittance details are on every invoice in a copyable block.
Request your rate card.
Tell us the systems, the cadence you need and the volume you expect. We will come back with a rate card and the quantities we think it will multiply.