Agent-O-Rama: Build, Trace, Evaluate, and Monitor LLM Agents in Java or Clojure
Posted2 months agoActiveabout 2 months ago
blog.redplanetlabs.comTechstory
calmmixed
Debate
20/100
LLM AgentsRamaJava/clojure Development
Key topics
LLM Agents
Rama
Java/clojure Development
The post introduces Agent-o-rama, a tool for building and managing LLM agents in Java or Clojure, sparking discussion about its technical internals and potential concerns around data access and backup.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
4h
Peak period
2
4-6h
Avg / period
1.3
Key moments
- 01Story posted
Nov 3, 2025 at 1:16 PM EST
2 months ago
Step 01 - 02First comment
Nov 3, 2025 at 5:11 PM EST
4h after posting
Step 02 - 03Peak activity
2 comments in 4-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 4, 2025 at 11:00 AM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45802290Type: storyLast synced: 11/20/2025, 12:50:41 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I see you're still using Clojure since writing Apache Storm!
- Execution model: Koog is a library for defining agents that run within a single process. AOR agents execute across a distributed cluster, whether one node or thousands.
- Deployment and scaling: Koog provides no deployment or scaling mechanisms. That's something you need to figure out on your own. AOR includes built-in deployment, updating, and scaling.
- Integration complexity: Koog must be combined with other tools (monitoring tool, databases, deployment tools, etc.) to approximate a complete agent platform. AOR is fully integrated, including built-in high-performance, durable storage for any data model.
- Experimentation and evaluation: Koog has no features for experimentation or online evaluation. AOR includes extensive support for both.
- Scalability: AOR scales horizontally for both computation and storage. With Koog, you'd need to design and operate that infrastructure yourself.
- Observability: Koog's observability is limited to traces and basic telemetry exposed via OpenTelemetry. AOR provides a much broader set of telemetry, including "time to first token" and online evaluation charts. You can also split all time-series charts automatically by any metadata you attach to your runs (e.g. see how agent latency differs by the choice of model used). Plus, it's all built-in and automatic.
Please correct me if I'm wrong on any aspect of Koog.
Rama isn't open source, but it's far from a black box. All data structures and computation are fully visible in the UI. You can inspect depots, topologies, and PStates, and see exactly what's stored and how it changes over time. Everything is also accessible through the Rama client API for direct querying. The PState schemas used by Agent-o-rama are defined here: https://github.com/redplanetlabs/agent-o-rama/blob/master/sr...
Backups are easy: you configure a “backup provider” (we provide one for S3) and a schedule for incremental backups. The free version can also be backed up with a short maintenance window. Full details are here: https://redplanetlabs.com/docs/~/backups.html