Corridor — Workforce Housing Marketplace Platform
Akhil Yadav
Self-initiated portfolio project. Demonstrates implemented functionality and is not presented as a client engagement. Features and integrations are described according to their verified implementation status.
Source code: github.com/akhilyad/Corridor
Overview
Corridor is a marketplace concept that matches construction and engineering firms (EPC contractors and data-center developers) with vetted vendors who can house crews and provide secured yards and storage next to large build sites. The repository is a full-stack reference implementation of a written whitepaper, including its worked pricing example.
Problem
Large projects must house hundreds of workers near remote sites, and procurement needs housing that also meets compliance and security requirements. Pricing and invoicing across many sites is usually handled in spreadsheets.
Solution
One platform with three roles (client, vendor partner, admin and staff). A single pricing engine drives every euro figure: the public calculator, the pricing page, deployment quotes and invoices, so numbers cannot drift apart.
Public landing page
Key features (implemented)
Pricing engine and live calculator reproducing the whitepaper example (600 crew, 9 months, six sites: about €7.56M gross, about €983K platform take, 19% VAT)
Listings with admin review, booking requests and responses, deployments with multi-site economics snapshots
Compliance document vault with upload, review queue and vendor accreditation
Consolidated multi-site invoices with per-site line items, partner payouts and an audit log
Role-based access (middleware gate plus per-action checks); server actions validated with Zod; hashed passwords and signed session cookies
Admin operations dashboard (seeded data)
Engineering
Next.js App Router, React, TypeScript, Prisma on SQLite (portable to Postgres), Tailwind. I ran the project locally with its seed data: the TypeScript check is clean and the public pages, calculator and all role dashboards render (dashboards were reached with the repository's documented session-token helper).
Limitations
All data is seeded demo data; organisation and vendor names are fictional examples
SQLite and local file storage for documents; production use would need a hosted database and storage
Stripe billing is optional and falls back to an offline mode; no real payments or invoices are issued
No automated test suite beyond the type check and smoke tests described in the repository
Like this project
Posted Oct 18, 2026
A marketplace for European energy and data-center construction crews: pricing engine, vendor accreditation, document vault, and invoicing on seeded demo data.
