Billing

Introduction

swarmvia bills each organization for a licensed plan and monthly request usage. Licensed plans are billed monthly. The request allowance and metered overage reset on your monthly usage period.

Manage plan, usage, spend limits, payment method, and cancellation under Billing in the dashboard.

Every organization starts on the Free plan: 25,000 requests to start, no card. When they are used up, sources pause until you add a payment method or choose a plan. Upgrade when you need more sources or requests.

Plans

Prices are in USD, per organization per month. Every plan includes unlimited members.

Plan	Monthly	Included requests / org / mo	Overage (per 100k)	Sources	Work projects	Log retention
Free	$0	25k one-time (25k / mo with a card)	$10.00 with a card on file	2	1	1 day
Starter	$49	500k	$6.00	6	5	30 days
Team	$99	1M	$6.00	20	25	90 days
Business	$199	5M	$5.00	50	Unlimited	1 year

Free's 25k requests are a one-time allowance — no card, no clock, no monthly reset. Sources pause once it is used. Add a payment method on the billing page to pay as you go instead: 25k requests are free every month, and requests past that bill at $10.00 per 100k ($0.10 per 1,000). Your monthly spending limit (every organization starts with one) caps what a month can cost — raise, lower, or clear it any time. Everything else about the Free plan is unchanged.

Every plan includes a *.swarmvia.cloud endpoint for each source.

Need more than Business? Contact [email protected].

Plans scale on sources, requests and Work projects (Free: 1, Starter: 5, Team: 25, Business: unlimited). Every paid plan allows up to 50 concurrent requests per source (Free: 10). Every plan can front an MCP server, an HTTP origin, or a PostgreSQL or MySQL database, and every plan includes IP policies and caller JWT or Cloudflare Access. JDBC sources, which run a driver you supply, use a source each and are also capped on their own, because each keeps a runtime of its own warm while it is in use: Starter allows 1, Team 3, Business 10 (Free: none). Every paid plan includes shared origin Capacity budgets with Fixed or Auto balancing. Team and Business add async admission. Origins per source are plan-capped (Free and Starter: 1, Team: 5, Business: 8). Access log retention scales by plan (Free: 1 day, Starter: 30 days, Team: 90 days, Business: 1 year). See the pricing page for the full comparison.

Exact feature gates are shown on the pricing page and in-product when a control is plan-locked.

Free plan

The Free plan has no clock and needs no card. Its request allowance is one-time: when the organization has used it, sources pause and refuse traffic until you add a payment method or subscribe. Paused sources keep their configuration and credentials.

To keep sources running without changing plans, add a payment method on Billing ("pay as you go"). With a card on file the same allowance is free every month, and requests past it bill at the Free overage rate above, bounded by your spending limit. Limits, sources, and features stay exactly the Free plan's. Removing the card later returns the organization to whatever remains of the one-time allowance.

Once an organization has paid subscription history, the Free plan no longer applies: after a cancellation or payment failure, sources stay offline until you subscribe again. Pay as you go is not a paid tier for this rule — cancelling it simply returns the organization to the regular Free plan.

On Billing, choose Starter, Team, or Business. New subscriptions open Stripe Checkout for the licensed plan. Monthly usage billing is attached after the subscription starts.

You can set a spend limit before you subscribe so it is ready when overage starts.

Changing plans

Plan changes live under Billing → Change plan. Payment method and invoice history use Manage payment in the Stripe Customer Portal. Plan changes stay in the app so limits and proration stay consistent.

Metered usage does not reset when you change plans. The previous plan's included request volume and overage rate continue through the current usage period. Stripe applies the new plan's metered price after the next usage invoice. Plan limits and licensed pricing change immediately.

Upgrades

Upgrades take effect immediately. Higher source, concurrency, and feature limits apply right away. Stripe charges a prorated difference for the rest of the billing period on an invoice now.

Access log retention also rises with the plan within a few seconds. Logs you already have stay searchable and are now kept for the longer period.

Downgrades

Downgrades also take effect immediately once they are allowed. Stripe credits unused time from the higher plan and invoices the adjustment now.

You cannot downgrade until your organization fits the lower plan. If anything is over the target limits, Billing shows the blockers and the switch stays disabled. Typical blockers:

More live or archived sources than the target plan allows
Source concurrency, queue depth, or origin count above the target caps
Async admission still configured on sources when the target plan does not include it
More Work projects than the target plan allows
Too many async webhooks for the target plan
Origin capacity budgets (or auto-balancing) still present when the target plan does not include them

Reduce or remove those resources under Sources, Capacity, IP Policies, or Webhooks, then try again.

Log retention drops with the plan immediately after a successful downgrade. The Logs tab shows only the new retention period, and older access logs are deleted.

Note. Soft “grandfathering” only applies when you stay on your plan and edit sources. Existing settings can keep values you already set. You still cannot increase past the current plan. Choosing a lower plan is different: you must fit that plan first so lower tiers do not keep higher-tier capacity or gated features.

First paid plan from Free

Every paid plan includes everything Free does, so upgrading from Free always fits.

What counts as a request

Each admitted proxied request counts, including response cache hits (a hit still writes an access-log entry and meters as one request). Rejected or failed admissions that still hit your source also count.

Overage bills on your billing period. The Billing page usage charts and spend limits use the same usage period while subscribed. Free organizations use calendar-month buckets.

Metrics vs Billing

Metrics answers whether the concurrency limit did work (admit, queue, reject, top keys). Billing answers how much request allowance you used. They look at the same traffic for different questions.

Spend caps

Set a monthly overage spend limit under Billing. Choose notify only, or pause every source when estimated overage reaches the limit. Defaults can ship on new organizations so surprise bills are less likely; raise, switch to notify-only, or clear the limit on the same page.

Paused sources refuse traffic until you change the limit or the usage period resets. Spend pauses are separate from payment-failure suspension.

Stripe Tax

Automatic Stripe Tax is off by default. Enable it in your Stripe Dashboard only after Stripe Tax registrations are active. Consult a tax advisor before enabling it.

Payment, cancellation, and recovery

Manage payment opens the Stripe portal for card updates and invoices. Use Cancel subscription on the Billing page to cancel. Your plan stays active through the end of the licensed billing period. Billing shows the plan as cancelling until that date.

If an invoice fails, sources suspend so traffic stops and metering stops. Update the payment method and pay the open invoice to recover. After a long grace period, suspended sources can be purged. Opening Billing also re-syncs with Stripe and brings eligible sources online if a recovery webhook was missed.

Strong Customer Authentication (3-D Secure) may open a confirmation step during an upgrade charge. Complete it to finish the plan change.