Skip to content
§PRProposed plan structure — not final pricing

Usage that tracks your business, not your seat count.

Currency figures are not shown because they have not been set. What is settled is the model: what is free, what is metered, what triggers an upgrade and what belongs to Enterprise. Publishing a number we would have to retract would be worse than being straight about this.

§PR.1Plans

Proposed plan structure — not final pricing

  • Developer

    Free

    permanently, at small scale

    Build and evaluate

    Gated on 3 production connections

  • Most integrations

    Growth

    Indicative

    monthly · figure not yet set

    First production integrations

    Gated on 1M data operations / month

  • Business

    Indicative

    monthly · figure not yet set

    Multiple teams, real volume

    Gated on 90-day retention

  • Enterprise

    Contact

    scoped to the deployment

    Governance and scale

    Gated on SSO, residency, custom limits

§PR.2Compare

Compare plans

Every limit, in one table.

Indicative

monthly · figure not yet set

Usage

Active connections
10
Data operations / month
1,000,000
API requests / month
2,000,000
Flow executions
50,000

Workspace

Environments
+ 1 extra
Team members
8
Roles
All five roles

Operate

Log and run retention
30 days
Monitoring and alerts
Alert rules
Audit log
30 days

Platform

Custom API connector
Included
Sandbox environment
Unmetered
Dedicated infrastructure / residency
—

Support

Support
Email
§PR.3Metering

What is metered

Five dimensions, all of which track your own volume.

Active connections
Connections enabled in production during the billing period. Sandbox connections are free, so testing is never billed.
Data operations
One record processed through one flow run. This is the primary cost driver — it is what the engine actually spends.
API requests
Requests served by your generated read endpoints.
Flow executions
The number of runs, which captures high-frequency, low-volume schedules.
Retention
Days of run records and logs kept — storage, and a genuine value ladder for whoever operates the integration.
Usage · current periodSample data
Data operations612,400 / 1,000,000 ops
API requests1,240,882 / 2,000,000 req
Active connections7 / 10 conn
Flow executions41,020 / 50,000 runs

Projected to exceed flow executions on day 27 · usage.limit_approaching sent

§PR.4Limits

Going over

Nothing stops silently.

Soft limits with a documented grace band of 110%, plus an in-app and webhook warning. Beyond the band, read APIs throttle first with a 429 and a Retry-After; flows are paused only after two notifications. Stopping an integration without warning would be the worst possible failure, so the system is designed not to.

§PR.5Questions

Pricing questions

Answered plainly.

§PR.6Enterprise

Enterprise is for things that genuinely need a contract.

SSO and SCIM, dedicated infrastructure or data residency, custom retention, security-review support, a named contact and custom limits. Role-based access control and monitoring are not hidden behind it.

Talk to us