Pilot-first commercial path for
enterprise Spark teams
Start with a guided pilot, prove value on a scoped workload, and then choose a rollout path.
Self-guided path for technical teams that want to evaluate core workflow behavior on their own.
- Single-team workspace
- Core preflight checks
- Manual environment setup
- 20+ preflight safety checks
- Run lifecycle tracking
- Estimated run cost
- Airflow and Dagster providers (preview, source-only)
- Community support (GitHub)
Sales-led pilot for platform teams that need a governed Spark path with clear success criteria.
- Multi-tenant controls
- Pilot environment setup
- BYOC-Lite provisioning
- Preflight and diagnostics suite
- CUR cost reconciliation (Early access)
- Team budget guardrails
- Policy controls (Coming soon)
- Guided rollout plan
- Support channel during pilot
Post-pilot rollout path for organizations with procurement, security, and multi-team operations.
- Everything in Pilot Program
- Production environment expansion
- Security and procurement review
- Support channels and escalation guidance
- Deployment and operations guidance
- Executive rollout planning
Capability labels show current maturity: Available now, In beta, Early access, or Coming soon.
How commercial evaluation works
- 1Discovery call to scope one workload and success metrics
- 2Guided setup and first governed run in your AWS account
- 3Pilot review and rollout recommendation
Common questions
Does SparkPilot have access to my AWS account?
SparkPilot runs inside your AWS account using a cross-account IAM role you provision. Spark job data and storage remain in your AWS environment.
What does BYOC mean?
Bring Your Own Cloud. You provide the EKS cluster and IAM setup. SparkPilot registers your environment, validates prerequisites, and dispatches jobs within your account.
What AWS services does SparkPilot require?
EMR on EKS (virtual cluster), EKS (your cluster), IAM (cross-account role + IRSA bindings), CloudWatch (log retrieval), and optionally Athena + S3 for CUR cost reconciliation (Early access).
How does a pilot start?
Most teams begin with a scoped pilot call, then run one governed workload in their AWS account before deciding rollout scope.
Can we evaluate SparkPilot without changing our current infrastructure?
Yes. BYOC-Lite connects SparkPilot to an existing EKS cluster without replacing your IAM model or S3 setup. The pilot scopes one workload to a test environment before any production changes.
Need a realistic pilot plan?
We start by scoping your pilot, then recommend the right rollout path based on pilot results.