3 ms·

Show HN: Signed URLs Gateway – The Missing Infra Piece for Building Modern Apps

6 points by GabrielMusat 3y ago

GabrielMusat 3y ago
Hi HN community, I'm excited to share my latest Open Source project, Signway – a proxy server designed to simplify and secure the process of re-streaming API responses in serverless and traditional architectures. The core idea behind Signway is to enable frontend applications to request third-party APIs "directly" through short-lived signed URLs, created synchronously by the backend. This approach not only enhances security by preventing credential leaks but also optimizes serverless setups where streaming responses can be a challenge. Signway is built for high throughput and is written in Rust, ensuring performance and efficiency. It's particularly useful for scenarios where you need to stream large amounts of data or leverage Server-Sent Events (SSE), but find traditional methods cumbersome or expensive. We've developed SDKs for Python, JavaScript, and Ruby to easily integrate Signway into your workflow. I believe this tool can be a game-changer for many developers dealing with API integrations, and I'm keen to hear your thoughts, feedback, or any questions you might have! Check out the GitHub repo for more details and examples: https://github.com/gabotechs/signway https://github.com/gabotechs/signway. Looking forward to your insights and discussions!
- quickthrower2 3y ago
  It is a clever idea. It makes it easier to put together “JAMStack” type solutions where the browser orchestrates everything and this solves the trust problem. OpenAI and chatbots are a good example. Although I would want a proxy to keep track of usage too in that scenario.
  - GabrielMusat 3y ago
    That's a good observation! people that have tried Signway for the OpenAI use case tend to care a lot about tracking usage. The OSS version uses structured logging for reporting usage (just measured by bytes in/out), which can be good enough for some scenarios, but definitely something worth keeping track of.

6 points by GabrielMusat 3y ago

Hi HN community, I'm excited to share my latest Open Source project, Signway – a proxy server designed to simplify and secure the process of re-streaming API responses in serverless and traditional architectures. The core idea behind Signway is to enable frontend applications to request third-party APIs "directly" through short-lived signed URLs, created synchronously by the backend. This approach not only enhances security by preventing credential leaks but also optimizes serverless setups where streaming responses can be a challenge. Signway is built for high throughput and is written in Rust, ensuring performance and efficiency. It's particularly useful for scenarios where you need to stream large amounts of data or leverage Server-Sent Events (SSE), but find traditional methods cumbersome or expensive. We've developed SDKs for Python, JavaScript, and Ruby to easily integrate Signway into your workflow. I believe this tool can be a game-changer for many developers dealing with API integrations, and I'm keen to hear your thoughts, feedback, or any questions you might have! Check out the GitHub repo for more details and examples: https://github.com/gabotechs/signway https://github.com/gabotechs/signway. Looking forward to your insights and discussions!

quickthrower2 3y ago
It is a clever idea. It makes it easier to put together “JAMStack” type solutions where the browser orchestrates everything and this solves the trust problem. OpenAI and chatbots are a good example. Although I would want a proxy to keep track of usage too in that scenario.
- GabrielMusat 3y ago
  That's a good observation! people that have tried Signway for the OpenAI use case tend to care a lot about tracking usage. The OSS version uses structured logging for reporting usage (just measured by bytes in/out), which can be good enough for some scenarios, but definitely something worth keeping track of.