Billing

Free Tier Thresholds

App Services is free to use below the following daily free tier thresholds:

• 50,000 requests

• 25 hours of compute

• 30,000 minutes of sync runtime

• 0.5 GB of data transfer

App Services Requests

App Services counts the number of requests that an application receives and handles. Requests are billed at a set rate for each request.

There are several types of requests:

• Function Executions, such as when a user calls a function from a client app, when a function calls an external service, or when a custom error handler is invoked by a failed EventBridge trigger. If an executing function calls another function, App Services considers both executions as part of the same request.

• Trigger Executions, such as when a database trigger matches a change event, a scheduled trigger is configured to fire, or an authentication trigger responds to a user login. The request resulting from a trigger execution also includes all operations invoked by the trigger, including functions and EventBridge forwarding.

• GraphQL Requests, such as when a client application issues a GraphQL query operation or calls a custom resolver. (GraphQL is deprecated. Learn more)

• HTTPS Requests, such as when an external service sends a notification event or interaction payload to an incoming webhook or HTTPS endpoint.

• Sync Operations, such as when a sync client uploads a changeset, when App Services resolves a conflict in an uploaded changeset, or when App Services sends changesets to a connected sync client.

  For more information on sync operations, see Atlas Device Sync Protocol.

All incoming requests count toward your daily usage except for the following:

• Requests to an authentication provider

• Requests blocked by an application's IP Access List

• Requests to an invalid HTTP endpoint

Price: $2.00 / 1,000,000 requests ($0.000002 / request)

Formula: (Function Executions + Trigger Executions + GraphQL/Webhook/HTTPS Endpoint Requests + Sync Updates) * $0.000002

Free Tier Threshold: 50,000 requests, 25 hours of compute, and 30,000 minutes of sync runtime

App Services Compute

App Services counts the total amount of time and memory that each non-sync application request takes to process. Compute is billed at a set rate for each millisecond of runtime. For large requests, this rate is multiplied by a factor that reflects the amount of memory the request used.

The memory multiplier begins at 1 (i.e. it does not affect your billing rate) and increases by 1 for every 32MB of memory that a given request uses.

Price: $10.00 / 500 runtime hours (~$0.000000005 / ms)

Formula: (Number of Requests) * (Runtime (ms)) * (Memory (MB) / 32MB) * $0.000000005 / ms

Free Tier Threshold: 50,000 requests, 25 hours of compute, and 30,000 minutes of sync runtime

Atlas Device Sync

App Services counts the total amount of time in which a client application user has an active connection to the sync server even if they are not transferring data at the time. Sync is billed at a set rate for each millisecond of sync runtime per user.

Price: $0.08 / 1,000,000 runtime minutes ($0.00000008 / min)

Formula: (Number of Active Users) * (Sync Time (min / user)) * ($0.00000008 / min)

Free Tier Threshold: 50,000 requests, 25 hours of compute, and 30,000 minutes of sync runtime

Device Sync pauses automatically after 30 days of inactivity.

Data Transfer

App Services measures the total amount of data that your application sends out to client applications and external services. Data transfer is billed at a set rate for each gigabyte of data egress.

Price: $0.12 per GB

Formula: (Data Sent to Clients/Services (GB)) * ($0.12 / GB)

Free Tier Threshold: 10 GB

Mobile Application

A group messaging application uses App Services to manage permissions and sync messages between users in the same group. The app has the following usage:

• There are around 2,000 active group chats in any given day.

• The average group chat has 4 users that each send around 20 messages each day.

• Messages are usually small but may contain up to 2KB of data.

• The average user has the app open for about 1 hour each day.

The following calculations approximate the cost of running this application for one day:

Web Application

A hardware store uses a web application that allows customers to browse and order items online. The app uses Atlas Functions to fetch items based on a user's search, get detailed information for specific items, and submit orders. The app has the following usage:

• There are around 3,000 visitors each day.

• An average visitor performs 2 searches, looks at 10 items, and submits an order 20% of the time.

• Search results, item data, and order requests contain 4KB or less.

The following calculations approximate the cost of running this application for one day:

Backend Application

An international pizza chain uses App Services to handle orders for all of its restaurants. The app has the following usage:

• The chain has 18,000 stores, and each store gets about 400 orders each day.

• The stores are in operation for 16 hours each day.

• For each order, a database trigger sends the customer an email receipt. Another trigger sends text message updates to the customer when their order is received, when it's sent out for delivery, and when it's about to be delivered.

• A scheduled trigger runs every 5 minutes to monitor delivery times. If a delivery is taking too long, it sends a text message update to the user. About 10% of all deliveries take too long.

• Orders vary in size but are no larger than 4KB.