Introducing IronValet: secure credential handover with practical deployment paths

The problem

Accounts do not always move through a neat workflow. Someone leaves a role, access changes hands, and the next person inherits a trail of messages or documents. IronValet—the portfolio name for IRONVAULT—gives that handover a deliberate structure. IronValet project overview

Setup is product design

Many internal tools fail between “it runs on my machine” and “another person can operate it safely.” IronValet’s start.py wizard creates required directories, generates .env with secure defaults, normalizes the SQLite URL, applies migrations when requested, and can create the first superadmin.

Local setup

python start.py
flask --app app run --host 0.0.0.0 --port 5000

Three delivery paths

The project supports direct local runtime, a portable Windows package, and Docker deployment. That flexibility matters when a tool must move between developers, office machines, and servers. IronValet login

The Docker guide is explicit about its limits: Gunicorn serves the app, migrations run at startup, persistent data stays outside the image, Compose maps host port 5500, and SQLite requires a single instance until the database moves to PostgreSQL or MySQL.

Docker deployment

docker compose build
docker compose up -d
docker compose logs -f ironvault

Why it belongs here

IronValet combines security thinking, clear operations, multiple delivery paths, and documentation that states constraints instead of hiding them. That is the kind of engineering I want this portfolio to represent.

IronValet case study

Introducing IronValet: secure credential handover with practical deployment paths

The problem

Setup is product design

Three delivery paths

Why it belongs here

Recent notes

Two Personal Projects in Progress: Money Management and Nexa

An Internet Rights Meeting in Iran, and the Officials Who Were Absent