# Resinat/Resin

A high-performance proxy pool gateway. Turn massive proxy subscriptions into a stable, smart, and observable network with sticky sessions.

Repository: https://github.com/Resinat/Resin
Canonical: https://ross.abutalabs.com/products/resin
Language: Go
License: MIT
License Family: permissive
Topics: proxy, proxypool
Last push: 2026-08-01T16:52:42+00:00

## Health v2 (maintenance only)
Score: 79/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 95, release rhythm 95, longevity 13
- inputs: {"age_days": 186, "days_push": 32, "days_rel": 32, "gap_med": 1.5, "n_releases_24m": 15}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2224, forks 362 (observed 2026-08-28T04:06:27.974899+00:00)

## What it is
Resin is a high-performance proxy pool gateway written in Go that aggregates massive numbers of proxy nodes into a unified, observable proxy entrypoint. It provides smart scheduling with health checks and circuit breaking, sticky sessions bound to stable outbound IPs, and HTTP, SOCKS5, and reverse proxy access modes with a Web UI.

## Use cases
- aggregate thousands of proxy subscriptions into one stable proxy endpoint
- keep a business account pinned to the same outbound IP with sticky sessions
- automatically remove failing proxy nodes via health checks and circuit breaking
- serve HTTP and SOCKS5 forward proxy plus URL-based reverse proxy from one gateway
- monitor proxy pool health, latency, and request logs through a web dashboard
- route scraping or automation traffic through a resilient rotating proxy pool

## When to choose
- you operate large numbers of proxy nodes or subscriptions and need a single stable entrypoint
- you need session stickiness with automatic failover to nodes sharing the same outbound IP
- you want built-in observability, metrics, and a Web UI for your proxy infrastructure
- you need multiple proxy protocols (HTTP, SOCKS5, reverse proxy) behind one gateway

## When to avoid
- you just need a simple single upstream proxy without pool management
- you need a client-side VPN or full traffic encryption solution rather than a proxy gateway
- you want a managed cloud proxy service instead of self-hosting

## Facets
- artifact type: service
- maturity: active
- function: proxy, monitoring, logging, web-framework
- domain: networking, security, self-hosted, developer-tools
- platform: windows, self-hosted, go
- tags: proxy-pool, proxy-gateway, sticky-sessions, socks5, http-proxy, reverse-proxy, circuit-breaking, health-checks, web-ui, load-balancing, linux, macos, docker

## Member repositories
- Resinat/Resin (main) score 79

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:27.974899+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:44:57.089743+00:00, confidence not recorded.
  - readme: https://github.com/Resinat/Resin (fetched 2026-08-28T04:06:27.974899+00:00, sha 66738bbac1ac)
- Data as of 2026-08-30T08:39:29.467469+00:00.