Meridian Rotorcraft

Architecture

Flagship model for a rotorcraft dealer

What this demonstration implements now, and what production on ConsultifyIT infrastructure would add without changing the public story.

Now

Next.js App Router front end. Catalog as typed modules. Bookings and inquiries in browser storage so a client walkthrough works on a laptop with no database. Pages cover inventory, factory quote, lease, brokerage intake, schoolhouse enrollment, hangar slots, private and corporate desks, security narrative, and an operations console.

Production target

Same UI. Postgres for listings, hours, and seats. Auth for the desk (sales, instructor, inspector). Object store for log PDFs and identity scans. Payments for deposits and class fees. Calendar sync. Email/SMS from the desk. Kill-switch as a documented destruction workflow, not a localStorage wipe.

Domains

  • Catalog — airframes, factory options, photos
  • Transactions — sale, lease, brokerage
  • School — courses, sessions, seats, syllabus
  • Hangar — work orders, pre-buy, return to service
  • Desk — bookings, inquiries, status
  • Trust — roles, retention, kill switch

Presentation note

Trading name, staff, N-numbers, and CRS code are fictional. Aircraft types, 2026 list prices, KSGJ geography, lease-rate shape, and service mix follow a real coastal Robinson-type dealer plus school and repair-station work.