Reza Shirazi / Head of Engineering

More I have built 2026

Secure access and password apps

Correct network access for every customer, and passwords that never leave the device.

For an internet provider: right access per customer, once, on the least busy server. Plus two offline apps for passwords and two-step login codes.

Role
Creator and only developer
Years
2026
Scope
Customer access, password safety
Way of work
Built alone, with AI coding help

01 The problem

An internet provider must give each customer the right access, with the right limits, exactly once. People with many passwords and two-step login codes want them locked on their own device, with no server in between.

02 Result

  • When a customer moves to another server, used traffic moves too, so nobody gets a free new plan.
  • Every step of each access request is logged, so support can see what happened.
  • Passwords and two-step login codes stay on the device; neither app makes any network calls.

03 What I built

  • 01

    Customer access setup

    Checks a customer's plan in the provider's billing system, then creates network access on the least busy server with the right limits.

  • 02

    Works when a server fails

    Checks all servers at the same time, so one server that is down does not stop a customer's request.

  • 03

    Encryption on the device

    Secrets are locked with a key made from one passphrase, through a slow key step that makes guessing a password very costly.

  • 04

    Quick, safe unlock

    Fingerprint or face unlock, an automatic lock when the app sits unused, and copied secrets cleared after 30 seconds.

  • 05

    Fill only the right site

    Saved logins and two-step login codes are offered only on the matching app or website. Web pages never see the secrets.

  • 06

    Encrypted backups

    Backup files use the same encrypted format as the stored data, so a copied file shows nothing readable.

04 Risks I handled

  • Risk 01

    One account per customer

    Two requests at the same moment could create two accounts for one customer. A lock per customer in the database lets only one of them run.

  • Risk 02

    Codes must be exactly right

    A wrong two-step login code means the user cannot sign in. The code maker was written from the official standard and checked against its published test values.

  • Risk 03

    Web pages asking for secrets

    Any website can send messages to a browser extension. Private actions are accepted only from the extension itself, and tests check that web pages are refused.

05 Examples

  • Example 01

    Provider access service

    Links a provider's billing system to several network servers. Customers get their setup from a chat bot or a web page with a QR code.

  • Example 02

    Offline password manager

    An Android app for logins, notes and identities, with a password maker and two-step login codes. No server, no account, no sync.

  • Example 03

    Login code extension

    A browser extension for two-step login codes, unlocked with Touch ID. It imports existing codes and skips any it already has.

06 Stack

  • Python
  • FastAPI
  • PostgreSQL
  • Kotlin
  • React Native
  • TypeScript
  • JavaScript
  • Web Crypto

Get in touch.

Hiring an engineering lead, or building a platform or AI agents? Tell me about it.