Branded
URL
System
Build 01
Designing an authenticated link-shortening system to explore internal link ownership, branded distribution and potential SaaS extensibility.
A prototype branded, authenticated URL shortener built on Firebase and Netlify to test link ownership and potential SaaS extensibility.
While working in a content-driven environment, social distribution relied on external URL-shortening services. Every shared link passed through third-party infrastructure, introducing several limitations:
To explore technical capabilities and internal tooling possibilities, a prototype branded URL shortener was developed. The project also served as an opportunity to validate product-thinking and backend architecture skills.
If a branded internal URL shortening system could be built:
This experiment was built to test that concept.
The system was designed to be lightweight, serverless and easily scalable using Firebase infrastructure.
The system follows a linear authentication-to-redirect pipeline with branching logic for duplicate detection.
During evaluation of the prototype, the possibility of expanding the system into a SaaS product was discussed. This highlighted potential areas of expansion:
The prototype primarily served as a proof-of-concept exploring both internal infrastructure tooling and potential productization pathways.
It is a prototype authenticated link-shortening system built on Firebase Authentication and Firestore and deployed on Netlify, created to explore internal link ownership, branded distribution and potential SaaS extensibility.
Social distribution relied on external URL-shortening services, so every shared link passed through third-party infrastructure with no branded link ownership and limited control. The prototype tested whether a branded internal system was feasible.
Users log in through Firebase Authentication and submit a long URL. The system checks Firestore for duplicates, then generates a unique short path, stores the mapping in Firestore, and redirects visitors to the stored destination when the short link is opened.
Netlify for frontend deployment, GitHub for version control, and Firebase for the backend: Firebase Auth for authentication, Firestore for the database and Firebase Storage for the storage layer.
Evaluation discussed expanding it into a SaaS product, with analytics tracking, team-level access management, branded domain integrations and campaign attribution tracking as potential areas. It remained a proof of concept.