Credora

Credora decides which corporate customers of Sapphire Bank get a pre-approved loan offer, and it does the work inside Exasol Personal.

It is live and working. Every link below is the real deployment.

Sign in with one click on the login page, or use a demo login. All data is synthetic, so the passwords are public.

• admin / Demo@123 is the bank manager, who approves models and policy.
• datasci / Demo@123 is the data scientist, who runs the analysis and publishes it.
• loanops / Demo@123 is loan operations, who assigns companies to relationship managers.
• rm / Demo@123 is Subhashree Mohanty (RM001), a relationship manager who sees only her own companies.

What it does#

Sapphire Bank has 1,000 corporate current-account customers and wants to approach the best of them with a pre-approved offer. Each offer has an amount, a rate and a tenure, plus a negotiation limit the relationship manager can move within. The data for that sits in the bank's Oracle, MySQL and PostgreSQL databases (including each company's credit need on file) and in 3rd party data via API from CIBIL, GSTN and the Account Aggregator. One call, EXECUTE SCRIPT CREDORA.RUN_ANALYSIS('<run>'), reads all six sources in place, scores risk with models trained in Exasol and prices and ranks the companies analysed in about 18 seconds.

The data scientist runs the analysis and publishes it. Loan operations assigns the companies to relationship managers, and each manager negotiates inside the limit and logs the loan status. The admin approves model activations and policy changes. In every role, Ask Credora answers plain-English questions with Claude through the official Exasol MCP server.

Exasol features used#

Credora started on the Exasol Personal Local Starter Kit (exakit 0.2.3, with the Exasol MCP server 2.3.0, exapump 0.13.1 and pyexasol). It was then deployed on AWS with the Exasol Personal launcher 2.3.0, running Exasol 2026.1.0 on an r6i.xlarge.

Each feature, with its code and the reason for it, is in docs/WHY_EXASOL.md.

Roles, enforced by Exasol#

Every app role reads Exasol as its own database user. The backend runs each screen's queries as that user, and Ask Credora starts the MCP server logged in as the same user. When Exasol refuses a query, the screen shows 403 Exasol denied access for your role. Analysis, training and the purge run as the service user CREDORA_SVC.

The V_RM_* views join CREDORA.RM_ASSIGNMENT on EXA_USER = CURRENT_USER, and R_RM has no grant on the result tables. Signed in to Exasol as CREDORA_RM, V_RM_DECISIONS returns her 25 companies and SELECT * FROM CREDORA.DECISIONS fails with "insufficient privileges". A prompt can't widen that, because the limit lives in the database.

Verify it yourself#

Every claim can be checked on https://credora.loan and in the code.

Deploy it yourself#

Everything runs from your own machine against your own AWS account. Nothing in the code is tied to an account or a domain.

1. Install the exasol launcher from exasol/exasol-personal and check it with exasol version.
2. Install the AWS CLI v2, Docker, Python 3.12 with uv, Node.js 20+ and Git.
3. Log in to AWS, and have a Route 53 hosted zone in that account. The default sizes need 6 vCPUs of on-demand EC2. bash aws configure --profile mysite aws sts get-caller-identity --profile mysite
4. Clone the repo and install the deploy tool. bash git clone https://github.com/anamika-iit-kgp/credora.git cd credora make setup # or: uv venv deploy/.venv && uv pip install -p deploy/.venv -r deploy/requirements.txt
5. Copy .env.example to .env.mysite and fill it in. The name after .env. is the deployment name.

6. Deploy, then write every URL, login and password to deployments/mysite/ACCESS.md. bash python deploy/credora.py deploy --env mysite python deploy/credora.py access --env mysite

deploy is idempotent. It installs Exasol through the launcher, creates the RDS databases, app host and DNS with OpenTofu, starts the containers, generates 1,000 companies and sets up every Exasol object. Database and API passwords are generated into AWS Secrets Manager. Other commands (status, ship, exasol, generate, destroy) and moving a deployment to another machine are in docs/PORTING.md.

Diagrams#

The full design, with failure modes and trade-offs, is in docs/architecture.html.

Repository layout#

exasol/     SQL, Python UDFs, Lua scripts, preprocessor modules and the semantic model
backend/    FastAPI with roles, jobs, Ask Credora and the Exasol audit
frontend/   React and TypeScript, with Explain mode
mocks/      mock CIBIL, GSTN and Account Aggregator APIs and the data generator
deploy/     the one-command deploy tool, with infra/ (OpenTofu) beside it
docs/       architecture, diagrams, glossary, data model, APIs, porting

Documentation#

Built with Exasol open source, thank you#

Every project below runs in the live deployment or in CI. Thank you to the Exasol team and to everyone who contributes to them.

About, contributing and contact#

Credora is an ExaThon India 2026 project. It is a try-out of the Exasol Personal Local Starter Kit and of Exasol Personal, deployed on AWS. The live deployment runs in my own AWS account, on the domains credora.loan and credora.link, which I registered for this project.

Contributions are welcome. Fork the repo and open a pull request, or open an issue first for a larger change. To build on Credora, adapt it for your bank, or buy or license it, raise an issue and I will get in touch.

Project by Anamika, Product Manager @ Equitas Small Finance Bank. Sapphire Bank is fictional, and all data is synthetic.

License#

MIT. See LICENSE.