DEEIX-Chat
An enterprise AI workspace for model routing, multimodal chat, files, tools, billing, identity, and operations.
Runssource: GitHubhomepageGoApache-2.0commit 16450dbc4176
Go, Apache-2.0 licensed. The project labels itself: ai, ai chatbots, llm, mcp, open source, rag, self hosted and ui.
DEEIX-Chat runs. An Argusic agent installed it in 21 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The DEEIX Chat monorepo builds completely: Go backend compiles, all Go unit tests pass (internal/application, shared, ports, transport/http, etc.), Next.js frontend builds to static output, and the single binary serves both API and frontend on port 8080 returning 200 on health, API, and static endpoints
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.
- Go 1.26 compiler not found in container2 minutes
- libsqlite3-dev headers/libs missing for CGO2 minutes
- pnpm isolated linker hid tailwindcss-oxide native .node binary from turbopack bundler2 minutes
- pnpm not available; npm install -g failed due to permissions1 minute
- Node.js 18 too old for Next.js 16 (needs >=20.9.0)1 minute
- Install time
- 21 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./... exited 0 (all packages pass); frontend pnpm build --filter=@deeix/web succeeded; server launched on port 8080, curl returned HTTP 200 on /healthz, /readyz, /api/v1/version, /api/v1/branding, /api/v1/auth/login-options, frontend root, /chat, and /swagger
- Model tokens used
- 173,467
- Exact commit tested
- 16450dbc4176
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
`pnpm build --filter=@deeix/web` — **frontend builds successfully**, all pages rendered.
Server test (single exec_command run to keep background alive):
```
healthz: HTTP 200
readyz: HTTP 200
/api/v1/version → {"product":"DEEIX Chat","version":"0.4.1",...}
/api/v1/branding → {"errorMsg":"","data":{...}}
/api/v1/auth/login-options → {"errorMsg":"","data":{...}}
frontend root HTTP 200
frontend /chat HTTP 200
/swagger HTTP 200
```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 5 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 21 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, DEEIX-Chat was the 35th fastest to reach a running state, and 30 of 37 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/deeix-chat)Questions
- Does DEEIX-Chat run?
- Yes. DEEIX-Chat runs. Argusic installed and launched it on a clean machine in 21 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test DEEIX-Chat?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 16450dbc4176. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test DEEIX-Chat?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does DEEIX-Chat take to install?
- 21 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 DEEIX-Chat need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DEEIX-Chat?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does DEEIX-Chat compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, DEEIX-Chat was the 35th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for DEEIX-Chat?
- 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.