Rows processed
The records your sync moves.
Buy credits for shared runs or dedicated capacity.
No monthly subscription required. Consumption visible by job.
Shared runs account for rows, compute time, and data transferred. Failed shared runs are not charged standard run credits. Dedicated leases are metered separately, including ready and warm idle time.
The records your sync moves.
The execution time used by shared jobs. Dedicated compute uses its profile's hourly lease rate instead.
The volume of data moved.
Buy credits for your organization without a monthly subscription. Check your available balance before running work.
Usage is tracked by run. Successful shared runs use standard credits; a dedicated lease can accrue cost even if its run fails.
Inspect credit usage in job history and compare consumption across a selected date range.
Credit rates and packages are being finalized during beta. Contact us to discuss your workload and the terms available to your team.
Dedicated compute is in an operator-enabled rollout. Eligible teams see the profile rate and maximum reservation before a lease starts.
Talk about your workloadNo. Buy credits and use them as your jobs run. Credit packages and purchase terms are confirmed during beta.
Pre-run credit estimates are planned. Today, use run history to review actual credit consumption. Eligible dedicated profiles show their hourly rate and maximum lease reservation before execution.
The Credits page shows your balance and consumption. Job run history shows credits used per run, and usage reports let you select a date range.
No. Kusi is in beta. Credit rates, packages, and terms will be confirmed before purchase; this page does not quote a final rate.
Eligible organizations can use an operator-enabled dedicated profile. Kusi reserves the maximum lease cost, meters ready and warm idle time, and releases unused credits when the lease settles.