electric-pglite
Embeddable Postgres with real-time, reactive bindings.
Runssource: GitHubhomepageTypeScriptApache-2.0commit dbd6eb41c9ac
TypeScript, Apache-2.0 licensed. The project labels itself: database, postgres and wasm.
electric-pglite runs. An Argusic agent installed it in 18 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PGlite 0.5.6 core package builds and runs actual PostgreSQL 18.6 WASM queries via Emscripten on Node 18.19.1; 183+ vitest tests pass covering SQL execution, typed params, transactions, live incremental queries, full-text search, large objects, node-fs persistence, dump/load, clone, exec-protocol, and array types. Extension packages (age, tools, icu-full) do not build due to missing WASM artifact submodule.
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.
- Node.js v18.19.1 below required >=205 minutes
- postgres-pglite git submodule empty; Docker unavailable to build WASM from source3 minutes
- Extension packages (pglite-age, pglite-tools, pglite-icu-full) fail to build — they need their own release WASM files3 minutes
- pnpm 9.7.0 not on PATH (npm global install needs root)1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- CJS: `require('./dist/index.cjs')` → `PGlite.create()` → `query('select \'Hello world\' as message;')` returned `[{"message":"Hello world"}]`. ESM: `import { PGlite } from './dist/index.js'` returned same. Version query returned `PostgreSQL 18.6 (PGlite 0.5.16)`. Vitest test suite: 183+ tests passed across basic queries, types, params, transactions, live queries, FTS, large objects, clone, dump/load, node-fs persistence, exec-protocol, notify, describe-query, extended-query-error, and message-context-leak. pg-protocol subpackage: 83/83 tests passed.
- Model tokens used
- 193,322
- Exact commit tested
- dbd6eb41c9ac
- 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 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
basic.test.ts: 68 passed instantiation.test.ts: 7 passed live.test.ts: 50 passed node-fs.test.js: 6 passed node-memory.test.js: 4 passed pg-protocol: 83 passed other test files: dozens more passed Total across runs: 183+ passed, 4 failed (data contamination, pass in isolation), 3 skipped Now compiling the final report: tokens used 193,322 Now compiling 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 4 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 18 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 database projects Argusic has installed and timed, electric-pglite was the 33rd fastest to reach a running state, and 31 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/electric-pglite)Questions
- Does electric-pglite run?
- Yes. electric-pglite runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test electric-pglite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dbd6eb41c9ac. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test electric-pglite?
- 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 electric-pglite take to install?
- 18 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 electric-pglite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing electric-pglite?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does electric-pglite compare with the alternatives?
- Of the 37 database projects Argusic has installed and timed, electric-pglite was the 33rd fastest to reach a running state, and 31 of 37 reached one at all.
- Where is the evidence for electric-pglite?
- 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.