Thanks Kamran, "who maintains it in year two" is a better first question than the one I led with. It also makes the hand-over easier: one framework's auth, queues and scheduler are simpler for the next developer to pick up than five libraries wired together by hand. In the post's Driveway Morocco example (a car-rental demo I built in Laravel), adding the Expo mobile app later only meant adding Sanctum tokens to the same backend, with no second server. When you do pick NestJS, do you keep real-time inside the main app or split it into its own service from day one?