Repository navigation
Home
AzureBank is a personal banking app that I built as a portfolio project: a .NET 10 API behind an ASP.NET Core backend-for-frontend (BFF), a React 19 single-page app and SQL Server. It is a demo with invented money, not a bank.
I am the project's architect and sole engineer. I designed the system and decide what gets built. I have written part of the code myself, and I direct the AI coding agents that write the rest under rules I set. I read the code I merge. Every merge is my decision and my responsibility. The Engineering Playbook explains how I work.
Vladislav Aleshaev · LinkedIn · GitHub
Open the live demo · Code and README
On the sign-in page, one press of Try the demo gives you a private copy of a bank account, with no sign-up. The app sleeps when nobody is using it: the link opens an entry page that starts it and shows the wait, about 25 seconds when it was asleep.
The interesting part is not the screens. It is what has to stay true because the app moves money.
- A payment is applied at most once per key.
- The JWT never reaches the browser.
- One PIN entry authorises one payment.
- Security events go to an audit trail that can be checked, and its limits are written down.
- The frontend is held to the contract that the API generates.
- On Azure the database has no password.
| If you want to | Read |
|---|---|
| see it work in a browser | Quick tour |
| understand the design | How it works |
| judge the reasoning | Decisions |
| judge the evidence | Tests and CI |
| see how it runs in the cloud | On Azure |
| read what an interviewer asks | FAQ |
| know how it came to be | Story |
- Each page here is short and links to the repository for the detail.
- The decisions are written down: sixty-four records, with the alternatives that were rejected and what is left open, where a record has them.
- What is not done is written down too: Status and known limits.
- To run it on your own machine, see Try it.
- The code is released under the MIT License.
Next page: Quick tour.