Workflow-heavy Rental SaaS

SKACE Rent

A rental workflow platform with public catalog browsing, admin operations, customer portal access, payment-proof uploads, and reminder-driven rental lifecycle handling.

Next.jsPrismaPostgreSQLNextAuthTailwind CSSBlob uploads

Route surfaces19 audited

Auth modelAdmin + Customer

ValidationBuild passed

File handlingBlob-backed proofs

Back to case studies Open resume

Role focus

Business workflow design, admin tooling, customer portal implementation

Production buildAutomated tests

Project narrative

SKACE Rent is a strong example of software engineering that understands process. The interesting part is not just listing appliances, but how requests, provisioning, payments, proofs, reminders, and portal status all connect into one operational flow.

Why it matters

Strong workflow and business-logic signal

Good evidence of protected full-stack product work

Useful for SaaS, platform, or operations-tooling roles

Preview Gallery

Visuals that make the project story land faster.

Interface views and system visuals that help the product story read quickly. Tap any screenshot to view it full size.

Interface view covering the public catalog, admin queue, and customer payment portal.

Architecture overview showing public flows, auth, Prisma models, uploads, and reminders.

Architecture map

Frontend

The product includes a public catalog, admin inventory and payment views, and a customer portal for rental tracking and proof submission.

Backend

App Router endpoints handle uploads, rental requests, admin review, payment-proof processing, auth, and cron-style reminder workflows.

Data and auth

The Prisma schema models appliances, requests, agreements, payments, reminders, and user roles in a way that matches the operational journey closely.

Architecture overview highlighting how the frontend, backend, and data flow connect.

Engineering Decisions

This is where the software engineering depth shows up.

Beyond features, this section highlights the structural choices that shape scalability, reliability, and product clarity.

Treated payment-proof review as a first-class workflow instead of a side note.

Kept the admin and customer experiences separate so the product can serve both operations and trust.

Modeled reminders and due dates in the backend, which helps the app feel operationally real.

Validation snapshot

Production build

The Next.js production build passed during the audit.

Automated tests

No automated tests were detected in the repository.