Atlas bills Atlas Triggers according to how much they're used on a daily basis. Three independently-measured usage types determine how much you pay each day:
Requests, which measures the number of trigger executions.
Compute, which measures the runtime and memory usage of trigger executions.
Data Transfer, which measures the amount of data that triggers send to external services.
Daily Free Tier
All Triggers in a Atlas project have a daily free tier. Atlas doesn't bill usage below the following daily free tier thresholds:
50,000 requests
25 hours of compute
0.5 GB of data transfer
Invoicing and Payment
Your MongoDB Atlas bill includes a line item for Triggers. Atlas sends invoices monthly that include all costs incurred from going over the daily free tier thresholds.
You can pay for Triggers with all payment methods that work with Atlas, including prepaid Atlas Credits. Atlas bills any costs associated with a linked Atlas cluster, such as database operations and backup, separately from Triggers.
To learn more, see Manage Billing.
Usage Types
Requests
Atlas counts each fired trigger as a request. A trigger can fire when a document is inserted, changed, or deleted (database trigger) or according to a schedule (scheduled trigger). The trigger request includes all operations that the trigger invokes, including functions and AWS EventBridge forwarding.
Price: Tiered daily rates based on the number of requests:
$2.00 / 1,000,000 requests ($0.000002 / request) for the first 25,000,000 requests
$1.00 / 1,000,000 requests ($0.000001 / request) for requests 25,000,001 to 250,000,000
$0.75 / 1,000,000 requests ($0.00000075 / request) for requests above 250,000,000
Free Tier Threshold: 50,000 requests
Compute
Atlas counts the total time and memory that each 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, which doesn't affect your billing rate. The multiplier increases by 1 for every 32 MB of memory that a request uses.
Price: $10.00 / 500 runtime hours (~$0.000000005 / ms)
Formula: (Number of Requests) * (Runtime (ms)) * (Memory (MB) / 32 MB) * $0.000000005 / ms
Free Tier Threshold: 25 hours
Data Transfer
Atlas measures the total amount of data that your triggers send to 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 External Services (GB)) * ($0.12 / GB)
Free Tier Threshold: 0.5 GB
Note
Atlas Data Transfer
Atlas bills data transfer from a linked Atlas cluster to Triggers as an Atlas Data Egress charge. To learn more about Atlas egress rates, see Data Transfer Costs.
Example
An international restaurant chain uses Atlas Triggers to handle orders for all of its locations:
The chain has 18,000 locations, and each location gets about 400 orders each day.
The locations operate 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 takes too long, it sends a text message update to the customer. About 10% of all deliveries take too long.
Orders vary in size but are no larger than 4 KB.
The following calculations approximate the cost of running these triggers for one day:
Usage Type | Calculation |
|---|---|
| |
| |
| |
TOTAL | $76.07 (requests) + $76.23 (compute) + $24.48 (data transfer) = $176.78 for the day |
Note
Free Tier Usage
The way that free tier usage affects your bill depends on your consumption each day. Consumption can look different on any individual day.
The example usage exceeds the requests, compute, and data transfer free tier thresholds. The free tier would cover the following usage in each area:
Requests: 50,000 requests
Compute: 25 hours
Data Transfer: 0.5 GB