How billing works
The one subscription behind your account, and the usage lines that ride on it.
Everything your account pays for lands in one place: a single consolidated Stripe subscription for the things you subscribe to, plus a stream of metered usage lines for the things you consume by the hour. This page is the map of how those two halves fit together.
The consolidated subscription
One Stripe subscription per account carries every plan you are on as its own line item, or item, on that subscription: your membership plan, your support plan, your AI Workspace plan, and the plan of every module you have switched on (Commerce, Shipping, Drive, Email, Trust Center, and the rest). Changing one plan reprices that one item; it never touches the others, and it never creates a second subscription.
An account bills in exactly one currency (USD, EUR or ILS), chosen at signup from the country you gave or Cloudflare's own read of where the request came from, and every item on the consolidated subscription is in that currency. Stripe refuses to mix currencies on one customer, which is also why a domain, a phone number or a mailbox, each its own small subscription, has to be created in that same currency rather than in whichever one a price happened to be typed in.
What rides on the consolidated subscription
Every module plan is switched independently. Upgrading Commerce from Starter to Growth does not touch your Shipping plan, your membership, or anything else riding the same subscription; each is its own subscription item with its own price.
What is metered instead of subscribed
Deployments (VPS, app servers, datacenters, load balancers) do not carry a flat plan of their own. Each one is priced from the moment it is created: a server size (covering vCPU, RAM and disk), plus whichever add-ons are switched on for it, plus, for a native app build, the deployment-type fee that build carries (a PWA, an Android build, a desktop build and so on each cost a different flat amount). See Usage-based pricing for every figure.
The spec is priced when the deployment is created
Server size, add-ons and deploy-type fee are added up into a monthly total and an hourly rate the moment you deploy, the same math the deploy wizard showed you before you confirmed.
Cost accrues by the hour
The hourly rate accrues continuously while the deployment exists. A one-hour minimum applies to every billing segment, so resizing down again minutes after a burst does not let the hour be billed as a fraction.
A resize opens a new segment
Changing the server size or flipping an add-on closes the current segment and opens a new one at the new rate. Nothing is lost: the ledger keeps every segment, so the invoice line for the period reflects exactly what ran and for how long.
The accrued total is flushed onto the invoice
The metered total is added to the consolidated subscription's invoice as its own line items, alongside the flat subscription lines for membership, support and every module plan.
Deployments, VPS and add-ons
A VPS (a standalone virtual server, not tied to an app deployment) and an app-server
deployment both draw their size from the same server_slugs catalog, grouped into four server
types (shared, optimized, performance, and a large tier for the biggest sizes) across three modes:
hosting a deployment yourself, a Xuda-managed deployment, and a standalone VPS. Each
mode, size and type combination has its own catalog price; see
Usage-based pricing for the full table.
Add-ons that ride on top of a deployment, each its own monthly figure, converted to the hourly rate the same way: branding removal, a utility screen, user assist, a custom domain, a Xuda subdomain, taking a deployment offline on a schedule, automatic backups, and OCR on Drive uploads. A dedicated public IPv4 address is its own add-on, billed whenever a deployment or VPS opts into one, with a separate one-time setup fee the first time. Backup storage itself (the size of what has actually been backed up, not the backup feature switch) is metered separately, per GB per month.
Domains
A domain is not a catalog price: domain_search and domain_quote price each name live from the
registrar (wholesale plus Xuda's markup) and lock that quote for the purchase, because TLD pricing
changes registrar-side far more often than a static list could track. Once bought, a domain is its
own small Stripe subscription in your billing currency, separate from the consolidated one, so it
can be transferred to another Xuda account without touching anything else you pay for. A domain
attached to a Static Website you did not buy through Xuda is billed differently: a flat monthly
custom-domain fee on that website's own plan instead of a registration subscription.
Team seats and sponsored access
Every plan includes a number of team members for free (the team_members figure on your membership
tier). Members beyond that number accrue hourly at a flat per-member monthly rate, the same
hour-metered way a deployment does. A sponsored guest, someone given access without a seat of their
own, accrues by the hour they are actually active rather than by the month.
Why a plan change never surprises you
Because each plan category is its own subscription item, changing one plan only ever reprices that one item. An upgrade is prorated and charged the moment you confirm it; a downgrade is scheduled for the end of your current billing period so you keep what you are paying for until it renews. See that page for the full mechanics, and Cancellation for switching a plan back to its free tier.
Settings → Billing is the one place every one of these lines is shown together: the current cycle's running total, a breakdown by source, every plan you are on, your saved cards, and your invoice history.