What does software architect mean in Hossein Safaverdi's case?

He owns the shape of the system and still writes the code for the parts that carry risk: payment flows, data models, and anything involving money or compliance.

Is Hossein Safaverdi available for work?

For one more engagement this year, and not for a full-time role. Most of his week goes to Dadyar and two products behind it.

What is the fastest way to reach Hossein Safaverdi?

Telegram at @HosseinSafaverdi, usually answered the same day. Phone is +98 912 175 1273 and email is safaverdi.hossein@gmail.com.

00Profile

Tehran, Iran · UTC+3:30

Hossein Safaverdi

Q: Do you work with companies outside Iran?

Yes. LeadFi is in the United States and the 2025 to 2026 platform client was in Europe. Payment and contracting arrangements are settled in the first week.

Software architect. Payment systems, core banking, ERP.

For six years I've built backend systems where a mistake costs somebody money. A payment gateway and core-banking platform at Hami System Sharif. A provider-agnostic payment layer over Stripe and NMI for LeadFi in the United States. An ERP that five departments at AhanOnline still run on. Since 2025 most of my time has gone into products of my own, and the first one is live.

Message me on Telegram One-page CV

Based in: Tehran, Iran
Works with: Teams in the US and Europe, remote
Writes: C#, Python, TypeScript, SQL
Domains: Payments, core banking, ERP, multi-tenant SaaS
Speaks: Persian (native), English (professional)
Shipped: dadyar.pro

01Now

What I'm doing now

Dadyar is live at dadyar.pro. I still write most of the API myself, and all of the corpus pipeline and the citation verifier.
One client engagement running: payments work for LeadFi on Django, Stripe and NMI.
Two more products in private build. There's nothing to show yet, so there's nothing here about them.
Room for one more engagement this year. Not looking for a full-time role.

Reviewed August 2026

02Building

What I'm building

Three products, all of them mine. One has shipped. The other two are early enough that naming them would be marketing rather than information.

Dadyarدادیار

Live

Founder · architect · still writing the code

A Persian-language AI legal assistant for Iranian law.

You ask a legal question and the answer comes back with the text of the article it rests on. Every citation is resolved against the corpus before it reaches the screen, and anything that doesn't resolve is stripped out. Ask something Iranian law has no answer for and it says so instead of inventing one.

Around that sits the rest of the product: the full text of eighteen Iranian codes published article by article, contracts drafted clause by clause from a vetted library where each clause names the article it stands on, free calculators for diyeh, mahriyeh, court fees and statutory deadlines, and licensed lawyers you can book inside the app once a question turns into a real case.

Fabricated citations are why nobody sensible trusts a general chatbot with legal work. Making them impossible is the whole product, and it's an engineering problem before it's a legal one.

Corpus: 18 codes, 5,500+ articles, each at its own URL
Contracts: 28 types across 7 categories, clause library with citations
Stack: .NET 10, Next.js 15, PostgreSQL, pgvector
My part: Architecture, corpus ingestion, citation verification, most of the API

Open dadyar.pro

Accounting and operations platform

Private build

For companies that have outgrown spreadsheets and can't justify an enterprise ERP. Ledgers, documents, receivables, reporting. Clean-architecture .NET API with a customer app and an operator console generated from one OpenAPI contract. I led ERP at that scale for somebody else first.

Multi-tenant SaaS for messaging-first audiences

Private build

For teams whose audience lives in messaging apps rather than social feeds. Workspace isolation enforced in the data layer, subscription billing, channel and bot administration, an operator console behind it.

If either of those is close to something you're working on, ask me. I'll tell you more than this page does.

03Work

Systems I built for other people

Four engagements worth describing. Two as an employee, two on my own.

LeadFi

Payments · United States · 2025 to now

A payment layer that doesn't care which processor is behind it. Stripe and NMI sit behind one interface: SetupIntents, vaulting and tokenization, webhook-driven state transitions. Transactional flows run on Celery and Redis, with Prometheus metrics and mypy in strict mode over the whole service.

Changing processor used to be a rewrite. Now it's configuration.

Django, DRF, PostgreSQL, Celery, Redis, JWT, Stripe, NMI, Prometheus

Hami System Sharif

Payment gateway and core banking · Iran · 2025 to 2026

Lead architect on payment-gateway systems, then senior architect on core banking. I set the microservice boundaries and the technical standards the team built against, and designed the distributed payment services that talk to several providers at once under PCI-DSS-aware constraints.

