odd-platform
First open-source data discovery and observability platform. We make a life for data practitioners easy so you can focus on your business.
Runssource: GitHubhomepageJavaApache-2.0commit 015f6fa2dac9
Java, Apache-2.0 licensed. The project labels itself: alerting, bigdata, data catalog, data discovery, data engineering, data exploration, data governance and data lineage.
odd-platform runs. An Argusic agent installed it in 23 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ODD Platform backend compiles, starts, and serves HTTP 200 on /actuator/health with local PostgreSQL; 294 JOOQ classes and 367 API contract classes generated; frontend builds with 705 API client files; 645/962 backend tests pass (317 Docker-dependent skipped), 372/384 frontend tests pass.
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.
- PostgreSQL not installed; needed for both JOOQ codegen and runtime5 minutes
- Java 17 (JDK) not found in the container3 minutes
- Docker not available — JOOQ codegen (jooqDockerGenerate task) uses Testcontainers which needs Docker2 minutes
- Node.js 24+ required by frontend but only v18.19.1 was available2 minutes
- Frontend generate.sh uses Docker to run openapi-generator-cli2 minutes
- pnpm (required by frontend) not found, npm install -g failed due to permissions1 minute
- Install time
- 23 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- curl -s http://localhost:8080/actuator/health returned HTTP 200 with body '{"status":"UP"}'
- Model tokens used
- 233,058
- Exact commit tested
- 015f6fa2dac9
- 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.
2026-10-07T22:39:54.319Z INFO 5055 --- [ main] o.s.b.web.embedded.netty.NettyWebServer …
2026-10-07T22:39:54.402Z INFO 5055 --- [ main] o.o.oddplatform.ODDPlatformApplication …
2026-10-07T22:39:54.408Z WARN 5055 --- [ main] o.s.core.events.SpringDocAppInitializer …
2026-10-07T22:39:54.409Z WARN 5055 --- [ main] o.s.core.events.SpringDocAppInitializer …
VERIFIED: 200 on /actuator/health
BODY: {"status":"UP"}
2026-10-07T22:39:56.731Z INFO 5055 --- [ionShutdownHook] o.s.b.w.embedded.netty.GracefulShutdown …
2026-10-07T22:39:56.733Z INFO 5055 --- [ netty-shutdown] o.s.b.w.embedded.netty.GracefulShutdown …
Alright, I have all the data. Here's the final report.
tokens used
233,058
Alright, I have all the data. Here's the final report.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.
- Recovered from all 8 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 23 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 alerting projects Argusic has installed and timed, odd-platform was the 6th fastest to reach a running state, and 4 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
alertingbigdatadata-catalogdata-discoverydata-engineeringdata-explorationdata-governancedata-lineagedata-observabilitydata-pipelinesdata-platformdata-profilingdata-qualitydata-sciencedatacataloglineagemetadatametadata-managementobservabilityoss
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/odd-platform)Questions
- Does odd-platform run?
- Yes. odd-platform runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test odd-platform?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 015f6fa2dac9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test odd-platform?
- The run that produced this verdict cost $0.35: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does odd-platform take to install?
- 23 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 odd-platform need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing odd-platform?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does odd-platform compare with the alternatives?
- Of the 6 alerting projects Argusic has installed and timed, odd-platform was the 6th fastest to reach a running state, and 4 of 6 reached one at all.
- Where is the evidence for odd-platform?
- 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.