Build your proxy

Answer the questions and download a project that already works. Every choice maps to real files in the output, nothing is scaffolding you have to fill in later.

Prefer the terminal? node builder/cli.js --out ./my-proxy --preset standard

Choices that cannot work with what you have already picked are greyed out, with the reason on hover.

Start from a preset

Or answer them yourself

Project name

Language

TypeScript Types on the engine adapter and every feature module. Needs a bundler, because the browser cannot run .ts directly. JavaScript The same code with the types erased. Pair with no build step to edit files and just refresh.

Package manager

npm Ships with Node. pnpm Faster, hard-links its store. yarn Still common in older projects. bun Fastest install of the four.

Runtime

Node Node 20 or newer. TypeScript on the server runs through tsx. Bun Runs the TypeScript server with no loader. Only Express is reliable here; see the note in this file.

Server framework

Express The community default. Every proxy guide assumes it. Fastify Faster and stricter. What most large proxy sites run. Node only.

Frontend

Vanilla Plain DOM calls. Nothing between you and the engine. The best one to read first. React A React-rendered shell around the same engine adapter. Vite mounts the proxy controller after React commits the shell. Astro + Preact A static Astro page with a hydrated Preact proxy island. Astro builds the page; Preact owns the interactive shell.

Build step

No build step Plain files in public/, served as-is. JavaScript and plain CSS only. Vite Dev server with reload, bundled production build. Required for TypeScript, SCSS, Tailwind, React or Astro.

Styling

Plain CSS No tooling. SCSS Nesting and variables. Tailwind Utility classes. With no build step it loads from the Tailwind CDN instead.

Transports

libcurl curl in WebAssembly, over wisp. Widest site compatibility. Read the guide → epoxy A Rust TLS stack in WebAssembly, over wisp. Smaller than libcurl. Read the guide → bare Plain HTTP to a Bare server. Works without WebSockets. The only transport that runs on request/response serverless hosts. Your server can inspect target request and response data, and WebSocket sites will not work. Read the guide →

Features

Browser controls Back, forward and reload, wired to the frame's own history. Read the guide → Multiple tabs One proxy session per tab, kept alive in the background. Read the guide → Settings Validated, persisted settings. Search engine, home page. Read the guide → Transport switching Pick libcurl, epoxy or bare at runtime, or point at another wisp server. Read the guide → History A persisted visit log, separate from per-tab back and forward. Read the guide → Bookmarks A saved list, using the same storage layer as settings. Read the guide → Cloaking about:blank, blob, and title/icon presets, each toggleable. Read the guide → Quiet service worker Silence log, info and debug inside the worker. Warnings and errors stay. Read the guide → Custom protocols Internal pages on your own scheme, e.g. proxy://settings. Read the guide →

Build your proxy

Start from a preset

Or answer them yourself

Result