Nest

Stack

Business context

1. 01

   Nest is not a one-off dashboard. It is a serious internal enterprise platform that a 300+ person company uses to run day-to-day operations.

2. 02

   The project began in February 2025 and is still not finished because the platform keeps growing with the business and new internal needs.

3. 03

   Its role inside the company has expanded from a product initiative into a central system that more and more teams depend on.

Operational scope

1. 01

   Core workflows include fleet management, desk reservation, parking reservation, asset management, asset history, analytics, and accounting-related processes.

2. 02

   The platform supports practical internal operations rather than isolated features, which means reliability, clarity, and workflow fit matter as much as the code itself.

3. 03

   It keeps evolving as a platform a complete company can run on, instead of staying limited to a small set of administrative tools.

Technical delivery

1. 01

   Built with Next.js, React, TypeScript, tRPC, Prisma, MariaDB, Playwright, Vitest, Slack integration, and AWS S3.

2. 02

   The work spans frontend product development, backend business logic, data modeling, integrations, testing, and production-oriented refinement.

3. 03

   Type-safe API design with tRPC and a tested delivery flow with Playwright and Vitest helped keep a large internal tool maintainable as it expanded.

Why it matters

1. 01

   Nest shows that I can build more than a polished interface. It shows I can help shape a living product that supports real operational complexity.

2. 02

   It is one of the clearest examples of my full-stack work in a business-critical environment where the platform is actively used and keeps growing over time.