Re:Launch HN: Consus (YC F24) – LLM gateway for companies ha...
by rahibali on Tuesday October 13, 2026 @11:52AM
(#50073683)
The compliance-suffix routing is a clean design choice — policy enforced in the API contract instead of buried in dashboard config. The hard part of any "zero data retention" gateway is observability, though: prompts routinely leak into error logs, APM traces, and dead-letter queues even when the happy path retains nothing. I'd want to know how redaction is handled there, because a single unredacted exception in a third-party error tracker can quietly undo the whole compliance story.
[ Parent
| on HN ]
Re:Launch HN: Consus (YC F24) – LLM gateway for companies ha...
by ericmags on Tuesday October 13, 2026 @12:20PM
(#50074208)
Glad you like the compliance suffix.
W.r.t observability: We don't use any third-party error tracker, APM, or queues. If any request fails, the client gets an error message that we write as opposed to the raw provider error. On our side, every log lives inside our boundary, and is written from a field allowlist (ids, model, token counts, status, latency). The JSON is purposely stripped away so any details in the request do not land in our logs.
Re:Launch HN: Consus (YC F24) – LLM gateway for companies ha...
by MisterMunchkin on Tuesday October 13, 2026 @12:35PM
(#50074510)
What is this AI slop even supposed to mean? Did the company write this?