Pricing and plans

Your bill combines App, DB, and custom-domain resource charges with charges for eligible usage above the included allowances. Prices are in USD, excluding tax. Monthly charges are combined per account for Personal plans and per group for Business plans.

The App and DB resource price tables on this page apply to the Personal plan, which does not include a service level agreement (SLA). For the Business plan, we design the App and DB configuration to meet your requirements and quote resource charges individually. Contact us for configuration and pricing details.

Personal and Business plans differ in App and DB resource charges and custom-domain charges. Usage rates and allowance amounts are the same; HTTP, outbound transfer, and build allowances apply per Personal account or per Business group. DB processing allowances apply per DB on both plans.

The paid tier of the Personal plan is called the Pro plan. During the Free Trial, resource charges for eligible Apps and DBs are $0 for 30 days. HTTP requests, outbound data transfer, standard build time, and DB processing time above their included allowances, as well as custom domains, remain billable during the Free Trial.

A billing month runs from 00:00 on the first day (inclusive) to 00:00 on the first day of the next month (exclusive), Japan Standard Time (JST). HTTP, outbound transfer, and build allowances apply once per Personal account or Business group per billing month.

• HTTP, outbound transfer, and build allowances are shared by projects within the same Personal account or Business group. Business groups do not share allowances even when they have the same payer. Static and dynamic sites use the same HTTP rate.
• DB processing allowances are based on one DB on the same plan for 30 days (720 hours), prorated by active time within the billing month. Overages are calculated per DB and then combined for the Personal account or Business group; unused DB hours are not pooled.
• HTTP, outbound transfer, and build allowances reset at 00:00 on the first day of each month, Japan Standard Time (JST). Unused allowances do not roll over and cannot be exchanged between categories.
• A Personal account or Business group created mid-month receives that month's allowance once. Adding projects, members, or domains within it, or upgrading to paid usage, does not create another allowance.
• Only excess usage is charged. Requests are counted individually, transfer by byte, and builds by actual execution seconds. Usage is not rounded up to a million requests, a GB, or a minute.

HTTP requests

Each HTTP request for HTML, CSS, JavaScript, images, APIs, and other content counts separately. This is not a page-view count, and cached responses count too. Internal retries, health checks, traffic blocked before delivery, and failures caused by Kamui are excluded. The same request is not counted twice.

HTTP charge = max(monthly eligible requests − 500,000, 0) × $0.000002

Outbound data transfer

This covers data sent from your Apps to the public internet, including App responses sent for website delivery and App-initiated requests to external APIs.

Data sent by an App and its subsequent delivery to a visitor are not both counted. Inbound traffic, private traffic, routes with no transfer charge, and service-operation artifact transfers and internal retries are also excluded.

1 GB means 1,000,000,000 bytes.

Transfer charge = max(monthly eligible outbound GB − 5, 0) × $0.25

Standard build time

Billable time includes source checkout, dependency installation, compilation, image creation, and other build execution. Queue time, App placement and startup waits, and Kamui retries are excluded.

Failed builds caused by your code and canceled builds count for their actual execution time. Failures caused by the platform are waived. Redeploying or rolling back an existing image costs $0 in build charges if no new build runs. Concurrent builds each contribute their own execution seconds to the total. This rate applies to standard builds.

Build charge = max(monthly eligible execution seconds − 6,000, 0) ÷ 60 × $0.02

DB processing beyond the included hours costs $0.50 per hour. No processing overage is added within the allowance. DB resource charges apply separately.

Processing time included in the resource price

The table assumes one DB on the same plan for 30 days (720 hours). Hours are prorated by the time that plan was active within each billing month; they are not a fresh allocation every 30 days.

• Included hours apply separately to each DB. They cannot be transferred or shared with another DB, even within the same billing account, and do not roll over to the next month.
• Active time is elapsed time from DB creation to deletion, including periods without SQL execution. It is used to prorate the allowance and is distinct from DB processing time below.
• For partial-month use or plan changes, prorate each plan by its active time within the month and sum those allowances. Ownership transfers use the period assigned to each payer.

Monthly included hours = sum of each plan's (table allowance × active hours in the billing month ÷ 720 hours)

Example: Small for 15 days includes 10 hours × 360 hours ÷ 720 hours = 5 hours. Nano for 15 days followed by Small for 15 days includes 2.5 + 5 = 7.5 hours.

How processing time is counted

