AXOMED — System Architecture & Live Status

LIVE: the entire frontend (all pages), the backend API on the public URL below, the database (every signup/assessment/order writes to it and persists), the automation engine (assessment → CRM lead → notifications), the CRM pipeline with doctor assignment, and the WhatsApp webhook endpoint. Not live: actual Meta WhatsApp delivery and payment gateway — those need real credentials (WhatsApp token + phone ID, payment merchant keys) which only you can provide.

Yes. Submit an assessment → a CRM lead is created instantly, admin/doctor/pharmacy are notified, a patient draft record is created, and the event is logged with a timestamp. You can watch it happen in the Admin portal → CRM & Leads → Automation Events.

Yes. The Admin portal loads leads from the live backend, lets you move a lead through New → Contacted → Qualified → Assigned, and assign it to a doctor. Every action is saved to the database and appears in the automation log.

Yes — a persistent JSON-file store inside the backend process (survives restarts, atomic writes). Tables: users, assessments, leads, orders, inventory, prescriptions, messages, notifications, automation. For production scale it swaps to Supabase/Postgres without changing the API.

The backend runs on a public HTTPS URL (below) reachable from anywhere — this is what the frontend talks to. The frontend is served from permanent /sites/ URLs. Both are live right now.

Frontend = the pages you click (landing, login, portals) — visual product. Backend = the API answering those pages — you can open its URL in a browser to see JSON responses, and every page on this status panel shows a live ping to a real endpoint. The System Status page itself is the best single view.

Questionnaire (assessment quiz) → "You're all set — we're getting your plan ready" screen → care team notified → doctor matched → video consult scheduled → prescription delivered. This mirrors MEDVi's consult funnel and is implemented end-to-end in assessment.html.