From the NVIDIA edition of October 25, 2026
Lenovo customer story: Onetera's 40-day on-premises validation pilot on a ThinkSystem SR675 V3 reports up to 98% cost savings for token-heavy local-government workloads
Lenovo; Onetera · Local government AI infrastructure (on-premises inference economics) · North America
- Publisher
- Lenovo customer success stories
- Original publication
- Undated customer story
- Source retrieved
- 2026-10-26
What happened
Lenovo says Onetera worked with the Lenovo AI Center of Excellence to validate the breakeven and token economics of on-premises infrastructure for its municipal AI services. LLMs were deployed on a Lenovo ThinkSystem SR675 V3 server (NVIDIA processors listed), every pipeline stage stayed inside the infrastructure boundary, and during the 40-day pilot only one of the server's eight GPUs was actively used. Stated outcomes are cost savings of up to 98% for token-heavy workloads (against high cloud API pricing), lower cost making agentic AI more accessible to local governments, and control over where data is stored and flows.
Why it matters
Why now: it is the infrastructure-cost claim behind Onetera's Oct 25 on-premises pitch to cities. Relevant to state and local IT leaders weighing cloud API spend against owned GPU servers, with the caveat that the pilot was run by the vendor, not a government.
Evidence and measured results
Vendor customer-story summary (linked PDF not opened). 'Up to 98%' is a best case with no stated workload mix, comparison price, utilisation assumptions or amortisation period; one GPU of eight was used, so full-server cost allocation is unclear.
Limitations and uncertainty
Undated; vendor-run pilot by a software company, not a city; 'up to' figure; methodology in an unopened PDF; hardware vendor and customer both benefit from the claim.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-26; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Token-heavy agent workloads make cloud API costs unpredictable for local governments that also want data kept in their own environment.
- Stakeholders
- City CIO / IT director
- Finance or budget office
- Procurement
- Program owners using AI services
- Discovery questions
- What are current monthly token volumes and API costs?
- Who would operate and patch on-premises GPU servers?
- What refresh cycle and power costs should be included?
- Value hypothesis
- Interpretation: steady high-volume workloads may cost less on owned hardware than via APIs; the size depends on utilisation and is not established for any city here.
- Potential engagement
- Total-cost-of-ownership comparison for one AI workload, cloud API versus on-premises GPU server.
- Unsupported claims
- 98% savings for a city
- That an eight-GPU server is needed
- That on-premises is cheaper at low or bursty volumes
Pre-sales engineering
Role takeaway
- Fit
- Agencies with steady, high-token workloads and data-residency requirements.
- Architecture and integration
- Open LLMs served on a local multi-GPU server inside the city network, replacing calls to external APIs.
- Prerequisites
- Server-room capacity with power and cooling
- Operations staff or managed service
- Workload volume data
- Constraints
- Pilot used 1 of 8 GPUs, so sizing evidence is thin
- Methodology in unopened PDF
- Vendor-run, not government-run
- Security
- Keep all stages inside the boundary as claimed and add standard server hardening, access control and log retention.
- Proof of value
- Measure cost per completed task over a full month on real volumes
- Load-test to find the GPU count actually needed
Delivery
Role takeaway
- Work
- Install, size and operate a local inference server and migrate one workload from API to local serving.
- Dependencies
- Facilities (power and cooling)
- Hardware vendor support
- Model licence review
- Ownership
- City IT infrastructure team, or a managed service provider under contract.
- Skills and adoption
- IT staff need GPU server operations and model-serving skills.
- Governance checkpoints
- TCO review signed off by finance
- Licence review for open models
- Acceptance criteria
- Proposed: measured cost per completed task below prior API cost over one billing cycle
- Proposed: availability target met with documented failover
- Risks
- Under-utilised capital purchase
- Single-GPU failure
- Staff skill gaps
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Supports buying a multi-GPU server and running open models locally for high-token workloads; 1-of-8 GPU utilisation implies large headroom or overprovisioning.
Governance
Who approves, reviews and stays accountable for outcomes?
Cost comparisons against cloud APIs depend on assumptions public buyers should require in writing, including hardware refresh, staffing and power.
Security and privacy
What data, permissions and controls need testing?
Keeping all pipeline stages inside the infrastructure boundary supports data-sovereignty requirements; the controls themselves are not described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Owning GPU servers requires operations skills many small governments lack.
Procurement
What should contracts, pricing and exit terms secure?
Cities weighing on-premises against API pricing should ask for total cost of ownership, including capital, maintenance, staff and energy, not per-token comparisons alone.
Operating model
Which teams own the service once it runs?
On-premises AI shifts cost from variable API spend to fixed capital and operations, which suits steady high-volume workloads more than sporadic ones.
Publication history
- 2026-10-25NVIDIA · Issue 508 resources
Stable resource ID: lenovo-onetera-on-premises-local-government-ai-cost-pilot