> ## Documentation Index > Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt > Use this file to discover all available pages before exploring further. # Hosting upgrades and runtime add-ons Every plan ships with hosting: deploy from Git, get a private domain and a database. When one app outgrows its included limits, move that app up a hosting size or enable a runtime add-on. Hosting upgrades and runtime add-ons are per app: the rest of your apps stay where they are, and everything lands on the organization's one invoice. ## Hosting upgrades Each app starts on the hosting its plan includes, shown as **Included with {plan}** (for example "Included with Pro"). Its limits differ by plan. See the [comparison](/subscription-2). A hosting upgrade replaces the app's hosting limits with the size below. | | Medium (\$79 / app / month) | Large (\$199 / app / month) | Custom | | :- | :- | :- | :- | | Database | 10 GB | 50 GB | Dedicated | | Bandwidth | 150 GB | 500 GB | Custom | | Instances | up to 4 | up to 8 | Custom | | CPU and memory (production) | 2 vCPU, 1 GiB | 2 vCPU, 2 GiB | Custom | | [Always-on server](/always-on-server) | - | - | Enterprise only | | Region | - | - | EU / US | | SLA | - | - | Yes | An upgrade starts once its charge is paid, usually within a minute. Until then, and for as long as a failed charge stays unpaid, the app keeps the size it had. See [Changing hosting](/billing#changing-hosting). Production runs on the upgrade's CPU and memory, and the most instances it allows, as soon as the upgrade starts. Nothing needs redeploying. Staging and development run on one instance, at 1 vCPU and 512 MiB unless you give them more CPU and memory yourself. When an upgrade ends, the app goes back to the hosting its plan includes. For Custom, contact the Meridian team. ### Changing an app's hosting Every hosting change happens on the app's **Change hosting** page: pick a tier, check what it changes and what is charged today, then confirm. You reach it from: * **Change hosting** on the Hosting card of the app's billing page, or **Change** on the Hosting row of its settings Summary. * **Upgrade hosting** on the instances, database and bandwidth meters, on the app's settings, billing and Hosting pages. * **Choose** in the hosting comparison table, and the upgrade buttons on the app's Hosting page. A bigger tier is charged now, prorated. A smaller one, or going back to the included hosting, waits for the renewal. See [Changing hosting](/billing#changing-hosting). ## Runtime add-ons Runtime add-ons turn a capability on for one app rather than raising a number: | Add-on | What it provisions | | :- | :- | | [Redis](/redis) | A dedicated 1 GiB Memorystore instance for the environment | | [Scheduler](/scheduler) | Cron jobs that call your app, with a job allowance | | [Object storage](/storage) | A private GCS bucket with 1 GB included, and more capacity per GB | | [CDN](/cdn) | Caches the app's static files at Google's edge on all its hostnames, and its public storage files | These are scoped to a single app, and their current prices are shown on the enable button in **Hosting**. Redis, Object storage and CDN are on or off: an app has at most one of each, since a second one would add nothing. More object storage is bought per GB, from **Hosting > Storage** or as **Object storage (per GB)** in **Add capacity**, once the app has Object storage. No plan or hosting tier includes object storage, and the extra GB end with it. Scheduler is the exception: each unit adds 5 more scheduled jobs, so an app can hold several. The [always-on server](/always-on-server), which keeps one instance warm so an environment never cold-starts, is not a runtime add-on. It is part of Enterprise only, and Meridian turns it on for the environment you name. ## Billing model Hosting upgrades and runtime add-ons are billed monthly, aligned to the organization's billing anniversary. One purchased mid-cycle is prorated to the next anniversary date, charged at once, starts working when that charge is paid, then renews monthly from that point. Each app's add-ons are its own: when two apps buy the same add-on, each keeps the units and capacity it bought, and removing or keeping units on one app never changes the other's. Removing one, or some of its units, takes effect at the next anniversary, not immediately, and nothing is refunded: the app keeps the capacity until then, and **Keep** on its billing page undoes the removal. See [Removing add-ons](/billing#removing-add-ons). ## What upgrades don't change A hosting upgrade raises an app's hosting limits. It doesn't change the app's plan: features, team size and support come from [the plan](/plans-1). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.