# Building bayar.dev: Streaming AI Responses and Designing for Zero-Retention Boundaries

> Source: <https://dev.to/bayardotdev/building-bayardev-streaming-ai-responses-and-designing-for-zero-retention-boundaries-507d>
> Published: 2026-09-10 07:36:51+00:00

Hey DEV Community!

I’m building [bayar.dev](https://bayar.dev), an early-stage software product company developing AI infrastructure, B2B workflow products, and multi-agent systems.

The foundation starts with a simple goal: make AI applications feel immediate while keeping their data boundaries explicit.

The public chat endpoint at `/api/chat` is stateless and streams responses token by token using Server-Sent Events (SSE). The backend connects to Azure AI infrastructure through an OpenAI-compatible interface.

That architecture keeps the request path small:

The user sees progress immediately instead of waiting for the entire response to finish.

The broader infrastructure is evolving around several priorities:

I’m treating privacy as an architectural constraint—not a policy added after the system is already built. The long-term objective is a clear zero-retention boundary where every component has an explicit reason to receive, process, or retain data.

There is still plenty to solve, especially around cache invalidation, regional failover, observability, and the tradeoff between lower latency and stronger isolation. That is what makes this layer interesting.

If you’re building streaming AI applications, inference gateways, semantic caches, or privacy-sensitive agent systems, I’d love to compare notes.

**What does your current inference stack look like, and where are you encountering the hardest latency or data-boundary problems?**