All projects

Leve

SaaS · Routine and wellbeing

A mobile-first experience for logging routines, recognizing patterns and sharing information with a professional, with permission.

Visit product
Leve public introduction pageCapture of the public page

The problem

Logging routines is useful when the information comes back in an understandable form. Leve combines a diary, planning and professional follow-up, with attention to access control for personal data.

My contribution

Development of a SaaS product using Next.js and NestJS in a monorepo, with a shared design system and typed API client. The separation between personal use and professional follow-up guides the implementation.

What the system does

  • Routine diary and wellbeing logs.
  • Planning and shopping lists.
  • Professional follow-up authorized by category and date range.
  • Revocable permissions and private notes.

Engineering decisions

Sharing by choice.

Professional follow-up requires consent and defines authorized categories and dates. Professionals cannot edit the diary; private notes are never shared.

Contracts between layers.

The frontend communicates with the NestJS API through a typed client. UI, configuration and HTTP access live in shared packages.

Explicit scope.

Documentation keeps AI and billing disabled. The product prioritizes routine workflows and the boundaries of professional follow-up.

Architecture in perspective

Leve

  1. Next.js / Shared UI
  2. NestJS / Typed API client
  3. Prisma / PostgreSQL
  4. Supabase Auth / Consent

Architecture overview

Technical overview based on the reviewed source. No customer data is shown.

Context and boundaries

Private repository and published application. The public page is shown without accessing personal records. This portfolio does not describe the product as a diagnostic tool or a system with active AI.

Discuss this project

Next project

Dr. Alfredo Castro