Installed on your premises. Not on ours.
Koshtaq is on-premise NBFC software: lender allocation software installed on your servers, beside your LMS, that sends nothing to KGT. This page is for IT, CISO and compliance teams: what runs where, who can see what, and what the inspector gets.
Your data never leaves your network.
On-premise installation
Runs inside your infrastructure as a Docker Compose stack behind nginx. The loan tape, customer data and lender terms stay on your network. There is no shared multi-tenant instance.
Nothing is sent to us
The application sends nothing to KGT on its own. The only data that leaves your network is the lender schedule your team chooses to send.
Support without access
Fixes and tuning are shipped as versioned releases your IT team deploys. Live access to the system is granted per session, by you, and shows up in the audit log like any other login.
- 1Your LMS
Monthly loan tape, Excel/CSV or a direct read, inside your network.
- 2Koshtaq server
Validates, allocates, stores. PostgreSQL on your VM. Backups on your schedule.
- 3Your treasury team
Browser access over your LAN or VPN. Role-based, every action logged.
- 4Your lenders
Only the per-lender schedule your team exports and sends. Nothing automatic.
Koshtaq is not offered as a shared, hosted service: every installation runs on servers the customer controls. Results from a live NBFC are in the case study.
Three roles. Enforced server-side.
Role claims are checked on every endpoint, not just hidden in the UI.
A record that cannot be rewritten.
A Viewer login for your auditors, and an append-only log of every action with user, timestamp and reason. Numbers that reconcile, month after month.
Immutable audit log
Append-only across every table, filterable by table and date: who, what, when, and the reason where one is required. Nothing in the system edits or deletes a log row.
Rule-change protection
Versioned groups plus version-pinned allocations mean a rule change is always attributable and never retroactive.
Quarantine edit trail
Every manual field correction on a quarantined loan is stored separately from the loan itself.
Controlled deletion
Purges run as previewed, confirmed, logged jobs. No silent deletes.
Authentication
JWT sessions with bcrypt-hashed credentials and role claims enforced server-side on every endpoint.
Double-hypothecation lock
A uniqueness constraint in the database on loan and run month. Structurally impossible, not procedurally checked.
Boring in the right places.
A standard stack your IT team already knows how to run, back up and monitor.
Built and supported by KGT Solutions. About KGT Solutions
Questions IT and compliance teams ask.
- Does any of our data reach KGT?
- No, not unless your team sends it. Koshtaq runs on your servers and sends nothing to KGT on its own. The only data that leaves your network is the lender schedule your team chooses to send.
- Who installs it?
- KGT engineers, working with your IT team, on a server or VM inside your network. Koshtaq runs as containers (Docker Compose behind nginx) with a PostgreSQL database that you back up on your own schedule.
- How are updates applied?
- As versioned releases your IT team deploys, when it chooses. Nothing updates itself.
- What happens to our data if we stop using Koshtaq?
- Nothing leaves. It is already on your servers, in your database and under your backups, so there is nothing to retrieve from us.
Get the technical brief.
Ask for the technical brief, or send us your security questionnaire.