Your infrastructure
Install with Docker Compose or Helm on your servers or private cloud.
Self-hosted edition
For banks that keep customer data in house: Konnect ID ships as a compiled container image you run on your own infrastructure, with your own database and storage, activated by a signed license key.
# Docker Compose, from your install kit
cp env.example .env
cp konnect.lic secrets/konnect.lic
docker compose up -d
# Or Kubernetes, with the Helm chart
kubectl create secret generic konnectid-license \
--from-file=license.key=./konnect.lic
helm install konnectid ./helm/konnectid \
--set mongodb.uri="$MONGODB_URI" \
--set license.existingSecret=konnectid-license
# Ready when the database and license are
curl https://kyc.yourbank.tn/api/readyWhat it does
Install with Docker Compose or Helm on your servers or private cloud.
Customer records live in your database and your storage account.
You receive the running product, not its source code.
The flow, the review desk, the API and the webhooks work exactly as in the cloud.
Document reading and face comparison use cloud AI services under accounts you control. Your team decides where those accounts and your storage live.
FAQ
With Docker Compose or the Helm chart, on your servers or private cloud, using your own MongoDB and storage. A signed license key activates it.
No. You receive a compiled container image of the running product, with the same flow, review desk, API and webhooks as the cloud.
Customer records stay in your database and storage. Document reading and face comparison use cloud AI services under accounts you control, so you decide where those run.
The platform