1

proxylit — Proxy Infrastructure Site

A search-led product site for a six-line proxy network — a pricing calculator modelled per product line, per-country and per-integration coverage pages, a version-controlled content pipeline, and a documented design process where every significant change was specified before it was built.

GitHubWebsite

Technology Stack

React 18, TypeScript, Vite 6, Tailwind CSS 3.4, React Router 6, Radix UI, class-variance-authority, HugeIcons, react-markdown, remark-gfm, react-syntax-highlighter, ESLint, Prettier, Vercel

Overview

Duration: 3/2026 - 6/2026

proxylit sells proxy infrastructure — datacenter, residential, unlimited residential, ISP, IPv6, and mobile — to people who scrape, verify ads, monitor prices, and run anti-detect browsers. That buyer arrives already knowing what a sticky session is, comparing three providers in three tabs, and looking for two numbers: coverage and price per gigabyte.

So this is not a single-page pitch. It is a wide site built for organic search and for side-by-side comparison: a page per product, a matching page per price list, a page per use case, a page per country, and a page per supported anti-detect browser. The entire build is static with no backend — every number on the site is version-controlled data in the repository, which means a price change is a reviewed commit rather than a CMS edit nobody can audit.

Site Structure

Six route families:

The product-and-pricing pairing is the shape that matters: a visitor comparing providers wants the capability page and the price page to be different URLs they can hold open side by side.

Pricing Calculators

Pricing is the reason someone is on the site, so it carries the most logic — five calculator components, one per product line that needs one, plus a structured price list for datacenter.

Each calculator models its own product rather than sharing a generic abstraction, because the units genuinely differ: residential sells by the gigabyte, IPv6 by the subnet, mobile by the port. What they share is the shape — a typed plan describing included bandwidth, price per gigabyte, checkout price against list price, and which tier to highlight, tiered into regular and enterprise. The plan tables are data, so a price change is an edit to a constant rather than a rewrite of a component.

Each calculator also carries its own included-features table — IP pool size, authorisation method, targeting granularity, rotation interval, thread limits — so the comparison a buyer needs sits beside the number instead of a page away.

Content Pipeline

The blog is version-controlled markdown rendered with full GitHub-flavoured syntax and proper code highlighting. The posts are integration guides for anti-detect browsers, which is precisely the long-tail search traffic this category lives on.

Keeping posts as committed markdown rather than introducing a CMS means the content ships and versions with the code — the right call for a site whose blog is documentation rather than news, and one less system for the client to pay for and administer.

A Documented Design Process

The most distinctive thing about this project is what sits beside the source: a dated specification and an implementation plan for every significant piece of design work, committed alongside the code it produced.

Two things make this worth pointing at. First, decisions stay legible: the superseded specification and the one that replaced it both remain in the repository, so six months later anyone can read why the direction changed instead of finding an unexplained diff. Second, it front-loads the disagreement — the argument about a direction happens against a written spec, before it costs a build.

Alongside those, a committed design reference documents the full brand colour scale with the intended use of each swatch, button variants, typography, shadows, and animation rules; and a conventions document records the repository's own standards. That is what keeps a fast-moving build maintainable: the tokens, the conventions, and the reasoning live in the repository rather than in someone's memory.

Design System

This is the widest surface of the set — six product lines, six use cases, per-country and per-browser pages — and the engineering that matters is in refusing to let that become unmaintainable: pricing as data, brand as a module, assets behind one helper, and design decisions written down before they were built.