Building the Admin System for My Portfolio

By Neel Vora

This post walks through how I built admin System, and where it fits in the rest of my work.

My portfolio has become a real product with analytics, logging, RAG documents, and shop activity. To manage all of this, I needed a simple admin layer.

Authentication

I used Supabase magic link authentication. It gives me secure passwordless login with minimal setup.

The admin system supports:

• Admin users table
• Active sessions table
• Server side verification
• Route guards

AdminGuard

Every admin page uses a small guard component that checks for a valid session token stored in cookies.

If the user is not authenticated, they are redirected to a login screen.

Admin routes

The admin panel includes pages for:

• Analytics events
• Feature flags
• Logs
• RAG documents
• Health checks

Each one hits a server route and renders structured tables.

Background

It lets me treat my portfolio like a monitored application instead of a static website.

• Session management
• Protected routes
• Supabase integration
• Operational thinking

Keep exploring

From here you can:

• Visit /neel-vora for more background about me and my work.
• Browse more posts on the blog.