Run costs
Every run that touches billable resources reports a cost summary when it finishes. The summary appears on the run’s detail page under Cost.
How records are counted
Graftport charges per record, not per run. The rate depends on whether a record is being loaded for the first time or re-synced.
| Record type | When it applies |
|---|---|
| First load | The record has never been written to the destination. Charged at the tier rate for your plan. |
| Sync | The record was already on the destination and changed since the last load. Charged at the lower sync rate. |
| Skipped | The record was already on the destination and has not changed. No charge. |
The first-load tier rate decreases as your monthly loaded record count rises. Records above your included monthly allowance are charged at the tier 1 rate; above that threshold the per-record cost steps down at volume breakpoints. The exact rates and allowance are set per contract during the closed beta — check your proposal or ask sales.
Reading the cost summary
The cost summary on a run shows:
- First-loaded records — count and projected cost at the tier rate.
- Synced records — count and projected cost at the sync rate.
- Skipped records — count, no cost.
- Errored records — count, no cost (records that failed to load are not charged).
- Projected total — the sum of first-load and sync charges for this run.
“Projected” means the amount will be added to your monthly usage total. The invoice is issued at the end of the billing month and covers all runs across all migrations that fired during that period.
Dry runs and cost
Dry runs that include the extract phase still read from the source platform — that read is not free on Graftport’s side. However, dry runs do not generate billable record loads. Only runs with dry-run off that write records to the destination contribute to your usage total.
Dry-run transform and dry-run load runs do not hit the source and do not write to the destination, so they have no cost impact beyond any existing extracted data already on file.
Estimating cost before a run
Run a transform only + dry-run before any production load. The resulting run’s cost summary shows the projected first-load and sync counts for the real load that would follow. Use this to sanity-check the projected invoice before committing.
On a migration where staging has already loaded most records, the cut-over night projection typically shows a small sync count (records that changed since staging) and near-zero first loads — most of the first-load spend happened during the staging run.