From the State Government edition of November 7, 2026
Swiss canton of Valais puts its in-house sovereign AI platform AVA in front of all cantonal staff, claiming about CHF 2 per active user a month
Etat du Valais, Service cantonal de l'informatique (SCI), Filière IA · State government · Canton of Valais, Switzerland
- Publisher
- Etat du Valais
- Original publication
- 2026-11-05
- Source retrieved
- 2026-11-08
- Event date
- 2026-11-05
What happened
On 5 November 2026 the canton of Valais made AVA, an internally built AI assistant platform, available to all cantonal staff after an April-to-November pilot used by more than 2,000 employees. Data stays on cantonal servers and processing remains in Switzerland; press-conference material reported by ICTjournal describes open models (Apertus, Mistral, Qwen) with RAG, dedicated Swiss GPUs, 50+ tools and agents, and specialized HR, legal and parliament assistants. The canton estimates CHF 2 per daily active user per month and says no individual decision is automated.
Why it matters
A state-level government building its own staff AI platform instead of licensing a commercial copilot is directly comparable to U.S. states weighing enterprise ChatGPT/Copilot/Gemini seats against self-hosted open-model stacks. Transferability is limited: Swiss data-sovereignty law, canton scale and in-house AI staff differ from most U.S. states.
Evidence and measured results
Official vs.ch release (05.11.2026) for scope, data residency, 2,000+ pilot users and human verification; ICTjournal (06.11.2026) for model, RAG, GPU and cost details from the presentation; RTS (05.11, modified 06.11) for cost definition and quotes.
Limitations and uncertainty
All performance and cost figures are the canton's own; no accuracy, quality, or time-saved results. The cost comparison is inconsistent across reports (RTS: at least CHF 20 less; ICTjournal: at least twenty times cheaper) and the basis is not shown. Cost likely excludes staff development effort.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agency staff need generative AI on protected data that cannot go to public commercial services, and seat-based or per-token licensing looks expensive at enterprise scale.
- Stakeholders
- State CIO / central IT
- Finance department
- Data protection officer
- Agency HR and legal teams
- Municipal partners
- Discovery questions
- Which data classes are barred from commercial AI services today?
- What is current annual spend or quote for enterprise copilot seats?
- Does central IT have staff to run models and GPUs?
- Would municipalities share a state-hosted platform?
- Value hypothesis
- For protected-data workloads, a self-hosted open-model platform may lower marginal cost and data-residency risk compared with commercial seats, if quality is adequate and staffing is funded.
- Potential engagement
- Four-to-six-week build-versus-buy assessment: data-classification mapping, workload sampling, total cost of ownership for self-hosted versus commercial, and a pilot quality benchmark.
- Unsupported claims
- Guaranteed 20x cost savings
- Quality parity with commercial frontier models
- Measured productivity gains in Valais
- Easy replication by states without in-house AI staff
Pre-sales engineering
Role takeaway
- Fit
- Reference architecture for sovereign or on-prem staff AI: open-weight LLMs, RAG over internal documents, dedicated GPUs, modular specialized assistants and agents.
- Architecture and integration
- Model serving on dedicated GPU nodes; retrieval index over cantonal document stores on state servers; assistant/agent layer exposing 50+ tools; future citizen-facing chatbot on the same base.
- Prerequisites
- Data classification and retention rules
- GPU capacity or sovereign hosting
- Curated document repositories for RAG
- Identity and access integration
- Constraints
- Swiss data-residency context may not map to U.S. state law
- Open-model quality may lag commercial models on some tasks
- Open-source architecture release not yet verified
- Single-canton scale; canton itself says sustainability needs a wider ecosystem
- Security
- Keeps protected data on state infrastructure; requires access controls on retrieval indexes, logging, and model supply-chain review for open weights. No published security assessment.
- Proof of value
- Benchmark drafting, summarization and translation quality against a commercial model on agency samples
- Reconstruct cost per daily active user including staff and hardware amortization
- Test retrieval permission enforcement across departments
Delivery
Role takeaway
- Work
- Operate a shared staff AI platform: onboarding, training, assistant catalog, model updates and expansion to municipalities.
- Dependencies
- In-house AI engineering team
- GPU hosting
- Official usage directives
- Training content (guides, webinars, seminars)
- Ownership
- Cantonal IT service (SCI) AI unit; in a U.S. state, the central IT agency with agency data owners.
- Skills and adoption
- Guides, introductory webinars and business-oriented practical seminars; human verification of every answer taught as a norm.
- Governance checkpoints
- Data-classification sign-off per assistant
- Human-verification rule in directives
- Review before any citizen-facing release
- Municipal onboarding agreement
- Acceptance criteria
- Proposed: share of sampled outputs rated accurate by reviewers above an agreed threshold
- Proposed: documented cost per daily active user including staff
- Proposed: zero protected-data egress incidents in first quarter
- Risks
- Quality gap versus commercial tools drives shadow AI
- Hidden staffing costs
- Single-team dependency
- Agentic features outpacing governance
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?
Self-hosted open-weight LLMs with retrieval over internal document bases, dedicated GPU inference in Switzerland, modular specialized assistants and agents, and a platform meant to back future citizen-facing services (a vehicle-service chatbot is planned). Open-source publication of the architecture is promised but not yet verified.
Governance
Who approves, reviews and stays accountable for outcomes?
Official directives frame use; no automated individual decisions and mandatory human verification of every answer. Canton intends to extend to communes, which raises shared-service governance questions.
Security and privacy
What data, permissions and controls need testing?
Motivated by protected administrative data that cannot go to public commercial services; data stays on state servers under cantonal control. No published security assessment.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Positioned as assistant, not job replacement; training program accompanies rollout. Translation support is relevant to a bilingual canton.
Procurement
What should contracts, pricing and exit terms secure?
Avoids per-seat and per-token licensing but shifts spend to GPUs and staff; a U.S. state would still procure hardware or sovereign hosting.
Operating model
Which teams own the service once it runs?
Creates a central AI product function serving all departments and potentially municipalities as a shared service.
Publication history
- 2026-11-07State Government · Issue 613 resources
Stable resource ID: valais-ava-sovereign-ai-platform-all-cantonal-staff-20261105