Predictable pricing, for every stage.

Begin your adventure with Starter, accelerate with Growth, and craft the perfect solution with our Custom plan.

Trusted by growing companies worldwide

Compare our plans
Starter
$149/month
$229/month
$349/month
Get started
Unlimited users
Unified data Lakehouse
100 data connectors (sources, destinations, visualizations)
Schedule, event, and manual triggers
Data explorer (SQL)
Data transformations (SQL / Python)
Nekt SDK
Platform API
Data access API
Nekt AI
MCP Server
Alerts
Tags
Application-level user permissions
Growth
$499/month
$699/month
$999/month
Get started
Unlimited users
Unified data Lakehouse
100 data connectors (sources, destinations, visualizations)
Schedule, event, and manual triggers
Data explorer (SQL)
Data transformations (SQL / Python)
Nekt SDK
Platform API
Data access API
Nekt AI
MCP Server
Alerts
Tags
Application-level user permissions
Data-level permissions
Groups
Log-based change data capture (CDC)
Unstructured data volumes
Data lineage
Data expectations
Custom
Custom
Talk with us
Unlimited users
Unified data Lakehouse
100 data connectors (sources, destinations, visualizations)
Schedule, event, and manual triggers
Data explorer (SQL)
Data transformations (SQL / Python)
Nekt SDK
Platform API
Data access API
Nekt AI
MCP Server
Alerts
Tags
Application-level user permissions
Data-level permissions
Groups
Log-based change data capture (CDC)
Unstructured data volumes
Data lineage
Data expectations
SSO
Dedicated Slack channel
Custom SLAs
Custom security questionnaires
Designated support manager
Users
Unlimited
Unlimited
Unlimited
Unified data Lakehouse
100 data connectors (sources, destinations, visualizations)
Schedule, event, and manual triggers
Data explorer (SQL)
Data transformations (SQL / Python)
Nekt SDK
Platform API
Data access API
Nekt AI
MCP Server
Alerts
Tags
Application-level user permissions
Data-level permissions
Groups
Log-based change data capture (CDC)
Unstructured data volumes
Data lineage
Data expectations
SSO
Dedicated Slack channel
Custom SLAs
Custom security questionnaires
Designated support manager

Pay per run.
Scale without surprises.

Each credit represents a single run of a pipeline. When you execute a source, transformation, or destination, it consumes 1 credit—simple to understand, easy to forecast.
Forecast usage with clear triggers (scheduled, event-based, or manual), and rest easy knowing failed runs don’t consume credits. It’s a predictable, transparent way to align costs with outcomes.

Plan runs, predict credits

Set your expected runs across sources, transformations, and destinations, and get a monthly credit estimate.

Sources

Connect your product, marketing, sales, and customer tools to automatically bring data into one place.

How many sources do you want to connect?

How many times will they run each week?

Weekly = 1 time, daily = 7 times, hourly ≈ 168. For a custom pace, estimate total runs per source per week (e.g., every 12 hours ≈ 14). If different sources have different schedules, use an average.

Transformations

Unify, enrich, and analyze your data using SQL, Spark, or AI to create actionable pipelines.

How many transformations do you plan to create?

How many times will they run each week?

Weekly = 1 time, daily = 7 times, hourly ≈ 168. For a custom pace, estimate total runs per transformation per week (e.g., every 12 hours ≈ 14). If different transformations have different schedules, use an average.

Destinations

Send your data where it needs to go — CRMs, ad platforms, or internal systems — to keep operations in sync.

How many destinations do you want to connect?

How many times will they run each week?

Weekly = 1 time, daily = 7 times, hourly ≈ 168. For a custom pace, estimate total runs per destination per week (e.g., every 12 hours ≈ 14). If different destinations have different schedules, use an average.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Based on your inputs, here’s how many credits you’ll likely use each month
0
Edit estimate
Estimates can vary. Actual credits may change with run frequency adjustments, additional pipelines, or one‑off reruns (e.g., backfills, data fixes). Use this as a planning guide; monitor usage in Runs for precise tracking.