Starter BYOC
Launch
$499/month
- 15 weighted capacity units
- Streaming table = 2 units · Batch pipeline = 1
- Default mix: 5 streaming + 5 batch
- Up to 5 tables per batch pipeline
Pricing
Choose where PipePilot work runs.
Start with a trial, run supported work on a Private Agent, or request PipePilot-managed capacity where available.
TrialDisplayed allowance
Private AgentCustomer host
Managed capacityWhere available
Simple BYOC platform pricing
Start predictably. Add capacity when you need it.
BYOC infrastructure is paid separately. Runtime credits show usage without changing the monthly platform price.
BYOC add-on · 15 units
Growth
+$250/month
- +15 weighted capacity units
- Default mix: +5 streaming +5 batch
- Reallocate units to batch or streaming
- Same workspace and controls
BYOC add-on · 30 units
Scale
+$350/month
- +30 weighted capacity units
- Default mix: +10 streaming +10 batch
- Reallocate units to batch or streaming
- Same workspace and controls
Custom deployment
Custom
Contact Sales
- Capacity tailored to your workload mix
- Managed compute sized and quoted separately
- Private-network Agent rollout
- Onboarding and support planning
Capacity calculator
Plan a monthly configuration
Growth packs
Scale packs
15 capacity units · 2 per streaming table · 1 per batch pipeline
Estimated monthly total
$499/month
- Platform and capacity
- $499/mo
- Customer-provided compute
- $0 from PipePilot
Streaming allocation5 tables
Batch allocation5 pipelines
BYOC infrastructure is paid directly by the customer. Large data volume does not silently create a per-row PipePilot charge. Configured capacity does not guarantee simultaneous execution or throughput.
Sign upCore capabilities
Free trial
Create a trial workspace to evaluate enabled connections and pipeline workflows within the displayed allowance.
Pricing factors
01Match capacity to the workload.
Pricing depends on execution location, capacity, pipeline modes and provider requirements.
01
Visible trial allowance
02
Customer-paid Private Agent hosts
03
Managed capacity where available
04
Separate provider platform charges
Configuration and runtime evidence stay attached to the workflow.
Next step
02Review your source, destination and runtime.
Share your systems, movement mode, network location and capacity needs. We will map them to a supported option.
01
Batch, CDC and migration reviewed separately
02
Connector roles confirmed
03
Private and managed options explained
04
Prerequisites confirmed before deployment
Configuration and runtime evidence stay attached to the workflow.
Next step
Plan your data workflow.
Share your source, destination and network needs. We will confirm the supported workflow and prerequisites.