Pricing

Transparent pricing. No surprises.

Licensed per deployment — not per connector, row, or data volume. Flat fee regardless of how much data moves through your pipelines.

Plans

Three tiers. One flat fee per deployment.

Every tier includes 400+ connectors, schema drift detection, connection health monitoring, and a built-in analytics database. No per-row billing. No connector fees.

Community

Free

5 pipelines · 2 concurrent · 3 users

Startup

€299/mo

50 pipelines · 5 concurrent · 10 users · AI

Business

€999/mo

Unlimited pipelines · 20 concurrent · SSO

FeatureCommunityStartupBusiness
PriceFree€299 / mo€999 / mo
Pipelines550Unlimited
Concurrent Executions2520
Users310Unlimited
Built-in Connectors400+400+400+
Built-in Analytics Database
Schema Drift Detection
Connection Health Monitoring
Data Quality Checks
Pipeline Versioning & Rollback
AI Schema Mapping
AI Error Diagnosis
AI Transformation Generation
AI Support Chat
RBAC (Admin / Editor / Viewer)
SSO (OIDC)
API Keys (Scoped)
Support ChannelCommunity (GitHub)EmailPriority email

Enterprise tier (uncapped concurrency, audit logs, custom connectors, dedicated SLA) coming in v2.0. Contact us if you need enterprise features now.

Self-hosted — your data never leaves your infrastructure

All tiers run entirely within your own environment. RelayData does not transmit pipeline data, credentials, or usage telemetry to RelayData servers. See Security & Trust for the full data sovereignty architecture.

Licensing

How licensing works

Each paid tier is activated by a deployment license key — a signed JWT that encodes your tier, seat limit, concurrency cap, and expiry date. The key is validated locally on every application start and periodically at runtime. No network request is made to RelayData servers during validation.

Offline validation.

The license key is verified with a public key baked into the binary. Your instance does not phone home to check validity. Deployments in air-gapped or VPC-isolated environments work without exception.

One key per deployment.

A license covers a single running instance (or a Kubernetes deployment scaled across replicas). If you need a second independent environment — for example, a production and a staging instance — contact us for multi-deployment pricing.

No consumption billing.

Your license cost does not change based on the number of rows synced, connectors configured, or how frequently pipelines run. Run 50 pipelines every minute or one pipeline per day — the fee is the same.

License delivery.

On purchase or renewal, a license key is generated automatically via Stripe webhook integration and emailed to the billing contact. Keys can be rotated from the admin settings panel without redeployment.

Concurrency

What counts as concurrent?

Concurrency is measured as the number of connector processes actively transferring data at the same instant. A pipeline that is scheduled but waiting in the queue, or has finished running, does not occupy a concurrency slot.

In practice, most customers — even those with 50 pipelines — use 3 to 4 concurrent slots at peak. Pipelines tend to stagger naturally: a nightly warehouse sync, a few hourly CDC streams, and on-demand API pulls rarely all overlap at the same second.

What occupies a slot: A connector process that is reading from a source or writing to a destination right now.
What does not occupy a slot: Pipelines waiting in the scheduler queue, pipelines in a paused or disabled state, completed runs, or DAG steps blocked waiting for an upstream dependency.
When the limit is reached: New pipeline runs are queued and executed as slots free up. Nothing fails silently — the run status shows "queued" and the concurrency dashboard shows current utilization.

The concurrency dashboard (Settings > Concurrency) shows real-time slot usage so you can verify your workload fits comfortably within your tier before upgrading.

Community

Community tier

The Community tier is free, permanently, with no registration or license key required. Spin up an instance, connect your data sources, and build pipelines immediately.

Included

Full pipeline engine — batch, incremental, CDC, fan-out, DAG dependencies

All 20+ built-in connectors and Airbyte CDK integration

Schema drift detection and connection health monitoring

Data quality checks, lineage graph, and data catalog

All trigger types — cron, webhook, API poll, file arrival, row trigger

Multi-user authentication with RBAC

Docker Compose and Kubernetes Helm chart deployment

Open-source core under the Business Source License 1.1

Not included

AI features (schema mapping, error diagnosis, support chat)

SSO / SAML / OIDC

More than 5 pipelines or 2 concurrent executions

Commercial support

No registration required

Community deployments need no account, no email address, and no license key. Download the image, configure your environment, and run.

FAQ

Frequently asked questions

What happens if I exceed my pipeline or concurrency limit?

Limits are enforced gracefully — nothing breaks and no data is lost. If you have reached your pipeline limit, the UI will prevent creating additional pipelines and display an upgrade prompt. If all concurrency slots are occupied, new runs are queued and execute as slots free up. Queued runs appear with a "queued" status in the run history and on the pipeline detail page. You can monitor queue depth in real time from the concurrency dashboard.

Can I try paid features before purchasing?

Yes. RelayData runs a design partner program for teams evaluating the Startup or Business tier. Design partners get full access to paid features in exchange for product feedback and participation in early feature testing. If you are evaluating RelayData for a production deployment, contact us to discuss design partner access.

Is there an annual discount?

Yes. Annual pricing is available at a discount compared to month-to-month billing. Exact figures are provided on request — reach out with your deployment requirements and we will send a quote.

What is the cancellation policy?

You can cancel at any time. When a paid license expires or is cancelled, the deployment automatically falls back to the Community tier at the next license validation cycle. Features above the Community tier limits become read-only — existing pipelines above the 5-pipeline limit are preserved and visible but will not run until you either upgrade or remove pipelines to stay within the limit. No data is ever deleted as a result of a plan change.

Ready to try RelayData?

Start with the free Community tier. No credit card, no registration, no license key required.