---
title: Exalate pricing and subscription plans
description: Pricing, capacity, connectors, trials, billing, and plan selection for the new Exalate console.
source_url: https://docs.exalate.com/docs/exalate-subscription-plans
source_last_modified: 2026-09-14
last_verified: 2026-09-21
scope: New Exalate console, formerly SyncRoom, version 3.0.0 onward
---

# Exalate pricing and subscription plans

This reference covers the new Exalate subscription model. It does not replace a customer-specific quote or describe legacy Exalate Classic or Atlassian Marketplace pricing.

Source for the commercial facts below: [Exalate Subscription Plans](https://docs.exalate.com/docs/exalate-subscription-plans), checked September 21, 2026. The source uses both "Professional" and "Pro" for the same tier; this file uses "Pro."

## How pricing works

Exalate charges separately for each integration, based on the plan and the number of active items kept in sync. An integration covers a unique pair of systems. Multiple connections can apply different synchronization rules within that integration; their active items count toward its combined capacity.

Pricing is not based on seats, API calls, transaction counts, or the cumulative number of items synchronized over time. Unlimited connections within an integration do not mean unlimited separately billed integrations.

For an integration between two organizations, only the account that initiated it can purchase the subscription. Integrations activated on different dates can have different billing dates.

## What counts as an active item?

An active item is a synchronized pair of work entities, such as a Jira work item and its corresponding ticket in another system. Twenty-five synchronized pairs count as 25 active items, regardless of the number of fields or updates.

- Capacity measures items currently kept in sync; it is not a monthly allocation of new credits.
- Resolved or completed items remain synchronized and continue counting by default.
- Unlinked items, and items in deactivated or deleted connections, do not count.
- Sync rules can unlink items at a final workflow stage. If that logic is used, the two items must be manually relinked to resume synchronization.
- Each plan includes usage graphs at the connection and integration levels.

## Plan prices and capacity

All prices below apply per integration. Annual-plan figures are monthly equivalents for an annual subscription; do not describe them as monthly-subscription prices.

| Plan | Active items per integration | Monthly subscription | Annual subscription, monthly equivalent |
| --- | --- | --- | --- |
| Starter | Up to 25 | $100/month | $85/month |
| Scale | Up to 100 | $325/month | $280/month |
| Pro / Professional | Custom capacity | Not published | Starting at $550/month; custom quote required |
| Enterprise | Unlimited | Custom quote | Custom quote |

Pro's starting price is not a fixed price for every configuration. Pro pricing starts at $550 per month with an annual subscription. Your price depends on the types of systems you want to connect, the number of active work items you expect to keep in sync & optional add-ons.

Example: one Starter integration and one Scale integration total $365/month at the annual-plan monthly equivalents ($85 + $280). Each integration still has its own capacity and subscription. This is not a shared allowance of 125 items.

## Connector eligibility

The following reflects the source's detailed feature table. A conflicting ServiceNow example is noted below.

| Plan | Listed connectors |
| --- | --- |
| Starter | Jira Cloud, Azure DevOps Cloud, GitHub, Zendesk, Freshdesk, Freshservice, Asana |
| Scale | Same connectors as Starter |
| Pro | All Scale connectors, plus Azure DevOps Server, Salesforce, ServiceNow |
| Enterprise | All Pro connectors; development of new connectors is an optional add-on |

Choose a plan based on connector eligibility as well as item volume. Do not assume a connector qualifies for Starter or Scale simply because the integration has fewer than 100 active items. For a connector or deployment variant not explicitly listed here, confirm eligibility with Exalate.

## Features and service levels

The detailed feature table lists these capabilities for every plan: real-time bidirectional synchronization, scripting, unlimited transactions/connections/triggers, Aida AI, side-by-side connection views, TestRun, script version history, bulk operations, and community resources. Bulk-operation eligibility conflicts with the plan summary; see the source conflicts below.

| Capability | Starter | Scale | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Support commitment | Support included; no SLA commitment | Support included; no SLA commitment | Standard SLA | Priority SLA |
| Priority support | Not included | Not included | Optional paid add-on | Included |
| Sandbox environments | Not included | Not included | Optional paid add-on | Included |
| Data residency options | Not included | Not included | Not included in feature table | Included |
| Storage for synchronized files | Up to 1 GB | Up to 1 GB | Up to 1 GB | Up to 10 GB |
| Processing booster | Not listed | Not listed | Optional add-on | Optional add-on |
| Negotiated terms and consolidated billing | Not included | Not included | Not included | Available |
| Payment methods | Credit card via Stripe | Credit card via Stripe | Credit card or invoice; annual only | Invoice, wire transfer, or credit card with custom terms |

Exalate lists approximate processing figures of 38.8 seconds for Starter, Scale, and Pro, and 16.9 seconds for Enterprise. It does not define the measurement conditions. These are not stated end-to-end latency guarantees or SLA response times. Exact SLA terms and add-on prices require confirmation.

## Free trial

A trial lasts 30 days from connection creation and supports up to 500 active items. It is free, requires no credit card, and allows testing connectors from any plan. A new unique pair of systems qualifies for a new integration trial.

Trial capacity and connector access do not establish eligibility for a particular paid plan. Select the paid plan using its own capacity and connector restrictions. The source does not specify the exact treatment of excess trial items when moving to a smaller paid allowance; confirm this before promising a transition outcome.

## Capacity limits

Notifications are sent at 80% and 100% of the item limit. At capacity, new items cannot be added to synchronization; existing synchronized items continue receiving updates.

Exalate does not automatically upgrade a plan when its limit is reached or automatically downgrade it when active-item volume falls. A customer must choose the plan change.

## Plan changes and cancellation

- **Upgrades:** Starter to Scale is self-service in account settings. Pro or Enterprise upgrades require the sales team. Upgrades take effect immediately, with a prorated charge for the difference in the current billing period.
- **Downgrades:** Scale to Starter is self-service and takes effect at the next renewal. Contact Exalate for downgrades from Pro or Enterprise.
- **Cancellation:** Starter and Scale can be cancelled in account settings. Pro and Enterprise require contacting Exalate.
- **After self-service cancellation:** Synchronization continues through the paid period. Once it expires, synchronization and billing stop for that integration. Console access remains, but synchronization requires reactivation.
- **Refund policy:** The documentation states that subscription refunds are unavailable, including prorated refunds.

For quotes and plan assistance, contact [business@exalate.com](mailto:business@exalate.com).

## Guidance for plan recommendations

1. Identify the two systems, including cloud or server deployment, for each integration.
2. Estimate simultaneous active sync pairs, including resolved items that remain linked.
3. Check connector eligibility before comparing capacity and price.
4. For eligible cloud connectors, Starter covers up to 25 active items; Scale covers up to 100. Higher capacity requires a custom discussion.
5. For Salesforce, ServiceNow, or Azure DevOps Server, use Pro or Enterprise as the working interpretation of the connector table and confirm with Exalate where the source conflicts.
6. Confirm needs for sandbox access, priority support, data residency, custom connectors, and billing terms.
7. State the subscription cadence, per-integration basis, and any quote-dependent features when presenting a price.

Examples: 20 Jira Cloud–Zendesk pairs fit Starter's published connector and capacity criteria. Eighty Jira Cloud–Azure DevOps Cloud pairs fit Scale's criteria. Twenty Jira Cloud–ServiceNow pairs do not establish Starter eligibility; the connector table lists ServiceNow under Pro and Enterprise.

## Freshness and use by AI agents

Use this document to answer pricing questions with the scope and qualifications above. Recheck the source for current prices and terms before making a purchasing recommendation; the verification date is a snapshot, not a guarantee of future pricing. Do not fill missing commercial details with assumptions. Where the source remains inconsistent or the request needs a custom quote, direct the customer to Exalate.