
Moedban — Legal Deadline Manager
In Iranian practice a missed appeal or objection window is usually unrecoverable, yet offices still track them on sticky notes and chat messages. Moedban takes the notice type, the service date and whether the party lives in Iran or abroad, and returns each deadline with its legal basis, counting in the Jalali calendar and rolling any due date that lands on a Friday or holiday to the next working day. Every deadline has an owner and stays on the office's daily page until an action closes it.
// Architecture
The core is a pure rules engine with no I/O: 25 notice types across civil, criminal, Administrative Court, labour, tax and municipal proceedings, with chained deadlines and a rule version stored on every computed date. Around it sit a FastAPI and SQLAlchemy backend with Alembic migrations on PostgreSQL, and a Next.js 14 TypeScript panel built right-to-left. Unlike its sibling products it runs its own standalone backend rather than the shared SaaS core, because the legal engine is its whole value.
// Key capabilities
Every date cites its article
Each deadline shows the article it is based on and the rule version used to compute it, so a lawyer can check the reasoning rather than trust a number.
Reminders, then escalation
A daily sweep reminds the assignee at 7, 3 and 1 days out, then escalates to the office owner when a deadline is a day away or past with nothing recorded, in the panel and over Telegram.
Minimal client data
Cases work under an alias, the client's name is optional, and the office's judicial-portal password is never requested; the user enters the notice and the system only computes dates.
Fits existing tools
Deadlines export to any calendar as an ICS feed or to a CSV, cases can be imported from a CSV file, and a free public calculator works without signing up.
// Technology stack
- Python / FastAPI
- Next.js / TypeScript
- PostgreSQL
- Jalali calendar
- iCalendar
- Docker
// Next step
Need something like Moedban — Legal Deadline Manager?
Tell us what you're building. We'll reply with how we'd approach it, a rough timeline and the first step.
Start a similar project


