# future-agi: Evaluate, Trace, and Improve AI Agents

This repository profile is provided by osrepos.com, an open source repository discovery platform.

Source: osrepos.com
Repository profile: https://osrepos.com/repo/future-agi-future-agi
Generated for open source discovery and AI-assisted research.

Future AGI is a self-hostable platform for evaluating, observing, and improving LLM and AI agent applications, with OpenTelemetry-native tracing at its core. It connects simulations, evaluations, guardrails, and an LLM gateway in a shared feedback loop.

GitHub: https://github.com/future-agi/future-agi
OSRepos URL: https://osrepos.com/repo/future-agi-future-agi

## Summary

Future AGI is a self-hostable platform for evaluating, observing, and improving LLM and AI agent applications, with OpenTelemetry-native tracing at its core. It connects simulations, evaluations, guardrails, and an LLM gateway in a shared feedback loop.

## Topics

- python
- ai-agents
- evaluation
- observability
- self-hosted
- llm-tracing
- agent-simulation

## Repository Information

Last analyzed by OSRepos: Wed Nov 18 2026 05:20:37 GMT+0000 (Western European Standard Time)
Detail views: 2
GitHub clicks: 1

## Safety Notice

OSRepos shares public repositories for knowledge and discovery only. Review source code, dependencies, licenses, and security implications before running or installing anything.

## Content

## Overview

Future AGI is an open-source platform for evaluating, observing, and improving LLM and AI agent applications. Built around OpenTelemetry-native tracing, it aims to solve the problem of teams stitching together separate tools for testing, production monitoring, and user protection without a shared feedback loop.

The platform combines simulations, evaluation, tracing, guardrails, an OpenAI-compatible gateway, and prompt optimization. Teams can use the managed cloud or self-host the platform; the README describes Docker Compose deployments and a Kubernetes Helm option. Its Apache 2.0 core is intended for teams that want to inspect and control their evaluation logic and data.

## Key Features

- Instrument AI applications with OpenTelemetry tracing, with integrations for more than 50 frameworks.
- Evaluate outputs using metrics for areas such as groundedness, hallucinations, tool use, and PII.
- Simulate conversations with personas, adversarial inputs, and edge cases, including voice-agent scenarios.
- Apply built-in guardrail scanners or connect vendor adapters to check inputs and outputs.
- Route model requests through an OpenAI-compatible gateway with provider integrations, routing strategies, and semantic caching.
- Use production traces as feedback for prompt optimization and subsequent evaluations.

## Use Cases

- An AI application team can use simulations and evaluations to test an agent against edge cases before release.
- An operations team can trace agent runs in production and inspect spans, latency, and token cost.
- A team building a customer-facing agent can apply guardrails to screen for risks such as PII, jailbreaks, and prompt injection.
- Developers working with voice agents can simulate and evaluate conversations across supported voice platforms.

## Our Take

This is a broad, actively maintained platform for teams that want to bring agent testing, tracing, and runtime protections together, rather than adopt a single-purpose evaluation or observability tool.

**Good fit if:**
- You need simulations, evaluations, OpenTelemetry tracing, and guardrails in one agent-development workflow.
- You want to self-host an Apache 2.0 platform and can operate its Docker-based stack.
- You value an active project with regular releases and contributions from a broad group of developers.

**Look elsewhere if:**
- You need only a lightweight SDK or one standalone capability rather than a multi-component platform.
- You cannot provide Docker Compose and the resources needed for its self-hosted setup.
- Your deployment depends on a specific capability not listed in the README, such as a supported migration from a Standalone install to a Distributed one.

## Project Health

| Signal | Value |
|---|---|
| Status | **Active**: regular commits and releases |
| Last commit | 2026-11-18 (today) |
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 73 (latest v1.58.0, 2026-11-03) |
| Contributors | 97 (top contributor: 32% of commits) |
| Issues closed, last 90 days | 1+ |
| Pull requests merged, last 90 days | 62 (typically merged in 3 days) |
| Project age | 7 months |

Checked on 2026-11-18 with the GitHub API.

## Project Facts

- Language: Python
- License: Apache-2.0
- Stars: 2.3k
- Forks: 721
- Topics: agent-evaluation, ai-agents, ai-evals, ai-gateway, ai-observability, evals, evaluation-framework, guardrails
- Website: https://futureagi.com
- Archived: no

## What You Need

Detected in the repository:

- Node.js (from package.json)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- A test suite and automated checks on GitHub Actions

## Getting Started

For self-hosting, the README requires Docker Desktop or Docker Engine with Compose v2.24 or newer. Clone the repository and run the installer:

```bash
git clone https://github.com/future-agi/future-agi.git
cd future-agi
./bin/install
```

See the [README](https://github.com/future-agi/future-agi) for configuration, cloud setup, deployment choices, and tracing examples.

## License in Plain Words

**Apache-2.0** (permissive).

- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors

A summary, not legal advice: the LICENSE file is what applies.

## Alternatives

- [phoenix](https://osrepos.com/repo/arize-ai-phoenix): Phoenix focuses on self-hosted tracing, evaluation, and troubleshooting, while Future AGI also combines simulations, guardrails, and an LLM gateway.
- [langwatch](https://osrepos.com/repo/langwatch-langwatch): LangWatch combines observability and simulation testing with prompt management and governance, while Future AGI centers its feedback loop on OpenTelemetry-native tracing.
- [opik](https://osrepos.com/repo/comet-ml-opik): Opik offers tracing, experiments, datasets, and prompt tools, while Future AGI additionally brings simulations, guardrails, and an LLM gateway into its platform.
- [weave](https://osrepos.com/repo/wandb-weave): Weave focuses on tracing and evaluating application runs, while Future AGI adds agent simulations, guardrails, and an LLM gateway.

| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| **future-agi** | Python | Apache-2.0 | 2.3k | Active |
| [phoenix](https://osrepos.com/repo/arize-ai-phoenix) | Python | Other | 11.7k | Active |
| [langwatch](https://osrepos.com/repo/langwatch-langwatch) | TypeScript | Apache-2.0 | 4.9k | Active |
| [opik](https://osrepos.com/repo/comet-ml-opik) | Python | Apache-2.0 | 22.8k | Active |
| [weave](https://osrepos.com/repo/wandb-weave) | Python | Apache-2.0 | 1.1k | Active |

## Considerations

- The default self-hosted Standalone setup requires Docker to have 2 vCPUs and 4 GB of memory available; the installer downloads roughly 800 MB of images. The README lists higher resource needs for Distributed deployments.
- The project is actively developed, with recent commits and releases and contributions from many people. Its measured issue handling is less clear: only a small number of issues were closed in the recent period, and there is no median close time available.
- The README says data cannot be moved from a Standalone install to Distributed or Helm later through a supported path, so choose the deployment model before adding data.
- Self-hosted telemetry is enabled by default. The README documents its payload and opt-out settings; teams with strict outbound-network policies should review these before deployment.