← All case studies

Fintech · Property · Malaysia

Property & tokenised listing platform (Niaga Prestasi)

Sevendyne built a remote Vue.js and Laravel team for Niaga Prestasi, then that team worked with their property operators to design and ship buy/sell CRUD, Pusher real-time UI, and tokenised listing workflows.

Technical one-pager for prospects: Open brief → Print to PDF

3-minute CTO brief

We staffed a Vue/Laravel pod for Niaga Prestasi and placed them with property operators — standups on workflow states, PR reviews on transaction rules, and pairing with client leads on live listing UX. Operators needed governed CRUD and live listing state — not email-driven spreadsheets. The team kept Laravel for validation and transactions, Vue for workflows, and Pusher for domain events after commit so UIs never flash stale data.

  • Complexity: Multi-role CRUD · real-time operator UX
  • Client group: Same Niaga Prestasi footprint as TLMS
  • Contrast TLMS: Front-end reactivity vs queue back-end scale

Full-stack web · real-time UI · property workflows

API + reactive UI

Laravel models enforce buy/sell rules at the boundary. Vue SPAs consume JSON per workflow (search, offer, admin). ListingPublished-style events fire only after DB commit, then hit private Pusher channels scoped by operator role.

DecisionRationale
Pusher over self-hosted WSShip operator live-updates without running a socket cluster
Events after commitUI never shows rolled-back listing state
Shared Vue form kitBuy/sell/admin screens reuse validation components

Code shape (representative)

DB::transaction(function () use ($listing) {
  $listing->transitionTo('published');
});
event(new ListingPublished($listing)); // → Pusher private channel

Production outcomes

  • End-to-end property listing and transaction UI on Laravel + Vue.js.
  • Real-time updates via Pusher for operators and end users.
  • Delivered alongside TLMS logistics and RedDot Payment programmes.

Download technical brief (PDF) Schedule a technical review