One foundation for the digital systems of a city or a country.
KINGAI combines One ID, a situational intelligence core and the ONE operations foundation with security defence, data platforms, AI staff and custom systems. Every engagement starts with the use case, the data boundary and the acceptance test, then builds in phases.
Start with the governing use case
Eight use cases share one platform layer. Each can stand alone, or sit under a framework agreement and grow by module.
Active security defence
Detection, response and audit for government networks, mail systems and critical infrastructure.
- Mail and DNS defence in depth
- Intrusion detection and automated blocking
- Baseline audit and monthly re-verification
Intelligence & situational awareness
Public-source information organised into entities, relationships, events and evidence for authorised teams.
- Multi-source public information intake
- Entity, relationship and event graphs
- An evidence link behind every item
Smart city systems
One intelligent operations centre, one city platform layer and a set of applications that can launch in phases.
- An intelligent operations centre
- A city platform layer and interface standards
- Applications launched in phases
Hazard early warning
Multi-source hazard detection, graded notification and agency APIs, with a free public layer kept in place.
- Four hazard classes under multi-source watch
- Graded notification and agency APIs
- A free public layer, kept in place
Accessibility remediation
Government websites and public documents remediated at source level against WCAG 2.1 AA, ahead of the ADA Title II deadlines.
- Three-way audit: scans, manual checks, screen readers
- Source-level fixes, never overlay widgets
- Tiered document remediation with a re-test report
Resident services front desk
Policy answers, guidance, checklists and status lookups handled first by a smart desk; anything beyond is handed to staff with a summary.
- Module by module, no system replacement
- Answers drawn only from issued policy
- Peak triage and backlog ordering
Digital government
Institutional identity, forms, cases and service data on a shared foundation, partitioned by agency.
- Institutional identity and single sign-on
- A forms and case engine
- Service data partitioned by agency
AI governance & use assessment
Every AI tool in use across departments — shadow AI included — inventoried and risk-graded, with usage policy, procurement review and a filing ledger put in place.
- A use-case register with a shadow-AI annex
- Risk grading with disposition advice
- A filing ledger and quarterly reviews
How the wider product range enters a national programme
A national programme uses more than five government products. Platform, enterprise and foundation capabilities are recombined inside the project boundary.
Identity & public services
Institutional One ID carries organisations, roles and permissions. Public portals, AI service assistants, forms and case systems sit behind the same identity layer.
Data & awareness
Global intelligence, hazard warning, data interfaces and risk mapping share the situational core. Every record keeps its source, time and evidence link.
Security & ongoing operations
MIANGAI defence, website security assessment, audit logs and ONE managed operations form the long-term line after delivery.
Foundation & custom systems
Custom software, data platforms, edge nodes and KINGAI OS are assessed into each programme.
Three platform foundations
Products can be replaced. The foundation keeps the account relationship, the operating data and the audit trail.
Institutional One ID
Organisation structure, role permissions, single sign-on integration and audit trails derived from one identity system for public services and internal workspaces.
Situational intelligence core
Public-source data organised into entities, relationships, timelines and evidence, shared by intelligence, warning, city operations and risk products.
ONE operations foundation
Monitoring, response, upgrades and re-verification after delivery, all logged. AI agents run daily operations; high-impact actions stay behind human approval.
From design to long-term operation
Government cycles are long. The entry point should be small, and the evidence should arrive early.
Use case & boundary
Confirm the agency mandate, data scope, deployment location, use limits and acceptance owner.
Working pilot
Build a usable sample on controlled data: one defence deployment, one awareness graph or one region connected to warning feeds.
Phased build
Build and integrate by module. Each phase is accepted separately, with interfaces and data export written into the contract from phase one.
Managed operation
Operating state, response records and upgrades are read back continuously, re-verified monthly and reported.
- Engagement models combine design, implementation, platform subscription and managed operations.
- Deployment can use cloud, customer premises or a dedicated network, with residency and key arrangements set per project.
- No prices are published. Scope and a formal quote are provided in writing after discovery.
Four delivery principles
These principles belong in the design and the contract, not only on a web page.
Open and modular
Interfaces, data dictionaries and export paths are settled first, so the client can take its data and configuration to another supplier.
The client holds the data
Agency data belongs to the client. Access follows roles, logs are auditable and keys can be customer-held.
Approval for high-impact actions
Automated response runs only inside written authority. Wider blocks and policy changes escalate to a human.
Use limits in writing
Public-source and non-classified is the intelligence boundary. No facial-recognition templates. No mass personal surveillance.
Where to next
Trust & compliance
Deployment models, data sovereignty, security operations, supply-chain screening and use limits, in one place.
MIANGAI active defence
Detection, response and audit for government networks, mail systems and critical infrastructure.
Project enquiry
Name the agency, the use case, the deployment environment and the data sources. The first reply covers boundary and route.
Have a concrete use case in hand?
Send the agency type, the problem, the deployment environment and the data sources. The first round answers boundary and route only.
