> ## Documentation Index > Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These are the docs for Sevalla, a platform for deploying applications, databases, static sites, object storage and load balancers. The dashboard is at https://app.sevalla.com. > Bold text in steps is an exact dashboard label. > To act on a Sevalla account, prefer the Sevalla MCP server (https://mcp.sevalla.com/mcp, see https://docs.sevalla.com/ai-agents/overview.md), then the Sevalla CLI (https://docs.sevalla.com/developer-tools/cli.md), then the REST API (https://api-docs.sevalla.com, OpenAPI spec at https://api.sevalla.com/v3/openapi.json). > Every page index is at https://docs.sevalla.com/llms.txt. # Pricing > Every Sevalla price: application process sizes, disks, build time, bandwidth, database sizes, static site allowances, object storage and load balancers, in USD before tax. Sevalla prices every resource per unit of use, in USD, before tax. Running resources are billed by the second, bandwidth by the byte, and stored objects by size per month. A month in these prices is 730 hours: a resource that runs all of a 31-day month (744 hours) costs 744/730 of its monthly price. For how billing periods, invoices and credit work, see [How billing works](/billing/overview). ## How to read the prices * **Prices exclude tax.** The dashboard's cost estimates in the create forms include the tax for your billing address, so they can be higher than this page. See [Taxes](/billing/taxes). * **Per instance.** A process with 3 instances costs 3 times its size's price for as long as the instances run. * **Per second.** The hourly prices are the monthly price divided by 730, rounded to 4 decimals. Sevalla bills the exact seconds. * **1 GB is 1,000,000,000 bytes.** Bandwidth costs \$0.0000000001 per byte, so there's no rounding up to whole gigabytes. ## Applications An application is billed for its processes' compute, its disks, its build time and its bandwidth. ### Process sizes Every process (web, worker, cron or job) runs on one size. **CPU** and **RAM** are per instance. | Size | Category | CPU | RAM | Per month | Per hour | | - | - | - | - | - | - | | H1 | Hobby | 0.3 | 0.3 GB | \$5 | \$0.0068 | | S1 | Standard | 0.5 | 1 GB | \$10 | \$0.0137 | | S2 | Standard | 1 | 2 GB | \$40 | \$0.0548 | | S3 | Standard | 2 | 4 GB | \$80 | \$0.1096 | | S4 | Standard | 4 | 8 GB | \$160 | \$0.2192 | | S5 | Standard | 8 | 16 GB | \$320 | \$0.4384 | | C1 | CPU optimized | 1 | 1 GB | \$18 | \$0.0247 | | C2 | CPU optimized | 2 | 2 GB | \$68 | \$0.0932 | | C3 | CPU optimized | 4 | 4 GB | \$135 | \$0.1849 | | C4 | CPU optimized | 8 | 8 GB | \$270 | \$0.3699 | | M1 | Memory optimized | 0.5 | 2 GB | \$20 | \$0.0274 | | M2 | Memory optimized | 1 | 4 GB | \$70 | \$0.0959 | | M3 | Memory optimized | 2 | 8 GB | \$135 | \$0.1849 | | M4 | Memory optimized | 4 | 16 GB | \$250 | \$0.3425 | | M5 | Memory optimized | 8 | 32 GB | \$480 | \$0.6575 | A process is billed only while it has running instances. Cron jobs and jobs are billed for the seconds each run takes, and a process that's scaled to zero or [hibernated](/applications/scaling) costs nothing for compute. A web process on H1 can't have [custom domains](/domains/overview). To choose or change sizes, see [Scaling](/applications/scaling). ### Disks A [disk](/applications/disks) costs \$0.30 per GB per month and is billed by the second while the process it's attached to is running. | Size | Per month | | - | - | | 10 GB | \$3 | | 20 GB | \$6 | | 50 GB | \$15 | | 100 GB | \$30 | | 150 GB | \$45 | | 200 GB | \$60 | | 300 GB | \$90 | | 400 GB | \$120 | | 500 GB | \$150 | | 750 GB | \$225 | | 1,000 GB | \$300 | ### Build time Applications built from Git cost \$0.02 per minute of build time, billed by the second. Applications deployed from a Docker image aren't built, so they have no build time. Cancelling a deployment that's building stops its build time. See [Deployments](/applications/deployments). ### Bandwidth Application bandwidth costs \$0.10 per GB. It counts the response data that your application's domains (its `sevalla.app` domain and custom domains) send to visitors. Incoming requests and traffic over [internal connections](/applications/networking) are free. ## Databases A database is billed by the second while it runs, at its size's price. The price includes the size's CPU, RAM and storage. A suspended database isn't billed. | Size | CPU | RAM | Storage | Per month | Per hour | | - | - | - | - | - | - | | DB1 | 0.25 | 0.25 GB | 1 GB | \$5 | \$0.0068 | | DB2 | 0.5 | 2 GB | 5 GB | \$34 | \$0.0466 | | DB3 | 1 | 4 GB | 10 GB | \$65 | \$0.0890 | | DB4 | 2 | 8 GB | 20 GB | \$145 | \$0.1986 | | DB5 | 4 | 16 GB | 40 GB | \$310 | \$0.4247 | | DB6 | 8 | 32 GB | 60 GB | \$800 | \$1.0959 | | DB7 | 14.5 | 58 GB | 80 GB | \$1,200 | \$1.6438 | | DB8 | 28.5 | 108.5 GB | 90 GB | \$1,850 | \$2.5342 | | DB9 | 58.5 | 229 GB | 100 GB | \$3,250 | \$4.4521 | Database traffic isn't billed: neither internal connections from applications nor [external connections](/databases/connect). The dashboard marks DB1 as not recommended for production. To change a database's size, see [Database settings](/databases/settings). ## Static sites Static site hosting has no monthly fee. Each company gets a free allowance every billing period, shared by all its static sites: | Resource | Free per billing period | Beyond the allowance | | - | - | - | | Bandwidth | 100 GB | \$0.10 per GB | | Build time | 600 minutes | \$0.05 per minute, billed by the second | See [Static sites](/static-sites/overview). ## Object storage | Resource | Price | | - | - | | Stored data | \$0.02 per GB per month | | Operations (reads, writes, lists) | Free | | Egress | Free | Sevalla measures each bucket's peak stored size every hour and bills that hour's share of the monthly price. There's no free allowance. See [Object storage](/object-storage/overview). ## Load balancers | Resource | Price | | - | - | | Base fee | $40 per month per load balancer ($0.0548 per hour), billed by the second | | Bandwidth | \$0.10 per GB of response data sent to visitors | See [Load balancers](/load-balancers/overview). ## Example Acme Inc runs the `storefront` application and the `orders-db` database for all of October (31 days, 744 hours): | Resource | Usage | Cost | | - | - | - | | `storefront` web process, S2, 2 instances | 2 × 744 hours × \$40 / 730 hours | \$81.53 | | `storefront` worker process, S1, 1 instance | 744 hours × \$10 / 730 hours | \$10.19 | | Build time | 120 minutes × \$0.02 | \$2.40 | | Bandwidth | 50 GB × \$0.10 | \$5.00 | | `orders-db`, DB3 | 744 hours × \$65 / 730 hours | \$66.25 | | **Total before tax** | | **\$165.37** | If Acme Inc deleted `storefront` on Oct 10, its compute would stop on Oct 10, and October's invoice would include only the seconds it ran. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.