FireWeekly

Products · Developer platform

Artifacts

Store, version, and share filesystem artifacts across Workers, APIs, and git-compatible tools

Documentationllms.txt

Pricing and limits

Pricing

as of Nov 3, 2026

As of Nov 3, 2026, from Cloudflare's docs, last updated there Oct 28, 2026. Licensed CC BY 4.0; navigation removed.

Artifacts is currently only available on the Workers Paid plan.

Note

Cloudflare will begin billing for Artifacts operations and storage on November 12, 2026.

Artifacts pricing is billed on two dimensions:

  • Operations: the number of repo operations, such as create, push, pull, and clone.
  • Storage: the total amount of stored data, measured in gigabyte-months ( GB-mo).

Artifacts pricing

Unit Workers Free Workers Paid
Operations (1,000 operations) Unavailable First 10,000 per month + $0.15 per additional 1,000 operations
Storage (GB-mo) Unavailable First 1 GB per month + $0.50 per additional GB-mo

Storage usage

Storage is billed using gigabyte-month (GB-mo) as the billing metric, identical to Durable Objects SQL storage. A GB-mo is calculated by averaging peak storage per day over a 30-day billing period.

  • Storage is calculated across all repositories.
  • Replicas do not add storage charges. Storage is replicated by default, and you do not need to manage repository availability or uptime.
  • Repos remain stored until you explicitly delete them.

Limits

as of Nov 3, 2026

As of Nov 3, 2026, from Cloudflare's docs, last updated there Oct 28, 2026. Licensed CC BY 4.0; navigation removed.

Limits that apply to creating, importing, cloning, and pushing Artifacts are detailed below.

These limits cover naming rules, storage, request rates for control-plane and Git operations, and the size of each push.

Feature Limit
Control-plane request rate 2,000 requests per 10 seconds per Artifacts namespace
Git request rate, per artifact 2,000 requests per 10 seconds per artifact
Maximum storage per repository 1 GB for repos created on or after 2026-09-29. Repos created earlier have a 10 GB limit. See size limit change.
Maximum storage per account 1 TB (can be raised on request)
Maximum number of repositories Unlimited
Maximum number of namespaces Unlimited
Namespace name length 2–63 characters
Namespace and repo names Start with a letter or digit. Remaining characters may include letters, digits, ., _, and -.
Maximum push size 64 MiB per push. Includes all data sent in the push. Split larger work into several smaller pushes.
Maximum objects per push 50,000 objects, such as file versions, folders, and commits.
Maximum file size 32 MiB per file. Already-compressed files, like images, video, or zip archives, may be rejected slightly below 32 MiB.
Maximum ref updates per push 1 MiB of branch and tag updates per push.
Maximum entries per folder 100,000 files and subfolders in a single folder.

Timeline

12 entries since February 2024.

October 2026

September 2026

  • 1 GB storage limit for new Artifacts repos

    Starting September 29, 2026, Artifacts will enforce a 1 GB storage limit per repo for repos created on or after that date. Repos created before September 29, 2026, will retain their 10 GB storage limit. For more information, refer to Artifacts limits.

August 2026

  • Data localization support for Artifacts

    Artifacts now supports jurisdictions, allowing you to select the European Union or the United States as the only location where repo data is stored and processed. Select a jurisdiction when you create a namespace. Every repo in that namespace automatically uses the selected jurisdiction. curl --request POST \ "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/artifacts/namespaces" \ --hea…

  • Build and deploy Artifacts repos on every push

    You can now run your CI/CD pipeline on your Artifacts repo by defining a CI Workflow with the CI SDK ↗︎, automatically triggered on Artifacts push events. This allows you to: Automatically build and deploy application code stored in Artifacts. Run linting, type checking, tests, and other checks on every push. Reuse dependencies when the lockfile (i.e. pnpm-lock.yaml) has not changed. Stop deploym…

June 2026

  • Manage Artifacts from the Cloudflare dashboard

    You can now configure Artifacts namespaces, repos, and tokens directly from the Cloudflare dashboard. Artifacts is Git-compatible storage that lets you store repos on Cloudflare and interact with them using standard Git workflows. You can view and create namespaces, which are top-level containers for repos: You can view, create, fork, and search repos within a namespace: You can open a repo to vi…

May 2026

  • Event subscriptions for Artifacts lifecycle events

    You can now receive event notifications for Artifacts repository changes and consume them from a Worker to build commit-driven automation. This allows you to: Run custom workflows when a repository is created or imported Kick off a build and deploy a change when an agent pushes to a repo Trigger a review agent on every push Available events include: Account-level events (artifacts source) — repo.…

  • Manage Artifacts namespaces and repos with Wrangler CLI

    You can now manage Artifacts namespaces, repos, and repo-scoped tokens directly from Wrangler CLI. Available commands: wrangler artifacts namespaces list — List Artifacts namespaces in your account. wrangler artifacts namespaces get — Get metadata for a namespace. wrangler artifacts repos create — Create a repo in a namespace. wrangler artifacts repos list — List repos in a namespace. wrangler ar…

April 2026

  • Artifacts now in beta: versioned filesystem with Git access

    Artifacts is now in private beta. Artifacts is Git-compatible storage built for scale: create tens of millions of repos, fork from any remote, and hand off a URL to any Git client. It provides a versioned filesystem for storing and exchanging file trees across Workers, the REST API, and any Git client, running locally or within an agent. You can read the announcement blog ↗︎ to learn more about w…