Billing & Payouts
Your NodeRings platform subscription, marketplace commission, and how customer revenue reaches you
There are two money flows as a provider, and they are kept separate:
Your platform subscription
What you pay NodeRings for the provider platform. Billed to your payment method.
Your marketplace revenue
What customers pay you for VMs. Paid out to your account, minus a commission.
Prices and commission rates below reflect current defaults. Always confirm live numbers on /billing/subscription before you plan around them.
Platform subscription
When you create a provider organization, a Community subscription is attached automatically. Paid tiers unlock higher infrastructure limits and a lower marketplace commission.
| Tier | Monthly | Yearly | Payouts | Marketplace commission |
|---|---|---|---|---|
| Community | $0 | $0 | Enabled | 15% |
| Starter | $90 | $900 | Enabled | 10% |
| Premium | $120 | $1,200 | Enabled | 6% |
| Enterprise | Custom | Custom | Enabled | Negotiable |
Community is free forever (not a time-limited trial). You can sell on the marketplace and receive payouts on every tier, including Community. Upgrade to Starter or above when you need higher infrastructure limits or a lower take rate.
Manage your plan, invoices, payments, and payment methods at /billing/subscription.
Marketplace commission
NodeRings takes a percentage of your marketplace revenue as a platform fee: 15% on Community, 10% on Starter, 6% on Premium.
The commission is deducted from your revenue, not added to the customer's price. Customers pay the listed plan price plus tax; your payout is the plan price minus the commission.
For a $100 plan sale on Premium (6%):
| Line | Amount |
|---|---|
| Customer pays | $100 (+ tax) |
| NodeRings commission | $6 |
| Your payout | $94 |
Getting paid: choose a payout method
Set up payouts at /billing/payout. There are two options.
Recommended. Customer payments are split at charge time and transferred directly to your own Stripe account: NodeRings never settles the funds on your behalf.
Start onboarding
On /billing/payout → Payout Methods, choose Stripe Connect. NodeRings creates a Stripe Connect account and sends you to Stripe's hosted onboarding.
Complete Stripe's form
Provide your business and bank details to Stripe. When finished, Stripe returns you to the dashboard. Onboarding is complete once Stripe reports charges and payouts enabled.
Pick a payout schedule
Under Payout Schedule, choose how often transfers run:
| Schedule | When |
|---|---|
| Immediate | As soon as a customer payment settles |
| Daily | Once a day (09:00 UTC) |
| Weekly | Mondays |
| Monthly | 1st of the month |
With Stripe Connect, the commission is applied as a Stripe application fee on each charge, and the remainder is transferred to you on your schedule. Track transfers under Revenue Dashboard and Transfer History.
For regions where Stripe Connect isn't available, register bank account details for manual transfers instead.
Add your bank account
On /billing/payout → Payout Methods, choose Manual payout and enter your account details (IBAN/BIC, or account + routing number) and country.
Verification
NodeRings verifies the account before releasing funds. Manual payouts are held until the chargeback window has largely passed (typically 60–120 days), then released to you.
Manual payout and Stripe Connect are mutually exclusive. If you have only manual payout configured, the automated payout schedule does not apply, funds are released manually after verification.
How a customer payment reaches you
Customer buys a plan
A purchase creates a subscription tied to your plan and the customer's VM.
NodeRings generates an invoice
A daily job issues invoices. Fixed (subscription) plans are billed at the start of each period; usage-based plans are billed at the end, from metered usage records (for example bandwidth).
Payment is charged and split
The customer is charged via Stripe. For marketplace sales, the charge is split: your commission goes to NodeRings, and your share is earmarked for transfer to your Connect account.
Funds are paid out
On your payout schedule, NodeRings transfers your revenue and records a payout invoice you can review under Transfer History.
Fixed addon proration (mid-period purchases)
Fixed-price addons (for example Additional IP on a subscription plan, or Daily / Weekly Backup billed as a percentage of plan price) are in-advance charges that align with the VM subscription billing period, not the calendar month.
When a customer enables a fixed addon partway through an active VM period, they are charged immediately for the remaining portion of that period. They are not billed the full monthly amount on day one unless they add the addon at the start of the period.
How the billing period works
VM subscriptions use an hour-based monthly cycle:
| Concept | Value |
|---|---|
| Standard month length | 730 hours (~30.42 days) |
| Period boundaries | Set per subscription (current_period_start → current_period_end) |
| Proration basis | Seconds remaining in the current period ÷ total seconds in the period |
The platform does not prorate by calendar days in a 30/31-day month. It uses the subscription’s actual period length, which for monthly plans is anchored to 730 hours from period start.
Proration formula
When a fixed addon is added at time T during the current VM period:
prorated charge = full period addon price × (remaining period time ÷ total period time)- Full period addon price: flat monthly fee (for example $2/month per additional IP), or for backup addons on fixed plans, the configured percentage of the plan base price for one billing period.
- Remaining period time: from T until
current_period_end. - Total period time: from
current_period_startuntilcurrent_period_end.
Fractions are computed with second precision, so partial hours at the end of the period are included fairly.
Examples
Additional IP ($2.00 / month) on a VM whose period is half over:
| Line | Value |
|---|---|
| Full period price | $2.00 |
| Remaining fraction | ~50% of period |
| Immediate charge | ~$1.00 |
Daily Backup (30% of a $5.00 / month plan) added with ~25% of the period remaining:
| Line | Value |
|---|---|
| Full period backup price | 30% × $5.00 = $1.50 |
| Remaining fraction | ~25% |
| Immediate charge | ~$0.38 |
At the next VM renewal, the addon is included on the regular invoice for the full upcoming period (subject to the same subscription and addon pricing rules).
What customers see
- Mid-period enable: a one-time prorated charge to the payment method on file (shown on the client billing dashboard under add-ons).
- Renewal: the full-period addon amount on the VM invoice for the new period.
- Usage-based addons (for example backup storage on usage plans, additional IP on usage plans) are not prorated this way; they accrue from metered usage and are billed in arrears.
All fixed addon templates are configured to prorate to the VM billing period. Usage-based addons bill from meters (hours, GB-hours, and so on) instead. See Plans & Addons for which addon types support each billing model.
FAQ
Next
Revenue depends on plans passing validation first. Continue with Preflight Check, or review the platform overview in How it works → Billing and payouts.