Pilot
One use case end to end, on your data, in your infrastructure, in 8 weeks
The pilot installs graal on your premises, takes one use case all the way to results and trains your teams. In week eight, you decide on evidence.
Milestones
Eight weeks, week by week
Week 1
Scoping
The use case, the success criteria, the data and the access rights.
Week 2
Installation
graal installed on your cluster, with your platform team.
Week 3
Connection
SSO wired to your directory, first data sources connected.
Week 4
Pipelines
The use case data cleaned and transformed, the code exported.
Week 5
Orchestration
Jobs and workflows scheduled, retries and alerts in place.
Week 6
Model
Training runs tracked and compared, then the chosen model registered.
Week 7
Go-live
The model served or the results published; an AI agent connected under your rules.
Week 8
Review and decision
Results measured against the criteria, deployment plan and estimate.
Deliverables
What you get
- graal installed and documented in your infrastructure
- The use case running end to end, on your data
- The pipeline and job code, exported
- Teams trained on the platform
- A review report, backed by measurements
- A deployment plan and its estimate
On your side
What you provide
A cluster
Kubernetes or OpenShift, with S3 storage and a PostgreSQL database.
Data
The sources for the use case and the necessary access rights.
Two leads
A business lead and a technical lead, a few hours a week.
A sponsor
The person who sets the criteria in week 1 and decides in week 8.
Success criteria
Set in week 1, measured in week 8
Examples, to be adapted to your use case during scoping.
- The use case runs end to end, with no manual intervention
- Results reach the quality level agreed with the business
- The platform passes your security team’s review
- Your teams create and schedule a workload on their own
- The exported code runs outside graal
- Running costs are known, project by project
What next
Three possible outcomes
01
Deploy
The annual license takes over, and more use cases follow.
02
Extend
A second use case to confirm, before deciding.
03
Stop
You keep the exported code and your data, in open formats.
FAQ
About the pilot
Which use cases suit a pilot?
One that matters to the business, with accessible data and a measurable outcome: forecasting, maintenance, document assistant, fraud, taking a datalab into production.
How is the pilot invoiced?
At a fixed price, license included for its duration. It is sized to stay below the procedure exemption threshold for public buyers.
Do we need a cluster from week one?
It must be ready by week 2. If it still has to be built, we prepare it with your platform team during scoping.
Let’s prepare your pilot
One scoping conversation is enough to choose the use case and set the success criteria.