Novax Price Alert

Problem

Users needed reliable price monitoring and alerts without ambiguity in asset selection, unit (Toman primary), stale data, or duplicate notifications. The system had to coexist safely with other production sites on the same VPS.

Solution

• Explicit 6-step staged alert flow with confirmation gate (per improvement report)
• Canonical asset identity + display snapshots at creation time
• Atomic claim + idempotency + freshness policy enforcement in evaluator/dispatcher
• Rich TWA (tabbed: Prices, My Assets, Alerts, Advanced Charts, Create) with smart suggestions and portfolio demo
• VPS deploy with PM2 (api+worker on 8001), nginx per-subdomain, safe rsync, healthchecks, backups
• Policies codified in domain/policies.py and documented

Result

Production system live at novax.alirezasafaeisystems.ir with hardened alerts (no dups, freshness respected), rich client UX, co-existing safely with 3 other live sites. All report phases (0-4 + growth) completed and deployed.

Visit novax.alirezasafaeisystems.ir

Role

Full-stack product engineering: architecture, backend (FastAPI + worker + policies), TWA (Next-like single-file rich app), ops (PM2/nginx/VPS), docs alignment with report.

Tech Stack

Python/FastAPI, SQLAlchemy/Alembic, Redis, PostgreSQL, Telegram Bot API + CF Worker relay, Next.js-style TWA (Tailwind + Chart.js), PM2, nginx, certbot, GitHub Actions for price ingest.

Proof

Live subdomain with health 200, TWA fully functional (tabs, My Assets, suggestions, charts), worker evaluating alerts, safe multi-site VPS, all per report + production checklist executed.