How Kompi was
built.

A short link looks simple from the outside. A production link platform is not. It has to create and manage destinations, redirect quickly, preserve campaign context, record useful events, separate data between workspaces, protect authenticated areas and turn activity into something a person can actually understand.

Kompi was built around that broader product problem. Links are one layer; the application also connects KR Codes, K-Cards, analytics, QR experiences and workspace-level tools.

The current Kompi codebase is a custom Next.js 16 application running React 19. TypeScript and the Next.js App Router handle the public marketing site, authenticated product routes and API endpoints, while PostgreSQL and Prisma provide the persistent application layer.

Kompi's main product objects share a workspace model. A workspace can own links, bio pages, KR codes, forms, subscriber lists, engagement events and additional tools. The account is the centre of the product instead of each feature living in its own silo.

The schema also models K-Cards, QR menus, contact submissions, courses, loyalty activity, builder sites and Kompi Chat. Features can expand without having to reinvent authentication, ownership or account structure every time.

Each Kompi link stores its destination, short code, status, workspace relationship and aggregate click count. Individual click events can capture UTM source, medium, campaign, content and term, plus referrer and geographic context.

Public redirects are handled differently from protected dashboard traffic. At the edge, Kompi can read Vercel-provided country, region and city headers and pass that context into the redirect request. The result is infrastructure designed for measurement as well as speed.

Kompi's QR functionality is not a separate image generator bolted onto a website. KR Code records can hold a destination, style information and workspace ownership. K-Cards have public slugs and structured data, while click and message events can be associated back to the relevant card or workspace.

A physical scan, a digital profile card and a short link can all return to the same account, analytics and growth workflow.

Kompi has a substantial public content layer: product pages, customer pages, free tools, QR guides and a structured blog. The same Next.js application therefore serves two jobs — a crawlable public website and a protected SaaS dashboard.

Public pages use canonical metadata, index/follow directives and structured data where appropriate, while the sitemap covers core routes, tools and programmatic SEO pages. Product and acquisition work can share the same components and deployment pipeline.