You pay to design your workforce.
Not to run it.
No per-decision meter. No runtime license. Pricing shaped like the engagement — scoped by the processes you staff, never metered by the decisions your workers make.
Scoped like a project. Never metered like a utility.
Every engagement prices the design and delivery of your workforce — scoped by the processes you staff and the systems we integrate, never metered by the decisions your workers make. Ongoing help through Managed Delivery is optional and priced as a service you choose, not a dependency we engineer. Regeneration-in-place is work you commission when you want updates. And if you stop paying us, nothing stops working — it’s your code.
Workforce design & delivery
The core engagement: the design and delivery of your digital workforce, scoped by the processes you staff and the systems we integrate. The scope is agreed before work begins — and it is never metered by the decisions your workers make.
Managed Delivery — optional
Ongoing help, priced as a service you choose, not a dependency we engineer. Keep us on for upgrades and operations, or hand everything to your own engineers — tests and deployment files ship in the box either way.
Regeneration on your schedule
Work you commission when you want updates. If a worker is exported with upgrade-in-place switched on, a regenerated version can later be merged into your edited copy while keeping your team's changes — on your schedule, not a subscription clock.
You won’t find a price table on this page — on purpose. An engagement is scoped to your processes and your systems, so a generic figure wouldn’t be yours. The same policy that governs every number on this site applies here: we scope it honestly in a workforce design conversation rather than publish a number we can’t stand behind.
Whitelabel-ready applications, generated and delivered.
Generated, governed software workers — delivered as owned source code.
Delivered across finance, healthcare, manufacturing, energy, legal, logistics, automotive and more.
Portal and worker counts are computed from our delivery records. A digital worker is a generated, governed software worker delivered as owned source code — not a rebadged bot or script.
Three line items that don’t exist.
Each one is a property of the code you receive — and each one is something your own engineers can verify, on your hardware.
No per-decision meter
Metered platforms bill you every time your worker thinks. There is no Nexgile meter: as your workforce scales, there is no meter scaling with it, and success never raises what you pay us.
Verify it yourselfNo runtime license
Exports are complete Python projects running on your infrastructure — no license keys, no activation gates, no subscription keeping the lights on. Nothing stops working if you stop paying us.
Verify it yourselfNo calls home
The delivered workforce doesn’t phone Nexgile — there is nothing to cut off and no usage to report. Its AI bill of materials, with a signed attestation, lets your engineers check what’s inside on their own hardware.
Verify it yourselfEvery export ships an AI bill of materials listing what's inside, with a signed attestation your engineers can verify offline — without trusting us. Sample export files are available on request via the Trust Center; the verdict is yours to read.
How the cost mechanism works.
When a worker is designed, every decision that follows a fixed business rule becomes a rule step that runs at no AI cost — not discounted, never billed: the model is simply never called.
The AI judgment that remains runs on the model provider you choose, at your rates, and every design shows its estimated cost per run before you export. That spend is between you and your provider — Nexgile adds no meter on top.
We publish the mechanism, not a marketing percentage: you can reason about your own cost before you sign anything.
We charge to design your workforce, not to run it. A vendor with a meter profits when you depend on it; our incentives point at your independence — ongoing help is optional, on your terms.
- Designing the workforce Paid to Nexgile — scoped by the processes you staff and the systems we integrate, agreed before work begins.scoped
- Rule steps No AI tokens — a rule step applies your business rule without ever calling a model.zero
- Live AI judgment Billed by your model provider at your rates — every design shows its estimated cost per run, and Nexgile adds no meter on top.estimated
- Running the workforce Your infrastructure, your cloud — no runtime license, no calls home.yours
- Ongoing help Optional Managed Delivery, priced as a service you choose — on your terms.optional
No figures here, on purpose: engagements are scoped, not metered — and we don’t publish numbers that aren’t yours.
The questions procurement asks first.
What happens if we stop?
Nothing stops working — it’s your code. The workforce is a standard Python project running on your infrastructure; it doesn’t call home, and there is no meter to cut off. Every export ships an AI bill of materials with a signed attestation, so your engineers can check that themselves.
How to check an export yourselfHow is this priced without a meter?
You pay to design your workforce, not to run it. There’s no per-run fee and no runtime license: rule steps never call a model, and the AI judgment that remains runs on your own provider account at your rates — with an estimated cost per run shown for every design before you export.
How the cost mechanism worksWhy are there no price figures on this page?
Because engagements are scoped, not metered — by the processes you staff and the systems we integrate — a generic figure wouldn’t be yours. The same policy that governs every number on this site applies here: when we can’t publish something honestly, we don’t publish it. A scoping conversation produces a figure specific to your scope.
Scope a workforce designDoes what we pay Nexgile change when our volume grows?
No — there is no Nexgile meter, so success never raises what you pay us. The live AI judgment your workers still need is billed by your model provider and does scale with volume — which is why every design shows its estimated cost per run before you export, and why steps that follow fixed rules never call a model at all.
Is Managed Delivery required?
No. Ongoing help through Managed Delivery is optional and priced as a service you choose, not a dependency we engineer. Many clients keep Nexgile on for upgrades; others run everything with their own engineers — tests and deployment files ship in the box either way. Ownership means you choose who maintains it — including us, on your terms.
What exactly do we own?
Everything an export contains: the workflow, its prompts and code, the runtime that executes it, tests, deployment files, a threat model and an AI bill of materials — a complete Python project on your infrastructure and the cloud of your choice, with no license keys and no runtime dependency on Nexgile.
Read the Trust Center
You generate it. You preview it.
You own it. You run it.
A scoping conversation defines the processes you staff and the systems we integrate — and ends with a figure that’s yours, not a meter.