Pilot Start Guide

How to launch a SparkPilot pilot without confusion

SparkPilot starts with a guided pilot led by our team. Begin with pilot kickoff, then move into authenticated onboarding for setup and run operations.

Request pilot Existing customer sign in

Authenticated setup, runs, costs, and access management stay in the app. This page shows how to start a pilot.

Pick your starting point

Choose the path that matches your role so buyer and operator workflows stay separate.

New evaluator

I want a realistic pilot plan and a technical walkthrough for my team.

Request pilot

Existing customer user

I already have workspace access and need to continue onboarding or run operations.

Existing customer sign in

Existing customer admin

I own first-time setup and need access to onboarding and access controls.

Existing customer admin: Sign in to manage access

Role-based tracks

Pilot owners and platform admins have different responsibilities during setup and evaluation.

Pilot owner

I am evaluating SparkPilot as a buyer

Start with a pilot kickoff call to define scope and success criteria.
Confirm one workload family and one owner from platform engineering.
Use pilot checkpoints to evaluate operational fit and commercial fit.
Pilots are guided so teams can evaluate quickly with clear success criteria.

Platform owner

I am the platform admin running setup

Complete authenticated onboarding once, then onboard users with role mapping.
Validate OIDC trust, execution role bindings, namespace rules, and budget limits.
Run the first governed job and share pilot outputs with stakeholders.
After pilot sign-off, expand environments and user access in phases.

Recommended pilot sequence

Follow these steps in order to keep pilot execution clean and measurable.

Step 1

Request pilot kickoff

Share your workload profile and goals so we can scope a focused pilot with clear success criteria.

Request pilot

Step 2

Confirm architecture and owner roles

Align environment ownership, identity model, and timeline before setup starts.

Request pilot

Step 3

Connect AWS and run onboarding

Platform admins complete authenticated onboarding to validate IAM, OIDC, namespace, and dispatch prerequisites.

Existing customer: Sign in for onboarding

Step 4

Submit first pilot run

Run one governed workload, review diagnostics and cost visibility, then decide production rollout next steps.

Existing customer: Sign in to view runs

Command line quickstart (after sign-in)

Use these commands after sign-in for operator workflows and CI automation.

CLI

Submit and operate runs from terminal

sparkpilot env-list
sparkpilot run-submit
sparkpilot run-list
sparkpilot run-logs

Use the same authenticated workspace context as the dashboard and API.