notizen aus dem pool
Guides und Deep Dives vom Team hinter Europas verteiltem KI-Inferenz-Netzwerk — für GPU-Besitzer und für die Entwickler auf der anderen Seite der API.
a GPU died mid-sentence. the sentence finished.
Consumer hardware disappears without notice — someone sits down at their PC, a breaker trips, Wi-Fi drops. Our streams now survive that: another machine picks the answer up mid-word, and the dead segment is billed to nobody.
Artikel lesen →one model, every card: how a 27b runs on 8 gb
Qwen3.8 27B ships in five builds, from Q5_K_M on a 24 GB card down to IQ2_XXS on 8 GB. Why we split models from builds, what quantization actually costs, and how a quantized KV cache doubled our context overnight.
Artikel lesen →we stopped projecting your earnings and started measuring them
Most GPU marketplaces advertise what a card could earn. Our dashboard shows what yours measured, and refuses to show a number until it has one. Here is why that choice cost us a nicer-looking page and was still right.
Artikel lesen →prices should not need an engineer
Our price book used to be a file in a repository, which meant changing a price meant a deploy. It is now a dashboard control with guard rails that refuse an incoherent price — and the file is still the fallback you can return to.
Artikel lesen →our website and our app were two products. now they are one.
The marketing site and the dashboard had different navbars, different footers and different ideas of what we look like. Merging them into one Aurelia app meant solving the problem every SPA has with search engines — and finding two bugs the moment we looked.
Artikel lesen →the container that wasn't there
A friend with a 12 GB card asked what Docker images we'd install on his PC. The honest answer was none — and working out why took us through engines, image digests, registries and what a home GPU should really be asked to run.
Artikel lesen →meet mahout: the open-source agent that puts your gpu in the pool
mahout is ElephantPool's open-source host agent: one small Rust binary that probes your hardware, verifies every download, serves open-weight models, signs a receipt for every job — and pays you 80% of token revenue. How it works, how to install it, how to contribute.
Artikel lesen →why we pay gpu owners 80% — and how the math works
Every job on ElephantPool produces an ed25519-signed receipt, the ledger counts in micro-cents, and hosts keep 80% of token revenue. Here's why the split works and how monthly SEPA payouts happen.
Artikel lesen →your prompts don't belong in virginia — the case for eu-sovereign inference
Prompts are some of the most sensitive data a company produces. CLOUD Act vs GDPR, Schrems II, and what an EU-Sovereign inference tier actually guarantees — attested EU machines, no transfers, standard DPA.
Artikel lesen →ship with open-source ai: one api, the best open models of 2026
Qwen3.8, MiniMax M3, GLM-5.2, DeepSeek V4-Flash and Gemma 4 behind one OpenAI-compatible endpoint. Prepaid credits, spend caps, SSE streaming, transparent per-token pricing — 2–3× cheaper than US APIs.
Artikel lesen →put your gaming gpu to work: earn on every token it serves
Your GPU sits idle most of the day. Install mahout, link your machine, and get paid for every token it serves on the ElephantPool network — NVIDIA and AMD, supported equally from day one.
Artikel lesen →EU-only should be a routing rule, not a sentence on a website
You can now require EU processing per request, and the scheduler refuses to route it anywhere else. Here is how a machine's location is established — and what that proves.
Artikel lesen →Your GPU, your hours
Availability windows, power caps and per-machine limits — set from the terminal or from your phone, with a sync rule that never silently loses an edit.
Artikel lesen →Every token per second is money
Hosts are paid per token, so engine performance is not a benchmark score — it is the hourly rate. What we tune, why we measure instead of upgrading, and what it is worth.
Artikel lesen →Your machine's address never leaves our infrastructure
EU-only routing needs to know where a machine is. Asking a geolocation API would have meant handing a third party the address of every host on the network. So we built the lookup ourselves.
Artikel lesen →One model, nine prices
Everyone else quotes one price per model and never says which version answered. We price each quantization, prove which one ran, and let you set a floor.
Artikel lesen →