Capacity · Surge capacity
Surge capacity for AI platform programs that have slipped or grown
Surge capacity is Kernavique’s short-notice cover for an AI platform program that has slipped or grown. We scope the gap with you, then propose named engineers on contract through their own companies against it: Foundry and AIP, LLM, MLOps, data or AI infrastructure engineers. It is for partners and consultancies that hold a delivery contract with a date they cannot move and a team that is not big enough to meet it.
Last updated

Surge capacity
What you get
A scoped gap
What has slipped or grown, which skills are short, and what the extra engineers must deliver and by when.
Named engineers against it
Engineers proposed by name with our notes, matched to the work that is behind rather than to a generic role.
An answer on the brief call
We tell you on the call whether we can cover the scope and start date you need.
A defined end
Each term is set to the length of the recovery, with the option to extend or reduce it as the program steadies.
How it runs
- Scope the gapOn the brief call we set what is behind, the skills needed and the start date.
- ProposeNamed engineers against the gap, with our notes.
- StartYou choose, and the engineers start under a written scope and term.
- Step downAs the program recovers, we agree with you when each term ends.
When it fits
- A Foundry or AIP program has slipped and the go-live date is fixed.
- The client has added scope mid-program and your team is already fully committed.
- A key engineer has left a program and the work cannot wait for a permanent hire.
Who it is for
- Palantir partners and implementation consultancies that hold the delivery contract
- Mid-size consultancies with AI platform work and no bench
- Series A to C companies with a platform deadline
Questions buyers ask
- How fast can you cover a program that has slipped?
- Tell us the scope and the start date on the brief call, and we will tell you on that call whether we can cover it. If we cannot, we say so rather than propose engineers who do not fit the gap.
- What do you need from us to scope the gap?
- The program plan, what has slipped or been added, the platform and tools in use, and the date that cannot move. With that we can write a scope to match engineers against.
- Why not just hire permanently?
- If the gap is permanent, you should, and Search can help. But a permanent search runs on its own timeline, and a program that has slipped usually cannot wait for it. Surge capacity carries the work while the search runs.
- What happens when the program is back on track?
- Each term is set in writing at the start. As the program recovers, we agree with you whether to end, extend or reduce it. If an engineer should stay, Contract to permanent covers that.
Terms on this page
- AIP
- Palantir’s Artificial Intelligence Platform, used alongside its Foundry data platform.
- LLM
- Large language model, the kind of model behind chat assistants and many AI products.
- MLOps
- Machine learning operations: deploying, monitoring and maintaining models in production.
Related services
- CapacityPlatform engineersIndividual Foundry, AIP, LLM and MLOps engineers on contract for a defined scope and term, each matched to a written scope before they start.
- CapacityForward deployed teamsTwo to five engineers on contract who join a client program together under a lead, for programs that need a team from the start.
- SearchEngineering searchPermanent commissioning, mission-critical MEP, construction, platform and forward deployed engineers, through a contingent or committed search.