On-Premise Comprehensive KYC
ID Fort is the full ID Analyzer stack deployed inside your perimeter. OCR, 1:1 face match, liveness, and AML lookups — through a self-hosted portal or REST API. Customer documents and biometrics are processed and stored entirely on your own infrastructure.
Next-Level Identity Verification, Self-Hosted
The cloud platform refined and repackaged for the regulated industries that can't move data off-perimeter. Docker container. Single-server install in minutes. Horizontal scale-out when you outgrow it.
Docker-Native Deployment
Pull the image, run the container. Single Linux or Windows host on day one. Add nodes behind a load balancer when you need horizontal scale.
Your Data Stays
on Your Servers
Every document, selfie, and verification result is processed and stored on your own infrastructure — customer data never leaves your perimeter. Fully air-gapped deployment is available for select environments.
Cluster Scale to Production Volume
Multi-node deployment behind your load balancer. Add Nvidia GPU nodes when latency matters; throw CPU at it when cost does.
What Self-Hosting Unlocks
Three controls the cloud tier doesn't expose — because they only make sense when you own the box.
- Full user management & quota control
- Bring-your-own database & S3 bucket
- 70+ validation thresholds, all tunable
Admin
Console
Operator Account
Compliance Role
Active now
Quota Usage
Operator Team
3 reviewers online
The Same Engine, Inside Your Perimeter
3,000+ Documents
200+ countries, all in-perimeter
70 Validation Checks
Every threshold tunable to your risk tolerance
20+ Anti-Forgery Models
Tamper, recapture, deepfake, splice detection
Admin Portal
Operator review queue, transaction logs, threshold tuning — all browser-accessible
Today
12
05:00
Verify queue
09:00
Review queue
Verdicts
Accepted
94%
Manual review
4%
Rejected
2%
1:1 Face Match + Liveness
Biometric models bundled, no separate API
AML & PEP Lookup
Bring your own sanctions list or use ours
Same REST API
Drop-in replacement for the cloud endpoint
Six Controls You Only Get When You Own the Box
The hard-coded restrictions of the multi-tenant cloud — provisioning limits, fixed retention, untouchable thresholds — disappear when the verification engine runs on your own hardware.
User & Quota Management
Provision operators, limit access, throttle quota — no shared tenancy
Bring-Your-Own Storage
Persist documents and transactions to your DB and S3 bucket of choice
Per-Check Threshold Tuning
70+ validation thresholds, each individually adjustable in the admin portal
Field Bounding Boxes
Every extracted field returns pixel coordinates — for highlighting, masking, or audit
Signature Detection
Locate and extract signatures from contracts and IDs for downstream verification
Data Obscure
Auto-redact PII fields on stored images per your DPA before they hit the disk
From Docker Pull to First Verification
Same five steps every ID Fort deployment follows — bank or healthcare network, single node or load-balanced cluster.
Deploy the Docker Container
Pull and run the ID Fort Docker image on your own server or private cloud. Setup takes less than 10 minutes on any Linux or Windows environment that supports Docker.
Configure Verification Rules
Set up document validation thresholds, security profiles, accepted document types, and AML screening rules through the built-in administrator portal.
Integrate via REST API
Connect your application to ID Fort using the same REST API as the cloud version. Submit documents and face images for verification through standard HTTP requests.
Process Verifications On-Premise
OCR, face matching, liveness, and anti-forgery checks all run entirely on your infrastructure — customer documents and biometrics never leave your network.
Monitor and Manage
Track verification activity, manage API users, review transaction logs, and configure system settings through the built-in web dashboard.
When to Pick ID Fort Over the Cloud API
Same verification engine on both sides. The question is whether the verification needs to stay inside your perimeter — and who manages the box.
| Feature | Cloud API | ID Fort On-Premise |
|---|---|---|
| Deployment | Cloud-hosted, instant setup | Self-hosted Docker container |
| Data Control | Processed on ID Analyzer servers | Full data sovereignty |
| Scalability | Auto-scaling included | Scale with your infrastructure |
| Maintenance | Managed by ID Analyzer | Self-managed updates |
| Best For | Startups & SMBs | Enterprise & regulated industries |
Questions From the Procurement Review
Five questions banks, government agencies, and regulated enterprises consistently bring up before the pilot starts.
ID Fort ships as a Docker container, so it runs on any host that supports Docker — almost every Linux distribution plus Windows systems that support virtualization. No platform-specific build.
Minimum: 4 CPU cores, 16 GB RAM, 30 GB disk. Recommended for production throughput: 8 CPU cores plus an Nvidia GPU. The GPU is optional but cuts face-match and document-authentication latency dramatically.
No — Docker pull, run, configure. The container is up in under ten minutes. Everything else (operator users, accepted document types, threshold tuning, AML lists) happens in the browser-based admin portal.
Yes. Deploy multiple ID Fort instances behind a load balancer to handle whatever throughput you need. The instances are stateless on the verification path — scale-out is linear, no coordination layer required.
Yes. Tell us your use case via the contact form and we'll spin up a free demo server on AWS so your team can run end-to-end verifications before the procurement conversation starts.
Run a Pilot Inside Your Perimeter
Free demo server on AWS so your security and compliance teams can run real verifications before procurement starts. Pilot turns into a production deployment when you're ready.
