* Break Inference page into several pages
* Make all inference code snippets testable and clean up
* Make more snippets testable
* Edits
* Document automatic query and passage prefix injection in Cloud Inference
Qdrant Cloud Inference silently applies model-specific prefixes (e.g.
"query: "/"passage: " for E5, BGE-style instruction prefix for BGE/mxbai/
Snowflake arctic-embed) so users don't need to manage them manually.
Add a section explaining this behavior, the idempotency guarantee, and
the scope (Qdrant-hosted models only; external providers handle their own).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Document short query optimization in Cloud Inference
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Update links
* Expand on external provider API key usage
* Add section about external provider API keys
* Default to header for external API keys
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Log saturation (ReLU + log1p) is applied per-token before max pooling
across positions, not after. Fix text descriptions and pipeline diagram.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Initial commit
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Edits
* Edits
* Fix links
* Use 'true' instead of '1' in QDRANT__SERVICE__ENABLE_TLS example
* Review feedback
* Add link from Security page
* Update stack designation on overview page
* Update qdrant-landing/content/documentation/tutorials-operations/secure-qdrant.md
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
* Rewrite security page intro to be feature-forward
Replaces the generic opening paragraph with one that names each security
feature (API key auth, read-only keys, JWT RBAC, network binding, TLS,
audit logging) and links directly to their sections, so scanning readers
see the full capability surface before hitting the warning block.
Also updates the checklist items to surface read-only keys and JWT RBAC
as explicit options under Authentication.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add Security FAQ section to Qdrant Fundamentals
Adds three new Q&A entries covering default security posture, read-only
API keys, and JWT collection-scoped access control — the exact questions
users ask in Discord. Also adds Security to the page nav table and fixes
the heading depth on the collection-per-user entry (## → ###).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Add Security section to production checklist
Inserts a new section 2 covering the five key security steps — API key
auth, read-only keys, JWT access control, TLS, and network binding —
with direct links to the Security page. Renumbers existing sections
2–4 to 3–5. Closes the gap where a user following the checklist
step-by-step could go to production with an open, unauthenticated instance.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Link production checklist from both quickstart pages
Adds a production checklist callout to the "Next Steps" section of the
local quickstart and a bullet to the "What's Next?" section of the cloud
quickstart, so users completing either tutorial have a clear path to
production readiness.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Make code snippets testable
* Lead Security page by listing all the features; Rename API keys->Admin API keys, and 'Granular Access Control with JWT' section into 'Granular Access API Keys'
* Update links
* Update meta description
* Fix C# snippet
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Dylan Couzon