Billing Integrations
If you already meter usage in a billing platform, Suger can forward it to every connected cloud marketplace instead of you reporting it a second time through the Metering API. Each connection is no-code, and none of them require migrating off the platform you use today.
Platforms Suger meters from
| Platform | What Suger forwards | How often | Setup guide |
|---|---|---|---|
| Metronome | Usage | Hourly or daily, whichever you choose | Metronome |
| Orb | Usage, costs, or invoice totals | Hourly | Orb |
| Lago | Subscription usage or costs | Daily | Lago |
Metronome forwards usage metered in your existing Metronome instance. Its guide covers org-level and user-level connections, how the sync works, what happens when a sync fails, and the billing modes available.
Orb forwards usage, costs, or invoice totals. Its guide covers the billing modes, invoice mode, and how to connect an Orb customer to a Suger buyer.
Lago forwards subscription usage or costs. Its guide covers the billing modes and how to connect a Lago customer to a Suger buyer.
Setting one up
Connect a platform from Settings > Integrations in the Suger console. You provide the platform’s API credentials, then map your internal billing dimensions to your marketplace dimension keys. Once the connection is active, the platform routes usage to Suger, which verifies it and reports it to the marketplaces.
You can run a native integration and the Metering API side by side. See Automate usage with billing integrations on the Metering page for how the two combine, and what happens if your billing platform has an outage.
Other billing and finance connections
Stripe, Chargebee, Zuora, QuickBooks, NetSuite, Avalara, and AWS Billing connect to Suger as well, but they handle payments, subscriptions, accounting, and tax rather than feeding metered usage. They are listed under Bill, meter, and close the books in the integrations catalog.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.