Is AI in a municipality compatible with the Swiss LPD?
Yes, provided the right architecture is chosen. The nLPD (in force since September 2023) requires, among other things, data minimisation, traceability of processing, and no transfers to countries without adequate protection. Kleap uses open-source models hosted in Europe (Hetzner, EU), without sending data to American APIs, and with complete audit logs. This architecture was designed to meet these requirements.
Where should a small municipality with limited IT resources start?
The best starting point is a single use case with high volume and low risk, for example a citizen FAQ assistant that answers questions about opening hours, forms, and routine procedures. The deployment does not require internal IT skills: Kleap or its partners handle the configuration. The cost is predictable and the pilot can be validated in 6 to 8 weeks.
Will AI replace municipal staff?
No. AI handles repetitive, low-value tasks: sorting mail, drafting standard letters, answering frequently asked questions. Staff members get back time for complex situations, citizen advisory work, and decisions that require human judgement. In pilot municipalities, staff describe AI as a tool that 'does the paperwork' so they can do their real job.
Does citizen data leave Switzerland or the EU?
No. Kleap's infrastructure is hosted by Hetzner, whose data centres are in Germany and Finland (European Union). The AI models used are open source and run on this infrastructure without sending data to third-party providers (OpenAI, Google, Microsoft). No citizen data passes through American servers.
What is the difference between Kleap and a tool like Microsoft Copilot?
Microsoft Copilot is a general-purpose tool designed for private enterprises. It processes data on Microsoft servers (primarily in the USA), with compliance guarantees that require complex additional configurations and specific licences. Kleap is architected from the outset for public services: EU hosting, auditable models, mandatory human validation, and configuration based on your local regulations and procedures.
How should resistance to change among staff be managed?
Experience from successful deployments shows that staff buy-in requires three conditions: being involved in the choice of use cases (they know better than anyone which tasks are burdensome), receiving practical training based on examples from their own municipality (not a generic demonstration), and quickly seeing that AI does not threaten their position but reduces pressure. Kleap systematically includes adoption workshops in its support programme.
Can a bilingual municipality use Kleap?
Yes. Kleap supports French, German, Italian, and Romansh. Citizen assistants can be configured to respond in the language chosen by the user. Municipalities in bilingual cantons (Fribourg, Berne, Valais) and trilingual cantons (Graubünden) are natural use cases for these features.
Is a significant IT budget needed to get started?
No. Kleap offers a gradual start on a limited scope, with predictable costs from the outset. The first pilot (one use case, 6 to 8 weeks) is sized for standard municipal budgets. Expansion happens at the pace of results and available resources.
How does Kleap ensure the reliability of AI responses?
Kleap applies two principles: first, the AI is trained on your own official documents (regulations, directives, internal FAQs), not on generic data that might be incorrect or outdated. Second, any sensitive response or action goes through human validation before being sent to the citizen or executed. AI errors are systematically logged for continuous improvement.
Can Kleap integrate with our existing municipal management software?
In most cases, yes. Kleap has connectors for the main solutions used in French-speaking Switzerland (document management systems, municipal ERPs, messaging). Specific integrations are assessed during the diagnostic phase. If your software exposes an API or standard exports, integration is generally achievable.