---
title: "CDN & cloud costs | Darwinium"
slug: "addional-costs"
description: "Understand CDN and cloud costs associated with Darwinium integrations and the infrastructure components that may incur usage charges."
updated: 2026-10-16T02:27:28Z
published: 2025-02-05T23:40:21Z
canonical: "docs.darwinium.com/addional-costs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CDN & cloud costs

## External Costs with your CDN/Cloud Vendor

Because Darwinium is deployed upon your infrastructure, there are additional 3rd party costs with your cloud vendor(s) associated with its operation. These costs may vary depending on the complexity of your solution, the time taken for it to execute (with CloudFlare), and whether you opt to store event data on your own infrastructure.

### Cloudflare (mandatory, if deploying via Cloudflare)

| Item | Description | Usage (per request**) |
| --- | --- | --- |
| Cloudflare Workers | A request matching one or more configured steps in a Darwinium Journey will cause a worker request. | 1 request, 30ms approx |
| Cloudflare Workers KV | In many cases label lookups will be performed on the edge in Cloudflare and it will use KV store reads. Setting labels incurs KV store writes. | 2 |

** based on a typical Darwinium login step containing 1 model with 1 *check label* rule For details on Cloudflare worker pricing, see: [https://developers.cloudflare.com/workers/platform/pricing/](https://developers.cloudflare.com/workers/platform/pricing/) - Sections: Workers, Workers KV

### AWS (mandatory, if deploying via AWS Cloudfront)

| Item | Description | Usage (per request) |
| --- | --- | --- |
| Lambda | A request matching one or more configured steps **but no steps that read or write to the response body** is satisfied through Viewer level functions. | 1 Viewer Request + 1 Viewer Response, both typically running with 61 mS execution time |
| Lambda: Origin | A request matching one or more configured steps **t****hat that read or write to the** **response body** is satisfied through an alternate pathway using a single OriginRequest lambda and a single Cloudfront Function. This configuration automatically occurs based upon your Darwinium step's configuration | 1 + 1 Cloudfront Function, typically running with 61mS execution time |

For detailed lambda pricing, see: [https://aws.amazon.com/lambda/pricing/](https://aws.amazon.com/lambda/pricing/)

### AWS Storage (Optional - if using your own S3 bucket for event storage)

More details on BYO S3 event storage can be found [here](/v1/docs/byo-s3-event-storage).

| Item | Description | Usage |
| --- | --- | --- |
| Amazon S3 | 2 records are stored in S3 per event: 1. Hashed PII & Non-PII event attributes 2. Encrypted PII event attributes | ~7GB/million events* |
| Backup of S3 objects | This is subject to customer data policies: - Frequency of backup - Retention of backups |  |

* Based on an average event producing: 5kb of Hashed PII & Non-pii attributes + 2kb encrypted PII (7kb total) For detailed s3 pricing, see: [https://aws.amazon.com/s3/pricing/](https://aws.amazon.com/s3/pricing/)