Ask your bank’s database a question. Get a report back.
Reporting has the question. Only IT can get the data.
So every new figure becomes a ticket. Definitions go back and forth, the SQL gets rewritten, and the answer arrives days later. Here is one typical request, side by side.
The 5 days, message by message
Ticket: For the board pack next week: our ten largest exposures by client group, as a share of own capital, compared with Q2.
Types the same question into Eloniq.
- Ten client groups, share of capital, change since Q2
- The SQL it ran on your warehouse
- The source columns behind each figure
Picked up. One question first: which client groups do you mean, the ones in the core banking system or the connected clients from the large exposures report?
Connected clients as in the large exposures report. Capital as of the quarter end.
First version attached.
top10_exposures_v1.xlsxGroup 3 is €40m lower than in our Q2 report. Guarantees seem to be missing.
Guarantees added, new version attached.
top10_exposures_v2.xlsxNumbers match now. Just in time for the board pack.
See where every number comes from.
Each figure in the report links back to the tables, joins and filters it came from, column by column. Hover a figure to follow it to its source, the way your reviewer would.Here are two of them, traced back the way your reviewer would.
- Step
SUM by client group - Step
JOIN on client_id - Sources
core.loanscore.clients
- Step
exposure ÷ own capital - Sources
€412.6m abovefinance.own_funds
Built to keep your data inside your bank.
Eloniq is designed to run on your bank’s systems with read-only access. These are the principles it is built on.
Designed for your own servers or your bank’s cloud tenant, so source data and results stay there.
Eloniq connects with a read-only database role and queries only the schemas you approve. It does not write to your warehouse.
Sign-in through your identity provider. Each user only sees the tables their existing roles allow.
Request, generated SQL, user and time are stored with each result. The source of each figure is read from the SQL that ran, not written by the model.
Your data, questions and reports are not used to train models. The language model runs in your environment or with a provider you approve.
Eloniq prepares the report. Your team checks and releases it. Nothing is sent to a supervisor automatically.
You talk to the people who build it.
We are Mark and Alex Maldonado, two brothers from enterprise IT. We build Eloniq ourselves and shape it around how regulatory reporting teams actually work. From the first demo to your security review, you work with us directly.


Large exposures first, then one report at a time.
We begin where every figure has to hold up in front of the supervisor. Once it does, the same engine takes on the next report.
Bring a report request you are waiting on.
In 30 minutes we run it through Eloniq with you, on the data of a fictional bank, and show the SQL and documentation it produces.
You talk to Mark or Alex directly.
hello@eloniq.com