alphora
A Production-Ready Framework for Building Composable AI Agents
Runs with mockssource: GitHubhomepagePythonApache-2.0commit 3885e73b8d61
Python, Apache-2.0 licensed. The project labels itself: agent framework, ai agents, llm and multi agent systems.
alphora runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
Alphora 1.3.4 is installed in a venv, all 22 tutorials run without errors, the alphora-web frontend server responds to HTTP 200 on /v1/health, and the publish_agent_api server accepts streaming and non-streaming chat completion requests against a mock OpenAI backend.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 52.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- memory/manager.py inject() failed on plain string -> AttributeError: 'str' object has no attribute 'to_dict'1 minute
- sync long_response path sent unexpected prompt_id to LongResponseGenerator1 minute
- Docker sandbox unavailable (no Docker socket)
- Install time
- 3 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- all 22 tutorials pass (tutorials/*.py), alphora-web --no-browser returns 200 on /, publish_agent_api server responds on /v1/health (200) and /v1/chat/completions (streaming SSE and non-streaming JSON), all core modules import cleanly
- Model tokens used
- 330,669
- Exact commit tested
- 3885e73b8d61
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc '# Quick calculation of time spent (rough) echo "Start time check..." date +%s' in /work/repo succeeded in 0ms: Start time check... 1792786049 All tutorials pass, the API server responds on `/v1/health` (200) and `/v1/chat/completions` (strea… It's about 13 minutes. Let me write the final output. tokens used 330,669 All tutorials pass, the API server responds on `/v1/health` (200) and `/v1/chat/completions` (strea… It's about 13 minutes. Let me write the final output.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 3 minutes.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 3 errors during setup, 1 of which were not solved.
Of the 64 agent-framework projects Argusic has installed and timed, alphora was the 30th fastest to reach a running state, and 51 of 64 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 85.33 | 0.09 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.01 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/alphora)Questions
- Does alphora run?
- alphora runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test alphora?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3885e73b8d61. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test alphora?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does alphora take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does alphora need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing alphora?
- 3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does alphora compare with the alternatives?
- Of the 64 agent-framework projects Argusic has installed and timed, alphora was the 30th fastest to reach a running state, and 51 of 64 reached one at all.
- Where is the evidence for alphora?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.