Skip to content

Self-hosted edition

Your servers.
Your data. Our software.

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/ready

What it does

Built for regulated onboarding.

Your infrastructure

Install with Docker Compose or Helm on your servers or private cloud.

Your data stays with you

Customer records live in your database and your storage account.

Compiled image

You receive the running product, not its source code.

Same product, same API

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

Questions, answered.

How is it installed?

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.

Do we get the source code?

No. You receive a compiled container image of the running product, with the same flow, review desk, API and webhooks as the cloud.

Does any data leave our infrastructure?

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.

See it with your own documents.