Skip to main content

Border Control Core

Border Control Core is the main functional unit of the Border Control Platform — an orchestration service, API, endpoints, and an ABIS matcher packaged together. It is a Linux-based biometric processing platform that provides fast 1:N identification and 1:1 verification across border workflows. Every other module on the platform reads from and writes to Core.

It exposes secure APIs for enrollment, search, and internal watchlist checks, and supports matching across fingerprints (including contactless), face, iris, and palm prints. The result is a scalable ABIS platform layer that improves identity assurance, reduces fraud, and accelerates border processing while keeping traceability and governance.

Capabilities​

  • Multimodal matching — face, fingerprint (slap and contactless), iris, palmprint
  • Identification (1:N) and verification (1:1 / 1:few)
  • Enrollment with built-in deduplication
  • Persistent traveler register
  • Galleries & watchlists with targeted-search scoping
  • Web UI for operations: applicant records browser with full audit context
  • Workflow orchestration: routes low-confidence cases for adjudication
  • Secure APIs (enrollment, search, watchlist, system integration)
  • RBAC (operator, supervisor, adjudicator, admin)
  • Identity-subset distribution to validation endpoints (Smart Corridors, eGates, border posts)

For the detailed breakdown of in-scope and out-of-scope responsibilities, see What Core does — and what it doesn't.

Resilience and scale​

  • High availability — Active-Active and Active-Passive site configurations; no single point of failure; supports active-active across primary DC + DR site
  • Cluster design — ABIS Management Servers + ABIS Matching Cluster; nodes can take over each other's work; Manager / Dispatcher monitors cluster health
  • Deployment platforms — Kubernetes (standard), VMs, bare metal; cloud, on-premise, or private cloud
  • Database support — Oracle, PostgreSQL, MS SQL (other ODBC/JDBC sources supported)
  • Disaster recovery — Oracle Data Guard or equivalent for SQL replication, side-bucket replication for MinIO object store, independent matcher instances per site

Inside this module​

  • What Core does — and what it doesn't — detailed scope: in-scope capabilities and the boundary with Traveler Management Module
  • Architecture — platform layer + ABIS backend; service map; deployment topology
  • Galleries & Watchlists — gallery model: internal vs integrator-defined; single vs multi-membership
  • Core Service & ABIS — biometric functions, scoring hierarchy, matching modes, deployment details, supported peripherals
  • Data Model — Traveler and Document entity schemas owned by Core (Journey and Encounter entity schemas are documented here for cross-reference, but the data itself lives in Traveler Management Module — Core does not persist or expose them)

See also​