faststream
Asynchronous Python framework for event-driven services. A thin client for Kafka, RabbitMQ, NATS, Redis and MQTT with full access to native broker features, plus AsyncAPI docs, in-memory tests and observability out of the box.
Runssource: GitHubhomepagePythonApache-2.0commit 31df8dac071b
Python, Apache-2.0 licensed. The project labels itself: asyncapi, asyncio, distributed systems, event driven architecture, faststream, kafka, mqtt and mqtt broker.
faststream runs. An Argusic agent installed it in 0.2 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
FastStream 0.7.7 is installed and all in-memory test suites pass: 4526 non-connected tests pass across Kafka, RabbitMQ, NATS, Redis, Confluent, and MQTT brokers, with CLI, ASGI, and AsyncAPI documentation generation working correctly.
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 80 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.
- test_serve_asyncapi_docs_from_app_with_reload fails on first run due to missing @pytest.mark.slow() marker and --reload file-watcher startup timing
- Install time
- under a minute
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- uv run pytest tests/ -m not slow and not connected -- 4526 pass 0 fail; faststream --version prints Running FastStream 0.7.7; uv build --wheel succeeds; individual broker suites all pass
- Model tokens used
- 90,211
- Exact commit tested
- 31df8dac071b
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
No mocks or external credentials needed — this is a pure Python framework with in-memory test broke…
exec
/bin/sh -lc "cat << 'EOF'
EOF" in /work/repo
succeeded in 0ms:
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
succeeded in 0ms:
**FastStream 0.7.7 — clean install, all in-memory tests pass.** Zero errors were introduced. One pr…
tokens used
90,211
**FastStream 0.7.7 — clean install, all in-memory tests pass.** Zero errors were introduced. One pr…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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.2 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.2 minutes after the clone.
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
Topics (from GitHub)
asyncapiasynciodistributed-systemsevent-driven-architecturefaststreamkafkamqttmqtt-brokernatspythonrabbitmqredisstream-processing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/faststream)Questions
- Does faststream run?
- Yes. faststream runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test faststream?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 31df8dac071b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test faststream?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does faststream take to install?
- 0.2 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 faststream need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing faststream?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for faststream?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.