Atmosphere

Async IO is the company behind Atmosphere — the real-time transport layer for Java AI agents. We provide the engineering, the support, and the long-term commitment that production systems require.

5 Transports WebSocket, SSE, WebTransport/HTTP3, Long-Polling, gRPC
3 Agent Protocols MCP, A2A, AG-UI
7 AI Runtimes Spring AI, LangChain4j, ADK, Embabel, Koog, Semantic Kernel, Built-in
18 Years in production

Transports. Protocols. Runtimes.

Build once with @Agent — deliver over any transport and any protocol. Three distinct layers, each independently extensible.

Transports

5 transports, one API

Your application code declares what it does. Atmosphere handles how it is delivered — and falls back automatically when a transport is unavailable.

  • WebSocket Full-duplex communication over a single TCP connection.
  • SSE Server-Sent Events.
  • WebTransport/HTTP3 Multiplexed, low-latency transport over QUIC.
  • Long-Polling HTTP long-polling with automatic reconnection.
  • gRPC High-performance RPC framework with bidirectional streaming over HTTP/2.
Auto-fallbackReconnection with jitterHeartbeatsMessage caching
Agent Protocols

3 protocols, zero configuration

Add the dependency to your classpath and your agent speaks the protocol. No manual endpoint wiring, no boilerplate.

  • MCP Model Context Protocol.
  • A2A Agent-to-Agent protocol by Google.
  • AG-UI Agent-User Interaction protocol.
Auto-registered from classpathMulti-channel: Slack, Telegram, Discord, WhatsApp, Messenger
AI Runtimes

7 backends, swap by dependency

Atmosphere is the infrastructure layer underneath your LLM library. Your @Agent and @AiTool annotations work identically across all backends.

  • Built-in Atmosphere's zero-dependency OpenAI-compatible client.
  • Spring AI Spring's official AI framework.
  • LangChain4j Java port of the LangChain ecosystem.
  • Google ADK Google's Agent Development Kit for building multi-agent systems.
  • Embabel Goal-driven agent framework by Rod Johnson (creator of Spring).
  • JetBrains Koog Kotlin-native AI framework by JetBrains.
  • Semantic Kernel Microsoft's enterprise-grade AI orchestration SDK.
Portable @AiTool across all backendsConversation memoryStructured outputUsage tracking

One support contract. Every Java AI framework.

The Java AI ecosystem has seven frameworks. Each one is moving fast, each one has its own release cadence, and each one could change direction tomorrow. Atmosphere is the runtime-abstraction layer that makes your @Agent, @AiEndpoint, and @AiTool code portable across all seven — swap the dependency, keep the code. Async IO maintains the abstraction and the bridges; our support contract is the insurance policy against vendor lock-in.

Spring AI

Spring / VMware

Spring's official AI framework. ChatClient, advisors, RAG, VectorStore, and full auto-configuration.

atmosphere-spring-ai Bridged

LangChain4j

Community

Java port of the LangChain ecosystem. Chains, AI services, streaming chat models, and tool bridging.

atmosphere-langchain4j Bridged

Google ADK

Google

Agent Development Kit. Multi-agent orchestration, sessions, and the Runner execution engine.

atmosphere-adk Bridged

Embabel

Embabel

Goal-driven agent framework from the creator of Spring. Declarative goals, planned execution, native PromptRunner.

atmosphere-embabel Bridged

JetBrains Koog

JetBrains

Kotlin-native AI framework. Structured concurrency, typed tools, and a composable agent DSL.

atmosphere-koog Bridged

Semantic Kernel

Microsoft

Microsoft's enterprise-grade AI orchestration SDK. ChatCompletionService, kernel plugins, memory, planners.

atmosphere-semantic-kernel Bridged

Built-in

Async IO

Atmosphere's zero-dependency OpenAI-compatible client. Built for tests and local dev without pulling in a framework — works with OpenAI, Gemini, Ollama, and any compatible endpoint.

atmosphere-ai Bridged
At-a-glance: seven frameworks, one bridge layer, one support contract.
Framework Language Vendor Atmosphere bridge Atmosphere support
Spring AI Java Spring / VMware atmosphere-spring-ai Included
LangChain4j Java Community atmosphere-langchain4j Included
Google ADK Java Google atmosphere-adk Included
Embabel Kotlin Embabel atmosphere-embabel Included
JetBrains Koog Kotlin JetBrains atmosphere-koog Included
Semantic Kernel Java Microsoft atmosphere-semantic-kernel Included
Built-in Java Async IO atmosphere-ai Included

Abstracted, portable, and then some

Atmosphere runs on top of each framework and its ecosystem — Spring for Spring AI, the LangChain4j chain library, Google ADK, Microsoft Semantic Kernel, JetBrains Koog, and Embabel's planning engine. The Built-in runtime is a zero-dependency OpenAI-compatible client for tests and local dev. Whichever you pick, you code against one surface — @Agent, @AiEndpoint, @AiTool — and you get more than any framework ships on its own.

Abstracted through the @Agent API

Portable across all 7 runtimes

Every framework provides these. Atmosphere normalizes them behind one annotation surface, so your agent code is identical whether you run on Spring AI, Koog, or anything in between.

  • Streaming text to any client
  • Tool calling with @AiTool and JSON-schema parameters
  • Human-in-the-loop approval gates via @RequiresApproval
  • Structured output with response schemas
  • Conversation memory across turns
  • Vision and multi-modal input on any framework that supports it
  • Token-usage accounting on every response
  • Per-request retry policy and prompt caching
