Tannur

I have refined the story and project overview to ensure all institutional references have been purged, focusing entirely on the technical innovation and independent identity of the platform.

The Story of Tannur: Engineering an Immutable Future

Building Tannur was not just about creating another dashboard; it was about reimagining how we perceive system state and developer observability.

The Inspiration

The inspiration for Tannur stemmed from the frustration of "anonymous" infrastructure—logs that tell you what happened but never truly show you who it happened to or the path taken to get there. I wanted to move away from traditional, ephemeral logging toward an event-sourced philosophy. The goal was to build a "source of truth" that felt as fluid and high-end as a cinematic experience, drawing heavily from the minimalist, monochromatic aesthetics of Vercel.

How I Built It

Tannur is engineered as a global, multi-tenant backend-as-a-service. The technical stack was chosen for precision and scale:

• Core Architecture: An event-sourced engine designed for an immutable, global observability platform.
• Database & Auth: I utilized MongoDB for flexible user profiles and tenant metadata, while integrating Supabase for real-time capabilities.
• The Frontend: Built with a focus on high-end minimalism, using a monochromatic palette (black, white, and grey) and Geist Mono typography.
• Motion Engine: I leveraged GSAP (GreenSock Animation Platform) to create a "video-like" UI, emphasizing seamless transitions such as "Ghost Streams" and "Ink Expansions".

What I Learned

The journey taught me the profound difference between "State" and "History." In an event-sourced system, the state at time $T$ is simply the fold of all events $e$ from the beginning of time: $$State(T) = \sum_{i=0}^{T} e_i$$ I learned to manage complex multi-tenancy by baking Tenant IDs into the architecture, ensuring rigorous data isolation across the platform. I also mastered the art of "Cinematic UI"—learning that motion isn't just decoration; it’s a functional tool to guide user focus through high-pressure debugging environments.

Challenges Faced

• Latency vs. Aesthetics: Maintaining real-time ingestion while running complex GSAP animations required significant optimization of the dashboard logic.
• Identity Mapping: Bridging the gap between raw technical events and human identities—the "Line of Life"—meant creating a resolution layer that could handle environment fingerprinting.
• Establishing Independence: A key strategic decision was the total removal of all institutional or faculty-led references to establish Tannur as a purely independent, global enterprise.

Tannur stands today as a testament to the belief that infrastructure should be as beautiful as it is auditable.

Built With

• database
• express.js
• mongodb
• node.js
• react
• react-native
• typescript