---
title: "Pricing and Billing"
description: "The Free and Pay as you go options, the free allowance, the usage rates, the billing cycle, the spending limit, billing alert thresholds, and every limit that applies to an organization, its configs, and the Admin API"
canonical_url: "https://docs.configdirector.com/getting-started/pricing-and-billing"
---
# Pricing and Billing

> The Free and Pay as you go options, the free allowance, the usage rates, the billing cycle, the spending limit, billing alert thresholds, and every limit that applies to an organization, its configs, and the Admin API

ConfigDirector has two pricing options, and an organization is on exactly one of them:

- **Free**: no payment method on file. Usage is capped at the free allowance, and the organization can have up to 5 projects and 100 configs.
- **Pay as you go**: a payment method is on file. The same free allowance applies every month, and usage beyond it is billed at the published rates. There is no monthly fee, and projects, configs, seats, and environments are unlimited.

Prices are in USD, plus applicable tax. The [pricing page](https://www.configdirector.com/pricing) has a cost estimator; this page explains how the billing works.

<div hidden="true" dataUniformTables="">



</div>

## Billing metrics

Three usage quantities are metered. Everything else, including seats, environments, evaluations, and alerts, is free.

<table>
<thead>
  <tr>
    <th>
      Metric
    </th>
    
    <th>
      What is counted
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Monthly active users
    </td>
    
    <td>
      A distinct user, device, or other context that your client apps identify to ConfigDirector in a calendar month, or a distinct app install or browser that evaluates configs without identifying anyone. Each one counts once a month across all your projects and environments: the same identifier signed in on two devices counts once, and a person who uses your app anonymously and then signs in counts twice. Only client SDKs count: the browser and mobile SDKs, and the browser side of the Next.js and Nuxt SDKs.
    </td>
  </tr>
  
  <tr>
    <td>
      Service connection hours
    </td>
    
    <td>
      The hours server SDKs spend connected or persistently polling. A server SDK in <code>
        polling
      </code>
      
       mode counts 5 minutes per request, which at the default 5-minute interval matches a <code>
        streaming
      </code>
      
       connection. 750 hours covers one server connected all month, with a buffer for deploys and traffic spikes.
    </td>
  </tr>
  
  <tr>
    <td>
      Admin API requests
    </td>
    
    <td>
      Calls to the Admin API, including every tool call made through the <a href="https://docs.configdirector.com/integrations/mcp">
        MCP server
      </a>
      
       and every change applied by the <a href="https://docs.configdirector.com/integrations/terraform">
        Terraform provider
      </a>
      
      . Dashboard use and SDK evaluations are not Admin API requests.
    </td>
  </tr>
</tbody>
</table>

An app install or a browser that evaluates configs without identifying anyone is recognized by the instance ID the client SDK keeps in the app's or the browser's own storage. When the SDK cannot store it, for example in a React Native app without AsyncStorage, every app start counts as one more monthly active user.

For example, a web app used every day by 2,000 people who sign in counts 2,000 monthly active users, however often each of them opens it. Browsers that evaluate configs before their person signs in count as well. One server connected all month uses about 730 service connection hours, and a nightly Terraform plan that reads 40 resources uses about 1,200 Admin API requests a month.

## The free allowance

Every month, each organization gets this allowance at no cost, on Free and on Pay as you go alike:

<table>
<thead>
  <tr>
    <th>
      Metric
    </th>
    
    <th>
      Free allowance per month
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Monthly active users
    </td>
    
    <td>
      1,000
    </td>
  </tr>
  
  <tr>
    <td>
      Service connection hours
    </td>
    
    <td>
      2,250, about 3 servers connected continuously all month
    </td>
  </tr>
  
  <tr>
    <td>
      Admin API requests
    </td>
    
    <td>
      10,000
    </td>
  </tr>
</tbody>
</table>

On Free, the allowance is a cap. When a Free organization goes past the allowance of a metric, a [free allowance exceeded](https://docs.configdirector.com/monitoring/alerts#free-allowance-exceeded) alert is raised and a **billing grace period** of 7 days starts, in which the organization can start pay as you go. The alert names the date and time the grace period ends. If the grace period ends with usage still over the allowance, service is suspended: the service stops accepting SDK connections and closes the open ones, so your applications fall back to the in-code default value they pass to the SDK, and the Admin API and the MCP server refuse requests, all with `429 Too Many Requests` and a `Retry-After` header, as described under [Spending limit](#spending-limit). The dashboard keeps working and shows a banner. A [service suspended: free allowance exceeded](https://docs.configdirector.com/monitoring/alerts#service-suspended-free-allowance-exceeded) alert is raised and emailed. Service is reinstated as soon as pay as you go starts, or shortly after the next billing cycle begins.

On Pay as you go, the allowance is the first price tier, priced at zero. Nothing is charged until usage goes past it.

## Pay as you go rates

Usage beyond the free allowance is priced in tiers. A tier's rate applies only to the usage that falls inside it, so the free allowance stays free and the rate drops as usage grows.

<table>
<thead>
  <tr>
    <th>
      Monthly active users
    </th>
    
    <th>
      Per 1,000 users
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      First 1,000
    </td>
    
    <td>
      Free
    </td>
  </tr>
  
  <tr>
    <td>
      1,000 to 500,000
    </td>
    
    <td>
      $5.00
    </td>
  </tr>
  
  <tr>
    <td>
      500,000 to 1,000,000
    </td>
    
    <td>
      $3.75
    </td>
  </tr>
  
  <tr>
    <td>
      Over 1,000,000
    </td>
    
    <td>
      $2.50
    </td>
  </tr>
</tbody>
</table>

<table>
<thead>
  <tr>
    <th>
      Service connection hours
    </th>
    
    <th>
      Per 750 hours
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      First 2,250
    </td>
    
    <td>
      Free
    </td>
  </tr>
  
  <tr>
    <td>
      2,250 to 7,500
    </td>
    
    <td>
      $6.00
    </td>
  </tr>
  
  <tr>
    <td>
      7,500 to 22,500
    </td>
    
    <td>
      $5.00
    </td>
  </tr>
  
  <tr>
    <td>
      Over 22,500
    </td>
    
    <td>
      $3.50
    </td>
  </tr>
</tbody>
</table>

<table>
<thead>
  <tr>
    <th>
      Admin API requests
    </th>
    
    <th>
      Per 10K requests
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      First 10,000
    </td>
    
    <td>
      Free
    </td>
  </tr>
  
  <tr>
    <td>
      10,000 to 250,000
    </td>
    
    <td>
      $1.00
    </td>
  </tr>
  
  <tr>
    <td>
      250,000 to 1,000,000
    </td>
    
    <td>
      $0.75
    </td>
  </tr>
  
  <tr>
    <td>
      Over 1,000,000
    </td>
    
    <td>
      $0.50
    </td>
  </tr>
</tbody>
</table>

For example, 600,000 monthly active users in a month cost nothing for the first 1,000, $2,495.00 for the next 499,000 at $5.00 per 1,000, and $375.00 for the last 100,000 at $3.75 per 1,000: $2,870.00 in all.

Organizations with usage, capacity, or support needs beyond these rates can ask for [custom pricing](https://www.configdirector.com/custom-pricing).

## The billing cycle

The billing cycle is the calendar month in UTC. Usage counts reset at the start of each month, and the free allowance applies again.

On Pay as you go, the month's usage above the free allowance is invoiced on the first day of the following month and charged to the payment method on file. The **Billing & usage** page in the dashboard shows the month so far: each metric against the free allowance on the **Usage** tab, with the month-to-date spend in total and per metric, and the invoices and receipts on the **Invoices & Receipts** tab.

If a payment fails, service keeps running. The **Billing** tab shows the failed payment, and updating the payment method retries it.

## Starting pay as you go

On the **Billing** tab of the **Billing & usage** page, **Start pay as you go** shows the rates and asks for a payment method. Pay as you go is active as soon as the payment method is saved, with no interruption in service. Owners and billing managers can do this, and every other billing change described on this page.

An organization that chose Pay as you go at sign-up stays on Free until a payment method is added; the dashboard reminds you until then.

## Switching to Free

**Switch to Free** on the **Billing** tab schedules the switch for the end of the current billing cycle. Usage until then is invoiced at the published rates, and the organization returns to Free when the cycle ends. Until then, the switch can be undone with **Resume**. An organization must be within the Free limits of 5 projects and 100 configs to switch; the dashboard says what to remove if it is not.

The spending limit and the billing alert thresholds are removed when the organization returns to Free, and the free allowance applies as a cap again.

## Spending limit

A Pay as you go organization can set a **spending limit**: a dollar amount per billing cycle, of at least $1.00, that the invoice never exceeds. It is set and removed on the **Billing** tab.

The spend alerts track the limit. When the month's spend is on track to reach it, a [spend projected to reach the spending limit](https://docs.configdirector.com/monitoring/alerts#spend-projected-to-reach-the-spending-limit) alert is raised at 70% and again at 90% of the limit. When spend reaches the limit, a [spending limit reached](https://docs.configdirector.com/monitoring/alerts#spending-limit-reached) alert is raised and service is suspended for the rest of the billing cycle: the service stops accepting SDK connections and closes the open ones, so your applications fall back to the in-code default value they pass to the SDK, and the Admin API and the MCP server refuse requests. The dashboard keeps working. Nothing above the limit is charged.

While service is suspended, the SDK endpoints, the Admin API, and the MCP server answer every request with `429 Too Many Requests` and a `Retry-After` header. The SDKs keep retrying in the background with their usual backoff, so they pick up where they left off once service resumes, without a restart. The dashboard shows a banner with a link to the spending limit.

Service resumes as soon as the limit is raised or removed, or shortly after the next billing cycle starts. Raising or removing the limit takes effect right away and resolves the open spending limit alerts. Setting the limit below the month's spend so far is allowed; the next hourly check raises the reached alert and suspends service. Without a spending limit, the service keeps running whatever the usage, and all of it is billed at the published rates.

## Billing alert thresholds

A Pay as you go organization can add up to 5 **billing alert thresholds**, each a distinct dollar amount of monthly spend with a priority of Medium, High, or Critical. When the month's spend reaches a threshold, a [billing alert threshold reached](https://docs.configdirector.com/monitoring/alerts#billing-alert-threshold-reached) alert is raised at that priority. Thresholds never affect the service; they are a heads-up about the invoice to come.

Threshold alerts are emailed to owners, admins, and billing managers at the priority chosen for the threshold: Critical right away and Medium or High in the daily digest. A threshold above the spending limit never fires, since the invoice never exceeds the limit.

Thresholds are managed on the **Billing** tab. Editing or deleting a threshold resolves its open alert right away, and raising a threshold during the month arms it again.

## Limits

Every limit below applies on Free and on Pay as you go alike, unless the table says otherwise. A save that goes over a limit is refused with a message naming it, in the dashboard and the Admin API alike.

### Organization

<table>
<thead>
  <tr>
    <th>
      Limit
    </th>
    
    <th>
      Value
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Projects
    </td>
    
    <td>
      5 on Free, unlimited on Pay as you go
    </td>
  </tr>
  
  <tr>
    <td>
      Configs, across the organization
    </td>
    
    <td>
      100 on Free, unlimited on Pay as you go
    </td>
  </tr>
  
  <tr>
    <td>
      Members
    </td>
    
    <td>
      Unlimited
    </td>
  </tr>
  
  <tr>
    <td>
      Member invitations
    </td>
    
    <td>
      50 per organization and 6 per email address, in any 24 hours
    </td>
  </tr>
  
  <tr>
    <td>
      Organization name
    </td>
    
    <td>
      300 characters
    </td>
  </tr>
</tbody>
</table>

### Projects and environments

<table>
<thead>
  <tr>
    <th>
      Limit
    </th>
    
    <th>
      Value
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Environments per project
    </td>
    
    <td>
      Unlimited. <code>
        Test
      </code>
      
       and <code>
        Production
      </code>
      
       are created with the project.
    </td>
  </tr>
  
  <tr>
    <td>
      Project name and slug
    </td>
    
    <td>
      255 characters each
    </td>
  </tr>
  
  <tr>
    <td>
      Environment name
    </td>
    
    <td>
      200 characters
    </td>
  </tr>
  
  <tr>
    <td>
      Environment slug
    </td>
    
    <td>
      150 characters
    </td>
  </tr>
  
  <tr>
    <td>
      Client SDK keys per environment
    </td>
    
    <td>
      5
    </td>
  </tr>
  
  <tr>
    <td>
      Server SDK keys per environment
    </td>
    
    <td>
      5
    </td>
  </tr>
  
  <tr>
    <td>
      Tags per project
    </td>
    
    <td>
      Unlimited. A tag name is 1 to 50 characters, unique in the project ignoring case.
    </td>
  </tr>
</tbody>
</table>

### Configs and values

<table>
<thead>
  <tr>
    <th>
      Limit
    </th>
    
    <th>
      Value
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Config key
    </td>
    
    <td>
      4 to 150 characters: letters, numbers, periods, dashes, and underscores, starting with a letter or number. Unique in the project.
    </td>
  </tr>
  
  <tr>
    <td>
      Old keys kept after a rename
    </td>
    
    <td>
      2 at a time. See <a href="https://docs.configdirector.com/getting-started/configs#key">
        Configs Anatomy
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      Description
    </td>
    
    <td>
      1,000 characters
    </td>
  </tr>
  
  <tr>
    <td>
      Variation name
    </td>
    
    <td>
      150 characters
    </td>
  </tr>
  
  <tr>
    <td>
      String, enum, and URL values
    </td>
    
    <td>
      1,000 characters
    </td>
  </tr>
  
  <tr>
    <td>
      Integer and float values
    </td>
    
    <td>
      60 digits
    </td>
  </tr>
  
  <tr>
    <td>
      Timespan values and constraints
    </td>
    
    <td>
      Up to 9,007,199,254,740,991, the largest exact integer in JavaScript
    </td>
  </tr>
  
  <tr>
    <td>
      JSON values
    </td>
    
    <td>
      16 KB
    </td>
  </tr>
  
  <tr>
    <td>
      JSON Schema
    </td>
    
    <td>
      32 KB, with the schema limits on <a href="https://docs.configdirector.com/getting-started/json-schema-validation#limits">
        JSON Schema validation
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      Tags per config
    </td>
    
    <td>
      20
    </td>
  </tr>
  
  <tr>
    <td>
      Values across a project
    </td>
    
    <td>
      1 MB
    </td>
  </tr>
</tbody>
</table>

### Targeting rules and segments

<table>
<thead>
  <tr>
    <th>
      Limit
    </th>
    
    <th>
      Value
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Values in one percentage rollout
    </td>
    
    <td>
      20
    </td>
  </tr>
  
  <tr>
    <td>
      Segment conditions in one targeting rule
    </td>
    
    <td>
      10
    </td>
  </tr>
  
  <tr>
    <td>
      Trait path in a condition
    </td>
    
    <td>
      500 characters
    </td>
  </tr>
  
  <tr>
    <td>
      Context kind
    </td>
    
    <td>
      1 to 64 lowercase letters, digits, dashes, or underscores
    </td>
  </tr>
  
  <tr>
    <td>
      Segments per project
    </td>
    
    <td>
      200
    </td>
  </tr>
  
  <tr>
    <td>
      Condition groups per segment, and per environment override
    </td>
    
    <td>
      10
    </td>
  </tr>
  
  <tr>
    <td>
      Conditions per condition group
    </td>
    
    <td>
      20
    </td>
  </tr>
  
  <tr>
    <td>
      Segment name
    </td>
    
    <td>
      150 characters
    </td>
  </tr>
</tbody>
</table>

There is no limit on the number of rules in a config's targeting rules, or on the conditions in a rule. [Segments](https://docs.configdirector.com/getting-started/segments#limits) describes the segment limits in context.

### Admin API and MCP server

<table>
<thead>
  <tr>
    <th>
      Limit
    </th>
    
    <th>
      Value
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Admin API requests
    </td>
    
    <td>
      10,000 a month in the free allowance, then per request on Pay as you go
    </td>
  </tr>
  
  <tr>
    <td>
      Request body
    </td>
    
    <td>
      4 MB. A larger body is refused with <code>
        413
      </code>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      MCP tool calls
    </td>
    
    <td>
      60 per minute per organization. Calls over the rate are refused with <code>
        429
      </code>
      
       until the minute passes.
    </td>
  </tr>
  
  <tr>
    <td>
      Schema updates on Free
    </td>
    
    <td>
      20 per hour, see <a href="https://docs.configdirector.com/getting-started/json-schema-validation#hourly-budgets-on-free">
        hourly budgets
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      JSON value validations on Free
    </td>
    
    <td>
      300 per hour, see <a href="https://docs.configdirector.com/getting-started/json-schema-validation#hourly-budgets-on-free">
        hourly budgets
      </a>
    </td>
  </tr>
</tbody>
</table>

## How long things are kept

<table>
<thead>
  <tr>
    <th>
      What
    </th>
    
    <th>
      Kept for
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Evaluation activity charts
    </td>
    
    <td>
      The <a href="https://docs.configdirector.com/monitoring/activity">
        Activity
      </a>
      
       tab shows up to the last 30 days. The configs list's weekly evaluation counts cover the last 7 days.
    </td>
  </tr>
  
  <tr>
    <td>
      Activity data behind lifecycle and alerts
    </td>
    
    <td>
      The daily summaries that size <a href="https://docs.configdirector.com/monitoring/dynamic-detection">
        quiet windows
      </a>
      
       cover 60 days. Individual evaluation records are archived after 60 days and deleted after 120. Connection records are archived after 60 days and deleted after 180.
    </td>
  </tr>
  
  <tr>
    <td>
      Archived configs
    </td>
    
    <td>
      Restorable for 30 days, then purged. See <a href="https://docs.configdirector.com/monitoring/lifecycle#archiving">
        Config Lifecycle
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      Old config keys after a rename
    </td>
    
    <td>
      At least 35 days, and until the old key is no longer used. See <a href="https://docs.configdirector.com/monitoring/dynamic-detection#old-keys">
        Dynamic Detection
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      Alerts
    </td>
    
    <td>
      A resolved alert is removed 30 days after it resolves, a dismissed one 30 days after the dismissal, and an alert you have read but not dismissed leaves your inbox after 90 days. Dismissals themselves expire per alert kind, see <a href="https://docs.configdirector.com/monitoring/alerts">
        Alerts
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      Alert sightings
    </td>
    
    <td>
      The detection history behind an alert's grace period is kept for 30 days.
    </td>
  </tr>
</tbody>
</table>


## Sitemap

See the full [sitemap](https://docs.configdirector.com/sitemap.md) for all pages.
