LinkNest
LinkNest: Multi-Tenant Digital Identity & Privacy-Preserving Contact Hub
Operational Workflow & State Machine
End-to-End Pipeline- 01User creates profile and configures 1 Highlighted Super Link and up to 5 Standard Links
- 02Visitor views public profile; contact info is protected behind a structured contact request button
- 03Visitor enters name, organization, and message to request direct communication
- 04Creator receives notification in private dashboard and approves or declines the request
- 05On approval, creator can open an instant WhatsApp chat with pre-filled greeting without exposing their phone number on the web
From Single-User Utility to Multi-Tenant SaaS
rukon-link successfully protected personal contact details from web scrapers, but was hard-coded for a single user with static environment configurations. Other professionals and entrepreneurs needed the same balance of open discoverability and strict contact privacy.
LinkNest re-engineers that premise into a scalable multi-tenant platform. Every user gains an authenticated dashboard to manage their digital persona, review inbound contact requests, and monitor engagement analytics.
The 1 + 5 Link Hierarchy & Quota Control
Most link-in-bio services suffer from link sprawl: endless buttons that degrade visual hierarchy and overwhelm visitors. LinkNest enforces intentional presentation: 1 Highlighted Super Link (e.g., current flagship project, newsletter, or major release) followed by up to 5 Standard Links.
Users requiring additional links submit an in-app quota expansion request (+1 to +3 links) reviewed by administrators, preventing visual bloat and maintaining high engagement quality.
Privacy-Preserving Contact Broker & WhatsApp Bridge
Directly displaying phone numbers and personal emails invites scraping bots, phishing, and spam. LinkNest acts as a confidential contact broker: visitors submit their credentials and message intent.
Once approved by the profile owner, the platform generates a pre-formatted WhatsApp Click-to-Chat URI leveraging preset country codes (+60 for Malaysia, +880 for Bangladesh), facilitating direct professional conversations safely.
Row Level Security Architecture
Multi-tenancy is enforced natively in Supabase PostgreSQL using Row Level Security (RLS). Every table is keyed by `user_id`, and policies strictly enforce that tenants can only read and mutate their own profile links, analytics events, and contact submissions.
What's live, and what isn't
“It exists in the repository” and “it runs in production” are different claims. This is the difference, stated rather than left to be assumed.
- ImplementedMulti-tenant digital profile pagesResponsive public profiles with custom handles and theme options.
- ImplementedStrict 1 Super + 5 Standard link hierarchyClean layout constraints preventing link sprawl.
- ImplementedPrivacy-preserving contact request systemVisitors request contact; creator reviews and approves before disclosure.
- ImplementedWhatsApp preset integration (+60, +880)Deep link generator with regional country code formatting.
- ImplementedSupabase Row Level Security isolationPostgreSQL RLS policies ensuring users can only read/modify their own tenant data.
Technical stack
Frontend & UI
Data & Security
Integrations & Routing
Limitations
- Currently running on Supabase staging project; custom domain routing pending final DNS cutover.
- Custom analytics dashboard is currently basic click tracking per link.
What's next
- 01Custom domain CNAME mapping for creator personal domains
- 02QR code generator with downloadable vector SVG assets
- 03Stripe integration for automated extra link quota purchasing
Source and further reading
Finished the technical breakdown?
Return to the concise HR overview or discover other projects in the portfolio.