awesome-vibecoded-saas
Open-source alternatives to the SaaS tools people pay for
Runssource: GitHubhomepagePythonMITcommit a619af1f0ca9
Python, MIT licensed. The project labels itself: ai apps, ai tools, awesome, awesome list, content creation, creative tools, generative ai and marketing tools.
awesome-vibecoded-saas runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The catalog validator runs on the bundled Python 3.12.3 and reports 'Validated 13 catalog entries.' with exit 0, all catalog JSON parses, and the working tree stays unchanged.
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 100 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.
- python3 -c import jsonschema failed: ModuleNotFoundError (probe only; repo validator is stdlib-only per scripts/validate.py docstring and README)
- network probe to json-schema.org returned HTTP 403 (probe only; not needed by the repo)
- Install time
- 1 minutes
- Cold machine to finish
- 1 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- python3 scripts/validate.py exited 0 and printed 'Validated 13 catalog entries.'; a negative test on a mutated copy exited 1 printing 'slug must use lowercase letters, numbers, and hyphens'; git status --short printed nothing
- Model tokens used
- 48,121
- Exact commit tested
- a619af1f0ca9
- 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.
EOF" in /work/repo succeeded in 0ms: network check failed HTTPError HTTP Error 403: Forbidden The repo's own test suite is `python scripts/validate.py` (also what CI runs). I have positive and … exec /bin/sh -lc 'git status --short; echo "---"; date -u +%H:%M:%S; python3 scripts/validate.py; echo "… succeeded in 0ms: 04:53:07 Validated 13 catalog entries. exit=0 tokens used 48,121
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 1 minute.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- 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 1 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)
ai-appsai-toolsawesomeawesome-listcontent-creationcreative-toolsgenerative-aimarketing-toolsopen-sourceopen-source-alternativesopen-source-appsproductivity-toolssaassaas-alternativesself-hostedself-hosted-appssoftware-alternativesvibe-codingvibecodingweb-apps
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/awesome-vibecoded-saas)Questions
- Does awesome-vibecoded-saas run?
- Yes. awesome-vibecoded-saas runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test awesome-vibecoded-saas?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a619af1f0ca9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test awesome-vibecoded-saas?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does awesome-vibecoded-saas take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does awesome-vibecoded-saas need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing awesome-vibecoded-saas?
- 2 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.
- Where is the evidence for awesome-vibecoded-saas?
- 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.