Only with Atmosphere

Wired to your agent, not to your infra team

The wider JVM ecosystem has pieces of some of these — Spring has WebSocket and Kafka, Spring Integration has channel adapters, there are community MCP clients. Atmosphere is what wires every item below directly to your @Agent / @AiTool code, shipped as one coherent stack and covered by one SLA — instead of half a dozen separate libraries your team glues together.

  • Cross-framework @Agent portability — one codebase, seven runtimes
  • Real-time streaming transport: WebSocket, SSE, WebTransport/HTTP3, gRPC, long-poll with automatic fallback
  • @Coordinator + @Fleet multi-agent orchestration with A2A protocol
  • Durable HITL workflows — agent state survives JVM restart via CheckpointStore
  • @Command routing to Slack, Telegram, Discord, WhatsApp, Messenger
  • Rooms, presence, and broadcaster clustering over Kafka or Redis
  • MCP server — expose @AiTool to Claude, Copilot, Cursor, any MCP client
  • atmosphere.js client SDK with React, Vue, Svelte, and React Native hooks
  • Enterprise support every year since 2014 — eleven consecutive years

No vendor lock-in. One support contract.

You are not shopping between Spring AI and LangChain4j — you already want an agent stack that does not lock you into one framework, one LLM provider, or one vendor. Atmosphere is that stack. Async IO has been selling the support contract that covers the abstraction and the swap — every year, since 2014.

Without Atmosphere

Locked in

  • One framework, chosen up front.
  • One LLM provider, locked into its pricing and SLA.
  • Rewrite the agent when the framework changes direction, goes EOL, or gets acquired.
  • Separate support contracts with each vendor. No one owns the integration.
  • No escape hatch if the bet goes wrong.
With Atmosphere + Async IO support

Portable, covered

  • Seven frameworks, portable @Agent code. Swap the dependency when the winner changes.
  • Any LLM provider supported by any of the seven frameworks. Move when pricing shifts, rate limits bite, or a new model lands.
  • The abstraction holds. Your @Agent, @AiEndpoint, and @AiTool code do not move.
  • One support contract with Async IO. Eleven years of shipping Atmosphere and writing every bridge on this page.
  • The escape hatch is the product. The swap is what you are paying us to maintain.

Production-grade agent infrastructure

Everything you need to build, deploy, and operate AI agents in production. Spring Boot 4.0 and Quarkus 3.21+ auto-configuration included.

@Agent Annotation

One class, one annotation. Endpoints, commands, tools, skill files, conversation memory, and protocol exposure are all auto-wired.

@Coordinator Orchestration

Manage fleets of agents with parallel fan-out, sequential pipelines, conditional routing, and result evaluation.

Durable Workflows

CheckpointStore persists workflow state as parent-chained snapshots. Pause workflows without holding a thread; resume via REST.

Human-in-the-Loop

@RequiresApproval pauses tool execution for human approval. The virtual thread parks cheaply until the client responds.

6 Channels

Web, Slack, Telegram, Discord, WhatsApp, Messenger. Set a bot token and the same @Command + AI pipeline works everywhere.

Admin Control Plane

Real-time dashboard, 25 REST endpoints, WebSocket event stream, and MCP tools for managing agents and runtimes.

Observability

OpenTelemetry tracing, Micrometer metrics, and AI token usage tracking. Auto-configured with Spring Boot.

Client SDKs

atmosphere.js with React, Vue, Svelte, and React Native hooks. Streaming, offline queues, auth token refresh.

Built by the people who wrote the spec

Atmosphere has been in continuous production since 2008 — powering trading floors, healthcare systems, collaboration tools, and AI applications at companies from startups to the Fortune 500. The team brings over 30 years of experience in real-time systems, JVM internals, and AI infrastructure.

We contributed to Java NIO/AIO and have been shipping real-time Java infrastructure since before WebSocket was standardized. Atmosphere itself has been open source since day one, and the project is backed by a team of Java Champions and Apache Committers who have been active in the JVM ecosystem for decades.

Java Champions Apache Committers JVM NIO/AIO contributors Open source since 2008
3.7k+ GitHub stars
18 Years in production
253 Versions on Maven Central
Apache 2.0 License

Backed by the team that built it

Get direct access to the core engineering team. We wrote the framework, we maintain it, and we stand behind it. Meet your production schedule and compliance requirements with guaranteed response times.

Bronze

  • Coverage Business Hours
  • Response (S1) 7 Business Days
  • Response (S2) 10 Business Days
  • Incidents 2 / year
  • Phone Support
  • Email Support
  • Emergency Patches
Get a Quote

Silver

  • Coverage Business Hours
  • Response (S1) 1 Business Day
  • Response (S2) 2 Business Days
  • Incidents 10 / year
  • Phone Support
  • Email Support
  • Emergency Patches
Get a Quote

Gold

  • Coverage Business Hours
  • Response (S1) 4 hours
  • Response (S2) 1 Business Day
  • Incidents 15 / year
  • Phone Support
  • Email Support
  • Emergency Patches
Get a Quote

Platinum

  • Coverage 24x7
  • Response (S1) 1 hour
  • Response (S2) 4 hours
  • Incidents Unlimited
  • Phone Support
  • Email Support
  • Emergency Patches
Get a Quote
Legacy

Atmosphere 2.x / 3.x Support

Still running Atmosphere 2.x or 3.x in production? We provide long-term support, security patches, and migration guidance for legacy deployments. Includes a migration path to Atmosphere 4.x when you are ready.

Contact Us