Plans and billing

Billing is per organization — everything billable (domains, redirects, subscription) belongs to the organization, not to an individual user. If you belong to several organizations, each has its own plan and limits. See organizations for the model.

Plans

	Free	Starter	Pro	Business
Price	$0	$9/month	$29/month	$99/month
Domains	3	20	100	500
Redirects per month	10,000	500K	5M	25M
Analytics	7-day	30-day	Advanced	Longer retention
API access	—	Yes	Yes	Yes
Other	Basic SSL		Bulk operations, teams	Priority support, advanced rules

Note

These are RouteSeam’s launch prices and limits. They may be adjusted as pricing is validated; the Settings → Billing page always shows your organization’s current plan and its actual limits.

Managing billing with Stripe

RouteSeam bills through Stripe. From Settings → Billing you can:

• See your current plan and usage against limits — domains and monthly redirects, shown as progress bars.
• Upgrade — a Stripe Checkout session opens; the new limits apply when checkout completes.
• Manage payment details, invoices, or cancel — the “manage” action opens the Stripe customer portal, where you handle anything card- or invoice-related directly with Stripe.

RouteSeam never stores your card number; Stripe holds payment details.

Usage limits and overages

RouteSeam’s rule for infrastructure software: your redirects never silently break because you hit a quota. Instead, limits escalate gently:

• 80% of quota — a warning banner appears in the dashboard (and on Settings → Billing) so you have time to upgrade.
• 100% of quota — a second warning plus overage handling. Paid plans support overages rather than hard cutoffs.
• Significant abuse — only sustained, extreme overuse leads to throttling or suspension, and that is an abuse response, not a billing mechanism.

The warnings are deliberately not punitive: a redirect that has worked for months keeps working while you decide what to do.

API access

The RouteSeam API requires a paid plan (Starter or above). Generate keys under Settings → API keys; keys are shown in full once at creation and stored only as hashes.

Downgrades and missed payments

Downgrading moves your organization to the lower plan’s limits. If you currently exceed the new plan’s limits — for example 30 active domains when dropping to Starter’s 20 — your existing redirects keep working, but you cannot add new domains until you are back under the limit. Reduce the domain count first, then downgrade, to keep management straightforward.

Past due. A failed payment puts the subscription into a past-due state while Stripe retries the card according to its dunning schedule. During this period existing redirects continue to serve — a billing problem in the control plane never takes the edge down. Update the payment method through the Stripe customer portal from Settings → Billing to clear the state. Accounts that stay unpaid eventually lose paid-plan capabilities, but suspension for non-payment is a last resort, not an automatic consequence of one failed charge.

Tip

Because redirects run at the edge independently of the control plane, even a full outage of billing systems does not affect live traffic. Your migration does not depend on an invoice being current.

Related pages

• Analytics — what each plan’s retention window gets you.
• Abuse and safety — the separate, stricter policies for abusive redirects.