An open-source reverse proxy that authenticates users
auth-proxy is a minimal HTTP reverse proxy that shows login pages on protected pages, and passes user information in headers. My goal was to build something that’s as flexible as possible and can add auth to any existing infrastructure. It’s pretty straightforward to use, after setting up Stack Auth (which this is based on) you can use the Docker container to proxy port 3000 to 3001: docker run -it \ -e NEXT_PUBLIC_STACK_PROJECT_ID= \ -e NEXT_PUBLIC_STACK_PUBLISHABLE_CLIENT_KEY= \ -e STACK_SECRET_SERVER_KEY= \ -e SERVER_PORT=3000 \ -e PROXY_PORT=3001 \ -p 3001:3001 \…
In plain words
Auth-proxy is an open-source HTTP reverse proxy that adds authentication to existing applications. It displays login pages for protected resources and forwards user information via headers to upstream services. Built on Stack Auth, it runs as a Docker container and integrates with any HTTP infrastructure, making it suitable for developers who need to add authentication to legacy or existing systems without modifying the underlying application code.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
auth-proxy is a minimal HTTP reverse proxy that shows login pages on protected pages, and passes user information in headers. My goal was to build something that’s as flexible as possible and can add auth to any existing infrastructure. It’s pretty straightforward to use, after setting up Stack Auth (which this is based on) you can use the Docker container to proxy port 3000 to 3001: docker run -it \ -e NEXT_PUBLIC_STACK_PROJECT_ID=<project-id> \ -e NEXT_PUBLIC_STACK_PUBLISHABLE_CLIENT_KEY=<client-key> \ -e STACK_SECRET_SERVER_KEY=<server-key> \ -e SERVER_PORT=3000 \ -e PROXY_PORT=3001 \ -p 3001:3001 \ stackauth/auth-proxy:latest <protected-page-patterns> If you now go to http://localhost:3001/handler/sign-in, you will see a log-in page. Once you’re authenticated, every request to your HTTP server will have the following extra headers: - x-stack-authenticated ("true" if authenticated; not present otherwise) - x-stack-user-id - x-stack-user-primary-email - x-stack-user-display-name If you’re building an SPA or client-side app, you can also fetch the current authentication status on /handler/me: { "user": { "id": "...", "primary_email": "[email protected]", "display_name": "John Doe" }, "authenticated": true } This is all still pretty hacky, but I’d love to hear your feedback. Any cool ideas on what to build? PS: Big props to fellow HN user rudasn who brought it up first, and who gave us plenty of ideas after another Hacker News thread: https://news.ycombinator.com/item?id=41195470
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
Launched alongside, October 2024
the whole month →
Softr for Notion▲925Turn Notion databases into portals & apps with no code
Dev tools · 2024 · softr.io
One inbox for all your work discussions
Work · 2024 · generalcollaboration.com