• Elapsed time in SQL execution is summed across all connections to the same DB. It is not a measure of CPU time alone.
• Waits during SQL execution, including lock waits and data read/write waits, count. Waiting for the next command without executing SQL does not count, whether inside or outside a transaction.
• Concurrent connections count separately. Two connections executing SQL for 10 seconds each at the same time count as 20 seconds.
• Time is aggregated in milliseconds without rounding each operation to a full minute or hour. One processing hour = 3,600 seconds = 3,600,000 milliseconds.

Overage calculation

Monthly overage for one DB = max(monthly DB processing hours − monthly included hours, 0) × $0.50

Convert all time values in this formula to hours. Fractions of an excess hour are charged proportionally. Calculate each DB's overage first, then combine the amounts for the Personal account or Business group.

Example: Small for 30 days with 10 hours 30 minutes of processing exceeds its allowance by 30 minutes (0.5 hours): 0.5 hours × $0.50 = $0.25. At 30 processing hours, the charge is 20 excess hours × $0.50 = $10. DB resource charges are added separately in both cases.

Each row shows monthly usage within one Personal account or one Business group. The DB example assumes 30 days of use. Resource charges, other categories, and tax are excluded.

A $0 transfer charge for static delivery does not remove separate HTTP or build charges above their allowances.

• At account registration, you agree that HTTP requests, outbound data transfer, standard build time, and DB processing time above their included allowances incur the usage rates in the pricing table.
• Based on this consent, overages are calculated automatically and billed monthly to the billing account. No separate activation per category or additional consent when an allowance is exceeded is required. Usage before consent is not billed retroactively.
• Exceeding an included allowance does not cause HTTP delivery, eligible outbound traffic, standard builds, or DB processing to stop or be restricted. Overages from builds and DB processing already in progress are also calculated at the corresponding usage rates.
• Notifications are sent at 80% and 100% of each allowance, with account totals and per-project usage and estimated charges. Usage continues after notifications, and usage above the allowances remains billable.
• Usage charges are combined per Personal account or Business group per month and rounded to the nearest cent ($0.01), with half a cent rounded up ($0.005 becomes $0.01). Bills below $0.50 carry forward within the same billing unit; they are not rounded up to $0.50. Business groups do not share carryover.
• Usage before an ownership transfer remains with the previous payer; subsequent usage belongs to the new payer. Missing or unattributed usage is not estimated for additional billing, and duplicate records are not billed twice.

The following calculation rules apply to the Personal plan. App and DB resource charges and custom-domain charges for the Business plan follow the individual quote.

The chargeable period runs from creation to deletion for Apps and DBs, and from registration with Kamui to removal of that registration for custom domains. Displayed resource prices are per App replica, per DB, or per domain. Resource charges apply even without requests. Resource charges for eligible Free Trial Apps and DBs are $0.

Within each billing month, billable time is summed across replicas for each App and specification, separately for each DB and specification, and separately for each registered domain. Each total is converted to minutes, with fractional minutes rounded up.

Charges are prorated using 30 days = 43,200 minutes. Before monetary rounding, using one replica, DB, or domain for 31 days costs 31/30 of its displayed 30-day price.

Resource charge before monetary rounding = 30-day price × billable minutes ÷ 43,200

For each of these billing items, the amount is first rounded down to the nearest $0.001, then rounded up to the nearest $0.01. The resulting amounts are added together. These rounding rules do not apply to usage charges; those follow the rules under "Usage billing and notifications."

Applicable taxes are calculated or shown according to billing details. Card-company and payment-processor exchange rates and settlement dates are outside our control. See "App and database resource pricing" at the top of this page for resource prices and specifications.

Static sites

• Static sites have a $0 base hosting charge. Eligible HTTP and build usage is calculated separately.
• Worldwide delivery supports up to 25 MiB (26,214,400 bytes) and 300 files per site. Pro projects allow up to 2 static sites each.

App Resource Limits and Replicas

• CPU, memory, and ephemeral storage limits apply to each replica.
• Ephemeral storage may be lost during deployments, restarts, or changes to the execution environment. Store persistent data in a DB or another persistent service.
• Before time and monetary rounding, running 2 replicas of the same type for the same period costs twice as much as running 1 replica.
• Maintenance and recovery from service disruptions may restart Apps. A single-replica App may experience brief downtime. We recommend 2 or more replicas for higher availability, but this does not guarantee uninterrupted operation.

DB Resource Limits

• The connection, storage, statement execution, idle-in-transaction, and temporary-file limits in the resource price tables apply to each DB type.
• SQL statements that exceed the statement timeout may be canceled.
• If a DB exceeds its storage limit, INSERT, UPDATE, and creation of new objects may be restricted while SELECT and DELETE remain available so that usage can be reduced.