HTTP forward and reverse proxy with a pluggable tower middleware pipeline
Security proxy for MCP (Model Context Protocol) — auth, rate limiting, payload filtering, and audit logging between AI agents and MCP servers
Fetch package updates directly from the source.
Reverse proxy and load balancer for the Antelope SHiP (State History Plugin) WebSocket protocol.
Transparent proxy with upstream HTTP CONNECT and SOCKS5 proxy support (macOS pf, Linux nftables)
MCP Gateway
Link.Assistant.Router — Claude MAX OAuth proxy and token gateway for Anthropic APIs
MCP Gateway — proxy tools, resources, and prompts from upstream MCP servers
Jokoway is a high-performance API Gateway built on Pingora (Rust) with dead-simple YAML configs.
High-performance Anthropic API proxy to OpenAI-compatible endpoints
Upstream for pingap
OCI registry pull-through cache
Add `upstream` remote-tracking branch to your forked repository by tracking GitHub.
Trout allows you to maintain a base version of special files (like Gemfile) in one repository, and then syncronize just that file with several other repositories. This means that you can update your Gemfile in the master repository, and then get the latest of all the common gems that you use in each project just by running "trout update Gemfile".
A Ruby gem to generate .conf files with upstreams to include in your nginx.conf. It uses your Thin config files: ./*/thin.yml, ./*/config/thin.yml
Parse the output of the Nginx Upstream Check plugin
upstreamwatchr makes it easy to keep track of changes in the upstream repositories of your forks by comparing two git remotes and creating an issue on your fork if it is out of sync.
Multicast upstream data to websocket clients
Middleware that injects upstream server info into the response
Automatically fetch from upstream every hour.
uh ok so roast beef is some kind of package manager that is for bleeding-edge programs. so basically it does not have its own repositories. instead it just will download source from the upstream repository and will do all the necessary steps to install . you get things that are as fresh as possible. i am talking about really fresh like your eggs and milk. roast beef saves you from having to look up the repository locations for all the stuff you want to build from source. it also abstracts away the differences in build processes. say you want the latest version of such a package as gnu emacs. so you grab the source but you know emacs is a little different from other packages and requires "make bootstrap" in between the configure and make step. with roastbeef all the complexity of such things is hidden from you. and if you have a lot of stuff built from source you can keep them all up to date with a single command. the motivations behind this are made more clear in a blog post: http://technomancy.us/106 == man why you even got to do a thing
Help to sync fork from upstream by extending git command
Super simple job queue over AMQP
Upstream pull request: https://github.com/amatsuda/kaminari/pull/636