Naver Cloud began onboarding Gyeonggi Province municipal offices into HyperCLOVA X fine-tuning sandboxes this week, giving county chatbot teams dedicated GPU tenants to train on local welfare and permit FAQs without uploading citizen transcripts into commercial model pools. The program sits inside Clova Studio’s government tier, which separates keys, logs, and egress policies from startup workspaces on the same region.
What the sandbox includes
Each municipality receives a capped GPU pool—typically two A100-class cards—plus storage for curated document sets: housing subsidy rules, small-business permit checklists, and disaster SMS templates. Fine-tunes run against HyperCLOVA X base weights hosted in Korean zones; outputs stay in tenant-isolated buckets with automatic deletion timers for raw uploads. Naver Cloud engineers said sandboxes block outbound API calls except to approved translation and moderation services audited last quarter.
Training jobs must declare data classification labels aligned with Gyeonggi’s digital governance handbook. County IT leads pick between low-rank adaptation for fast iterations and fuller fine-tunes when legal counsel signs off on broader corpora. Naver ships evaluation notebooks that score hallucination rates against gold-standard answers compiled by provincial trainers.
Why Gyeonggi moved first
Gyeonggi surrounds Seoul with dozens of cities that field repetitive chat queries about resident registration and childcare vouchers. Last year’s heat-wave hotline overload showed IVR trees could not keep up; several counties piloted generic large-language-model widgets that occasionally cited obsolete COVID rules. Provincial digital officers wanted a unified base model with local adapters per city, rather than ten vendors shipping mismatched bots.
HyperCLOVA’s Korean tokenization and honorific handling matter on civil service tone—English-first models stumbled on formal phrasing in beta tests at Suwon and Seongnam. Naver’s government pricing bundles sandbox hours with support tickets routed to engineers who have cleared security background checks, a requirement public offices insist on after a 2025 data residency review.
Regulator-facing guardrails
Ministry of Science and ICT guidance this summer requires logging prompts that touch personal identifiers and blocking training on uncensored citizen chats scraped from social media. Naver’s sandbox enforces regex filters on uploads and strips attachment types that could carry malware masquerading as PDF permits. County admins see redacted audit trails they can hand to provincial inspectors; raw logs stay with Naver under contract clauses that survived legal review in August.
Offices must publish bot scope statements on their homepages—what the chatbot will not do, such as issue binding legal opinions. Naver templates generate those disclosures in Korean and English for foreign resident pages common in Ansan and Dongducheon.
Deployment path
Early adopters include northern cities testing weekend-only bots for library events and southern counties routing construction permit status queries. Integrators embed sandbox-trained adapters into existing Kakao channel bots and provincial app webviews, using Naver’s API gateway for inference rather than exposing model weights. Latency targets stay under two seconds for 90th percentile prompts on wired kiosks in community centers.
Naver Cloud said sandboxes are not a replacement for back-office workflow systems: bots answer “what documents do I need,” not “approve my rezoning.” Human agents remain on escalation paths with ticket IDs bots attach when confidence scores drop.
Limits and vendor lock-in worries
Smaller towns worry about GPU hour overages when interns upload oversized PDF packets. Naver set hard caps that pause training rather than silently billing; counties must request quota lifts through provincial IT. Open-source advocates on county councils asked about exporting adapters if Naver prices rise; contracts allow download of LoRA weights but not base HyperCLOVA checkpoints, a familiar tension in government cloud deals.
Competing Upstage and NC AI offerings pitched similar sandboxes; Gyeonggi chose Naver for integration with existing Clova Talk telephony trials. Other provinces watch whether evaluation metrics actually reduce misinformation incidents measured in quarterly citizen surveys.
What residents will notice
Changes roll out city by city, not as a province-wide splash screen. Residents chatting about parking violations in Paju may get answers tuned to local ordinance numbers, while Yongin users see different fee tables—even though both ride HyperCLOVA cores. Naver plans a shared moderation dashboard so provincial staff can ban toxic prompts across tenants within minutes.
What success looks like
Digital officers defined success as fewer misrouted hotline calls during Monday mornings, not flashy generative prose. If sandbox hours stay within budget through Chuseok travel season, Gyeonggi will expand templates to tourism and agricultural subsidy bots ahead of spring planting questions. For Naver, the win is proving HyperCLOVA X can be governed like public infrastructure—not a consumer toy—while keeping training data off the open internet.