One constraint shaped everything else: a transaction is allowed to be slow, and it is never allowed to be lost.

Microservices, distributed transactions, high availability, PCI-DSS-aware design

Client in Europe

Platform and integrations · Europe · 2025 to 2026 · under NDA

A whole .NET service estate delivered end to end: a webhook-driven messaging bot service, an embedded web client over REST and OpenAPI, internal admin APIs, and crypto-gateway integrations. Containerized, with CI/CD from the first commit rather than bolted on at the end.

ASP.NET Core (.NET 10), EF Core, PostgreSQL, Redis, Docker Compose, GitHub Actions

AhanOnline

ERP and trade platform · Iran · 2020 to 2025

An online marketplace for steel and iron in Iran. I led the ERP that its call center, trade, accounting, procurement and sales teams work in, then spent the following year on the unglamorous half of the job: making it hold up under real transaction volume and rewriting the internal workflows it had inherited.

Before the ERP I built their warehouse and inventory system in Nest.js, which is where I learned what production actually costs.

Domain modelling, high-volume data, SQL Server, Nest.js, TypeScript, RBAC

04Record

Where I've worked

Independent

Founder, software architect, technical lead

Own products, and a short list of client engagements. A few engineers work with me.

2025–now

LeadFi

Backend engineer, remote (United States)

Provider-agnostic payment platform over Stripe and NMI, on Django and PostgreSQL.

2025–now

Client in Europe

Backend engineer, remote (Europe)

ASP.NET Core services, messaging bot platform, admin APIs, crypto-gateway integrations.

2025–2026

Hami System Sharif

Senior backend developer, lead architect

Payment gateway architecture, then core banking. Microservice boundaries and team standards.

2025–2026

AhanOnline

Senior backend developer

ERP across call center, trade, accounting, procurement and sales. Security and performance work.

2022–2025

AhanOnline

Backend developer

Warehouse and inventory system in Nest.js. REST APIs, role-based access control.

2020–2022

2019 to 2023B.Sc. Business Management, University of Applied Science and Technology, Tehran

05Stack

What I work with

Languages

C#, Python, TypeScript, SQL

Backend

ASP.NET Core (.NET 10), EF Core, Django, Django REST Framework, Celery, Nest.js

Architecture

Clean architecture, CQRS with MediatR, event-driven design, microservice boundaries, domain and data modelling

Payments

Gateway design, Stripe, NMI, tokenization and vaulting, webhook reliability, idempotency, PCI-DSS-aware design, core banking

Data

PostgreSQL, SQL Server, Redis, pgvector

Run it

Docker, Docker Compose, GitHub Actions, Prometheus, structured logging, OpenAPI

Not my strength

Front-end craft beyond what a service needs, and visual design. I know enough to build an admin console and to review the work. For anything a user has to enjoy looking at, I bring in somebody better.

06Method

Working together

I take on one or two things at a time. The work I'm useful for tends to look the same from the outside: money moves through the product, or regulated data sits inside it, or the codebase has quietly become expensive to change and nobody can say exactly when that happened.

You get a written architecture your engineers can argue with. I build the parts that carry the most risk myself and hand the rest over with the reasoning attached. A few engineers I've worked with before come in when a project needs more hands. There's no agency behind me and nobody in the middle.

If your problem isn't one I'm good at, I'd rather say so on the first call than find out in month three.

07FAQ

Questions I get asked

Do you work with companies outside Iran?

Yes, and I do now. LeadFi is in the United States and my 2025 to 2026 platform client was in Europe. Payment and contracting arrangements are worth settling in the first week, and I've had that conversation enough times to keep it short.

What does "software architect" mean in your case?

That I own the shape of the system and still write the code for the parts that matter. Payment flows, data models, anything with money or compliance in it. I've never wanted the version of the job where you stop opening the editor.

Are you available?

For one more engagement this year. Not for a full-time role, because most of my week belongs to Dadyar and the two products behind it.

What is the fastest way to reach you?

Telegram. I read it myself and usually answer the same day. Email works too, it's just slower. If you would rather talk, the number is below.

08Contact

Get in touch

Tell me what you're building and where it hurts. A paragraph is enough to start, and I'll tell you quickly whether I'm the right person for it.

@HosseinSafaverdiTelegram, usually same day +98 912 175 1273Phone, Tehran hours safaverdi.hossein@gmail.comEmail in/hossein-safaverdiLinkedIn cv.safaverdi.irOne-page CV

Other language