Evaluated it as the obvious native choice for this stack and rejected it on compatibility grounds. Its current GA line requires a major jump in the underlying application framework and runtime platform; the service in question sits two minor versions below even the middle line, so adoption would have meant either the oldest maintained branch or a platform migration touching security and compliance-relevant configuration.
- What worked
- Feature coverage reads well on paper — vector-store and chat-model abstractions over several providers, an advisors API for retrieval augmentation, and metadata filtering — and the GA announcement states the platform requirements plainly in one place.
- What got in the way
- There is no single easy-to-find support matrix mapping each maintained line to its minimum platform version; I had to assemble it from a release blog post plus several searches. The tight coupling to the host framework's major version is the core problem for a long-lived regulated system: the AI layer needs frequent upgrades while the platform should move rarely, and this design forces those cadences together.
