|
This version is still in development and is not considered stable yet. For the latest stable version, please use Spring AI 2.1.0! |
Community-Maintained Integrations
The integrations on this page are maintained outside the Spring AI repository. Their own documentation is the source of truth for setup and configuration.
| Integration | Provides | Documentation |
|---|---|---|
Qxotic jinfer |
Chat, embedding, text-to-speech and transcription models that run inside the JVM |
|
Oracle Cloud Infrastructure Generative AI |
Chat and embedding models |
|
Azure Cosmos DB |
Vector store |
|
Spring AI Agent Utils |
Agent tools, Agent Skills, long-term memory, sub-agents and sandboxed execution |
|
MCP Security |
OAuth 2.0 and API key security for MCP servers and clients |
|
Exposes a Spring AI agent, built on |
||
Auto-configured clients, agents and transports for the Agent Client Protocol (ACP) Java SDK |
||
One programming model and configuration for coding agents that speak ACP, such as Goose, Codex and OpenCode |
||
Model-as-a-judge, self-refine and guardrail advisors, and patterns built on the |
||
Add-ons for session memory: a turn status for each session, and tool call confirmations that are kept in the session log and resumed on any instance |
||
Amazon Bedrock AgentCore for Spring AI: runtime endpoints, identity, memory, browser, code interpreter and more |
Pages about a community-maintained project outside this section are marked "(Community)" in the navigation. The main page of each project starts with a "Community-maintained" note that links to the project’s own documentation and issue tracker.
Support and Security
Community projects extend Spring AI with integrations and features beyond the core project, and many of them are well worth using. They are maintained by their own authors, not by the Spring AI team, and come with different terms:
-
Support. They are not covered by the Spring AI support policy or by commercial support, and the Spring AI BOM does not manage their versions.
-
Security. They are outside the Spring security policy: each project handles vulnerability reports, fixes and disclosure itself, on its own schedule.
-
Versions. Each project follows its own release schedule and versioning; a 0.x version can change its API between releases.
-
Compatibility. Each release targets specific Spring AI versions: check the project’s documentation before you upgrade either one.
Before you use a community project in production, evaluate it as you would any other third-party dependency: its release history, how active its issue tracker is, and how it handles security reports.