Skip to content
KZ

02System

Trippp

One platform. Many tenants. Four interfaces shaped by responsibility.

Trippp is not one dashboard stretched across different users. Platform control, agency operations, trip execution and the traveler experience each get a surface built for the decisions that happen there.

Trippp Super Admin dashboard

Platform layer

Super Admin

Multi-tenant control plane

Role
Solo Software Engineer / Product Builder
Type
Multi-tenant product
Interfaces
4
Traveler
Mobile web

The problem

Complexity changes with responsibility.

Trippp is a multi-tenant travel platform, not a single dashboard. A platform-level Super Admin manages agencies; each tenant gets its own operations layer; Trip Managers run individual trips; travelers get a focused mobile web experience.

Architecture

Control → Operate → Manage → Experience

01

Super Admin

Platform

02

Tenant Admin

Agency

03

Trip Manager

Trip

04

Traveler

Mobile web

The Next.js 15 App Router frontend connects through tRPC v11 and Next.js API routes to PostgreSQL via Drizzle ORM. Supabase handles auth and storage; Redis, background jobs, email and monitoring support the operational layers.

01

Super Admin

Control the platform

The platform layer manages agencies and gives the operator a view across the multi-tenant system.

Trippp Super Admin agencies view

02

Tenant Admin

Operate an agency

Each tenant gets an operational surface for its own trips, people and day-to-day work.

Trippp Tenant Admin dashboard

03

Trip Manager

Run the trip

Trip Managers work closer to execution: program, documents and the information needed to keep a trip moving.

Trippp Trip Manager dashboard

04 / Traveler

The system gets quieter at the edge.

The traveler does not need an operations dashboard. The mobile web layer keeps the program and services close, while the complexity stays behind the scenes.

Trippp traveler home
Trippp traveler program
Trippp traveler services

Principle

One platform. Four layers.

One connected multi-tenant product model underneath four layers: Super Admin, Tenant Admin, Trip Manager and Traveler.

Approach

I built Trippp from scratch by myself, starting only from a brief. That meant shaping the product model, the four role-specific interfaces, the backend contracts, authentication, storage, jobs, email, monitoring and deployment as one connected system.

Experience

Desktop operational tools for the people running the platform and the trips, then a deliberately lighter mobile web app for the person actually traveling.

Reflection

Simple is not fewer features. It is knowing which one the person in front of the screen needs right now.

Explore the product

Open Trippp