How it works
No cloud tenancy.No implementation project.
Ironwood runs on the network your bank already has. Deployment is copying a folder to a share and setting your policy limits on one tab. There is no server to provision, no database, and no borrower data leaving the building.
Deployment
Running the same day
01
Copy a folder to a share
The suite lives on a network location your credit department already uses. No install, no service account, no vendor access to your environment.
02
Set your policy limits
The grading limits live on one tab. Enter the limits your credit policy already states and every workbook follows them.
03
Open a live file
Import a borrower statement and work a real credit file. Most banks are producing memos the same day they receive the suite.
For your IT department
Open, verifiable, and inside your perimeter
Borrower data stays on your file server. There is no cloud tenancy, no database server, and no outbound connection required for the suite to function.
The VBA is unlocked. Your team can read every line of it before the suite goes on the network, and again after any update.
A SHA-256 checksum ships with every release so IT can verify that what arrived on your server matches what we built.
We provide an information security document written for the people who will ask these questions, not a marketing summary.
Terms of use
Licensing
What you buy
A licence for the bank rather than a seat count. It is a site licence, so every lender in the bank can use it. Terms are covered on the walkthrough.
What ships with the licence
The consumer, commercial, ag, and global review workbooks, the PFS templates, the risk rating structure, the scenario builder, and the memo generator.
Configuration versus implementation
Setting your policy limits is configuration and it is included. Changing how the platform calculates is a separate implementation project, scoped and quoted before any work begins.
Support
Questions, small adjustments, and help with a file are part of the ongoing relationship. Anything larger is scoped and quoted before we start.
Where this goes
Ironwood Sentinel is the full platform being built. Your licence here credits toward it and your configuration carries forward.
Answers
Questions we get before the walkthrough
No. It runs on your own file server, offline. Nothing is uploaded and no borrower data leaves the bank.
Copy a folder to a network share and set your policy limits on one tab. Most banks are running the same day.
No. It sits where the credit analysis happens, before the loan is booked.
The formulas are locked. Loan officers type in the fields they need and cannot overwrite the calculations by accident. Every release is verified by recalculating the workbook and reading the output against known inputs.
There is no server, no database, and no vendor access to your environment. We provide an information security document written for your IT team and a SHA-256 checksum for every file.
The grading limits live on a tab you control. You set your own policy limits and the workbook grades every request against them. Change a limit and every subsequent writeup reflects it.
Configuration is included. Changing how it calculates is a separate implementation project, quoted before any work starts. You approve the scope before there is an invoice.
Ironwood Credit Suite is in live use at a community bank, refined against real loan officer feedback on real files. We are not naming the bank yet at their request, but we can show you a complete walkthrough built on fictional borrower data that reflects exactly what a real file looks like.
