Case studies

Pocketlink: Creator Infrastructure, Commerce & AI

Co-founder. I built a single page where creators publish, sell and grow, and owned the editor, domains, commerce, AI tools and infrastructure.

24,000+
users
reached at product scale
30+
analytics signals
behavior + heatmaps
14 mo
to 24,000+ users
confirmed scale window
3
clicks to checkout
lower-friction funnel

[1] Product

Product problem & ownership

One creator-owned page for publishing, selling, analytics and brand work.

Platform system landscape

The dashboard splits into four product areas, then comes back together on the public creator page.

Product goals

Goal 01Position creators effectivelyA customizable page gives creators more than a fixed list of links.
Goal 02Help creators monetizeProducts, subscriptions, digital downloads, checkout and brand deals all live in one product.
Goal 03Operational intelligenceAnalytics, heatmaps, AI business analysis and automated collaboration management turn page activity into decisions.

Ownership ledger

AreaDetailOwnership
Bento editor + page/card modelResponsive desktop/mobile compositionBuilt
Nested cards / nested pagesDeeper creator content pathsBuilt
Cloudflare domain + SSL lifecycle15-second status polling · TLS 1.2+Engineered
Creator commerceProducts · inventory · checkout · ordersBuilt
Autosave + undo/redo2.5 s save cadence · 10 snapshotsBuilt
Multi-tenant public routingPocketlink subdomains + custom domainsEngineered
Analytics + heatmaps30+ visitor/behavior signalsBuilt
AI, email + platform integrationsBI agent · manager · campaigns · infraBuilt

My role

I co-founded it and owned product and engineering: the editor and page architecture, multi-tenancy and domains, commerce, analytics, AI tools, email, integrations, deployment and infrastructure.

Product surface

Creator destinationPublishingProfile · bento editor · themes · nested pages.
Commerce + subscriptionsMonetizationProducts · checkout · gated downloads.
Behavior + AIIntelligenceAnalytics · heatmaps · Gemini BI agent.
Creator business toolingOperationsEmail · social · domains · integrations.

[2] Editor

Editor & publishing architecture

A responsive bento layout with saved page state, autosave, nested pages and hybrid public rendering.

2 → 12
grid mapping
mobile columns → desktop
2.5 s
autosave cadence
save window
10
history snapshots
bounded undo/redo

Editor state & persistence

Desktop and mobile layouts branch from shared React state and merge back into the saved page.

Autosave flow

State & delivery

AutosaveSave without a publish stepCreator action → React state → unsaved → 2.5-second save window → Supabase update → saved state.
Undo / redoBounded snapshot historyEdits are grouped on a 250 ms timer, with up to 10 desktop and mobile snapshots. A new edit after undo clears the redo history.
Public renderingHybrid server + client pathThe server resolves tenant data, metadata and profile. The client then hydrates the responsive grid and interactions.

The public page reads the saved configuration directly, so edits show up with no separate publish step.

[3] Domains & commerce

Multi-tenancy, domains & commerce

Hostname-based routing, Cloudflare domain handling and a three-click purchase.

15 s
domain / SSL polling
provider status cadence
TLS 1.2+
minimum enforced
TLS 1.3 supported
3
clicks to checkout
reduced purchase friction

Custom domain + tenant routing

Cloudflare handles hostnames and SSL. Next.js maps each active hostname to the right creator.

Commerce path

Commerce covers products, inventory, discounts, cart, checkout, shipping, payments, orders, reviews, subscriptions and gated downloads.

[4] Analytics & AI

Analytics, AI & audience operations

Behavior tracking, creator insights, collaboration management and audience workflows.

Behavioral analytics pipeline

Visitor events become behavior signals and heatmap batches, which feed the creator's analytics.

AI operations

Gemini 2.5 FlashCreator business intelligenceCreators ask questions in plain language about sales, inventory, product movement, churn and conversion, and get predicted stock estimates.
AI Creator ManagerBrand collaboration operationsIt judges creator-product fit and risks, negotiates terms and moves opportunities to an agreed deal.

Audience operations

Audience communicationEmail marketingContact lists, templates, drafts, personalization, instant and scheduled sends, unsubscribe handling, Gmail API and Nodemailer delivery, and queued sends.
Creator-facing dataIntegrationsYouTube · Instagram · Facebook · Gmail · Maps · image, product and OG-image tools.
Layout assistanceAI page toolingGeneration · onboarding generation · optimization · builder workflows.

[5] Delivery & results

Delivery, results & engineering lessons

Infrastructure, scale, architecture decisions and lessons from a platform with 24,000+ users.

SystemConfirmed resultFraming
Product scale24,000+ users in 14 monthsConfirmed headline fact
Creator analytics30+ visitor / behavior signalsIncludes heatmaps
Custom domains15-second domain / SSL pollingTLS 1.2+ enforced
CommerceThree-click checkout pathLower-friction checkout path

Delivery path

From a push to the repo to a replicated Next.js app on AWS EKS.

Architecture decisions

Editor modelSeparate responsive arrays2-column mobile → 12-column desktop synchronization.
TenancyHost-based public routingOne shared route tree for Pocketlink and custom domains.
Integration boundaryBrowser + route-handler splitCore state goes straight to Supabase. Server routes handle providers, secrets and orchestration.
Public renderingHybrid server / client modelServer tenant + metadata; client interactive grid and cards.

Engineering lessons

01
Composable page model.

Card-oriented schema across publishing and commerce.

02
Domains as product infrastructure.

Tenant routing, DNS, and SSL lifecycle.

03
Intelligence near operations.

Analytics, commerce context, and AI action.

Want to talk about any of this?

Happy to go deeper on the editor, multi-tenant routing, or commerce.

© 2026 Tharun Pranav SakthivelHome