Development of CarlsbergHub & ParkingHub

The Problem Local communities run on fragmented tools. Residents use one app to find services, another to buy and sell, a third to communicate, and nothing to manage parking which in dense urban districts like Carlsberg and Sydhavn is a daily friction point. The client needed one platform that eliminated that fragmentation entirely a single ecosystem where residents, vendors, and administrators could transact, communicate, and manage local operations without switching between tools or losing context.

What We Built Two interconnected products: a full-featured community and parking web platform serving the Carlsberg district, and a standalone mobile parking app now running across both Carlsberg and Sydhavn with Stripe and MobilePay integration.

The web platform brings three distinct systems together under one roof, a marketplace for buying and selling locally, a services directory where residents discover and book local providers, a parking management system where spot owners list availability and renters reserve and pay, and a real-time messaging layer connecting everyone.

Three different user types buyers, vendors, and admins each get a distinct, role-aware interface with access control enforced throughout.

The parking system was the most operationally complex piece. Spot owners list availability, set pricing, and manage license plate verifications. Renters search available spots, go through a validated booking flow, and pay through integrated payment processing. The system handles the full transaction lifecycle reservation, payment, access confirmation, and dispute management without admin intervention.

Real-time messaging runs on Socket.io with typing indicators, read receipts, file attachments, and live notifications. It's not a bolt-on chat widget it's the communication layer that makes every other transaction on the platform feel connected. A buyer and vendor negotiating a marketplace listing, a resident following up on a booked service, a parking renter confirming access all happening in the same unified messaging environment.

The marketplace goes beyond basic listings advanced filtering lets buyers narrow by category, location, price, and availability, while favourites and a review system build the trust layer that makes local commerce actually work between strangers. Every transaction has a paper trail and every vendor has a reputation score.

The services directory gives local providers full profiles with detailed descriptions, booking capabilities, and availability management residents don't just discover services, they book them directly through the platform without going off-platform to WhatsApp or email.

Admin panels give full operational oversight across every layer user management, listing moderation, service approvals, parking dispute resolution, and detailed analytics covering revenue, usage patterns, and engagement metrics across all three user types. The platform runs itself operationally, but when intervention is needed the admin tooling makes it fast.

The ParkingHub mobile app extended the parking system into a standalone product covering two districts. Stripe and MobilePay integration means residents can pay however they prefer card or Denmark's dominant mobile payment method without friction at the point of reservation.

Frontend: Next.js with role-based UI rendering for buyer, vendor, and admin interfaces

Backend: Node.js with microservices architecture for scalability across three distinct product systems

Real-time: Socket.io for instant messaging, typing indicators, read receipts, and live notifications

Database: PostgreSQL for transactional data integrity across marketplace, bookings, and payments

Caching: Redis for session management and performance under concurrent users

Payments: Stripe + MobilePay full transaction lifecycle for marketplace and parking

Storage: AWS S3 for images, attachments, and listing media

Stack: Next.js · Node.js · Socket.io · PostgreSQL · Redis · Stripe · MobilePay · AWS S3

First community platform to unify marketplace, services directory, parking, and real-time messaging in one ecosystem

Successfully launched across Carlsberg and Sydhavn districts

ParkingHub live as a standalone mobile app with dual payment integration

High adoption across all three user types buyers, vendors, and admins

Real-time messaging measurably improved transaction completion rates

Vendors report significant reduction in time spent managing listings and client communication

Delivered including testing, QA, and post-launch maintenance

What This Proves Unified platforms are harder than they look. Three separate systems each complex on its own sharing one authentication layer, one database, one real-time infrastructure, and one admin oversight panel, with three different user types navigating it simultaneously. The architecture decisions made at the start determined whether this held together under real usage or fell apart at the seams. It held together and then scaled into a second product.