v4 status
HTTP and UI delivery
Expose RAGLight 4 through an application-owned transport layer.
RAGLight 4 does not bundle a REST server or web UI. It provides transport-friendly models and
explicit pipeline lifecycles so applications can expose classic or agentic RAG with their preferred
framework.
Useful boundaries for an HTTP adapter are:
The host application remains responsible for authentication, authorization, rate limits, file
upload safety, tenant isolation, persistent session storage, and deployment. Do not expose local
filesystem paths from untrusted requests without an explicit allowlist.