# eolinker/apinto

基于golang开发的网关。具有各种插件，可以自行扩展，即插即用。此外，它可以快速帮助企业管理API服务，提高API服务的稳定性和安全性。

Repository: https://github.com/eolinker/apinto
Canonical: https://ross.abutalabs.com/products/apinto
Homepage: https://www.apinto.com
Language: Go
License: Apache-2.0
License Family: permissive
Topics: gateway, api, api-gateway, microservice, goku, middleware, servicemesh, proxy, apigateway, plugin, golang, go, router, loadbalancer, apinto, dubbo2, grpc
Last push: 2026-07-30T15:33:54+00:00

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

## Adoption (not part of the score)
Stars 1676, forks 258 (observed 2026-08-28T04:05:20.617583+00:00)

## What it is
Apinto is a high-performance, cloud-native API gateway written in Go with a modular, pluggable architecture. It handles dynamic routing, load balancing, service discovery, authentication, rate limiting, and monitoring for microservice traffic, and runs on Kubernetes or any cloud platform.

## Use cases
- manage and secure api traffic for microservices
- self-hosted open source api gateway
- dynamic routing and load balancing for backend services
- authenticate and rate-limit api consumers with jwt or api keys
- service discovery with eureka nacos or consul
- run an api gateway on kubernetes
- plugin-based gateway for grpc and dubbo traffic

## When to choose
- you need a self-hosted, extensible API gateway in front of microservices
- you want built-in auth, rate limiting, circuit breaking, and monitoring without extra tooling
- you run mixed workloads including HTTP, gRPC, and Dubbo
- you need cluster management and dynamic scaling of gateway nodes

## When to avoid
- you only need a simple static reverse proxy like nginx
- you prefer a fully managed cloud API gateway service
- you need a gateway with a large third-party plugin marketplace like Kong's ecosystem

## Facets
- artifact type: service
- maturity: active
- function: api-gateway, proxy, middleware, routing, load-testing, auth, rate-limiting, monitoring, plugin-system, http-server
- domain: microservices, apis, backend, cloud-computing, self-hosted
- platform: go, self-hosted, cloud
- tags: api-gateway, reverse-proxy, service-discovery, grpc, dubbo, load-balancing, circuit-breaker, cloud-native, extensible-plugins, devops, linux, docker, kubernetes

## Member repositories
- eolinker/apinto (main) score 86

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:20.617583+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-30T03:42:25.987162+00:00, confidence not recorded.
  - readme: https://github.com/eolinker/apinto (fetched 2026-08-28T04:05:20.617583+00:00, sha cda8c4b10611)
- Data as of 2026-08-30T08:39:29.467469+00:00.