
node-http-proxy
Serve
Haproxy
Traefik
MAMP
Envoy
DigitalOcean
Vercel
Tempreon
ChainMemory
Memori
Mem0
Agentmemory
TheSecondBrain.dev
cognee
VATES.jp
Tempreon is a personal memory layer for your AI tools, connected over MCP. Your knowledge, preferences, and decisions travel across Claude, ChatGPT, Cursor, and any MCP-capable client — captured once, available everywhere. It learns how you actually work instead of just storing what you said.
node-http-proxy
TempreonNo features have been listed yet.
Tempreon's answer:
Tempreon started with a simple observation: AI models keep changing, but the thing that makes them useful to you — your context, your preferences, your judgment — gets rebuilt from scratch inside every tool, and lost every time you move.
We built the layer that fixes that: person-owned memory served over the open Model Context Protocol, so it works across assistants instead of belonging to one. Along the way we open-sourced the pieces that are useful to everyone regardless of whether they use Tempreon — like memhaul, our MIT-licensed CLI for turning ChatGPT and Claude data exports into files you own.
The through-line is custody: the model is temporary, your memory shouldn't be.
Tempreon's answer:
Most alternatives in this space are memory infrastructure for developers building their own AI apps. If you're the person using several AI tools every day, that's not your problem — your problem is re-explaining yourself to each of them and losing everything when you switch.
The choice is really about who the memory is for. Ours is for you.
Tempreon's answer:
Tempreon is built for the person, not the app. Most memory products are developer APIs for adding memory to a single product; Tempreon is a memory layer you own that travels with you across every AI tool you use — Claude, ChatGPT, Cursor, anything MCP-capable.
Tempreon's answer:
Individuals who live in AI tools all day: operators, consultants, founders, sales professionals, and knowledge workers who use more than one assistant and are tired of being a stranger to each of them.
If you've ever pasted the same context into Claude and ChatGPT in the same week — you're the audience.
Tempreon's answer:
The protocol choice is the product decision: build on the open standard, and your memory works everywhere the standard does.
Based on our record, node-http-proxy seems to be more popular. It has been mentiond 10 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper. Source: over 3 years ago
I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds... Source: about 4 years ago
What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward. Source: about 4 years ago
There's several ways to have a blog path contain a separate setup from the marketing/product routes. One is to run a reverse proxy on the root domain to pull in separate routes for various services. https://github.com/http-party/node-http-proxy You can do rewrites at the server level for the root domain Or if the app on the root domain can do the routing for you (have done this before with a Rails app). - Source: Hacker News / over 4 years ago
Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response. - Source: dev.to / over 4 years ago
Serve - Postmate's autonomous delivery vehicle
ChainMemory - Portable, verifiable memory for AI agents — works across ChatGPT, Claude, Gemini and any MCP client
Haproxy - Reliable, High Performance TCP/HTTP Load Balancer
Memori - Persistent memory from agent trace, not just conversation
Traefik - Load Balancer / Reverse Proxy
Mem0 - Your private, local memory layer for all AI tools