Semantic Gateway is being built to cache by meaning, keep tenants apart, and show you exactly what each request did.
Match prompts by meaning instead of exact text, so a reworded question can return an answer that was already generated.
Cached responses and their vectors are stored in PostgreSQL with pgvector; Redis handles hot-cache and infrastructure concerns.
Send requests to one endpoint. Cache misses are forwarded to the provider you configure.
Issue scoped keys per workspace, see the secret once, and revoke them at any time.
Keys, cache entries, and logs are scoped to a tenant, so one team never receives another team's answers.
Designed to show every request with its hit or miss result, similarity score, latency, and token count. The read APIs are not built yet.
Some capabilities are labelled Preview because the underlying endpoint or user interface is still being completed. Status labels describe the build, not a release date.
Semantic Gateway is not open to the public yet. Leave an email to be considered for the private preview.
Demo form. Nothing is submitted, stored, or sent.