Review Machine · Master Review · local model runner
Ollama v0.34.1
Across 18 sources read on 16 September 2026 and dated between March 2025 and 14 September 2026, the one-command install, the wide model library and the local API are what the press and the independent reviews agree on, while the memory a model needs sets the ceiling; no source we could reach reviewed v0.34.1 itself.
Release read v0.34.1, 14 September 2026Licence MIT, per the licence fileLocal API HTTP on port 11434Platforms macOS, Windows, LinuxRead 16 September 2026Skip to the verdictRead as text

Verdict age
ProvisionalEditors and independent reviews in · no owner reviews readThe official tier and the repository figures are two days old or less. The press and independent reviews are five to thirteen months old and describe earlier releases, so anything they say about speed, defaults or hardware needs could have moved several versions since, and the current release notes are the only source here that speaks for v0.34.1.
- Early · editors only
- Provisional · editors in, owners thin
- Settled · owner reviews read over months
From 18 sources to one verdict
Seven levels, in the same order in every Master Review. Each line is the takeaway; open a level for the evidence under it, or stop when you have enough.
What we read
18 sources, 19 Mar 2025 – 16 Sep 2026. Editorial, news, buyer, forum and other tiers thin. Video tier empty.
By tier, heaviest first
README, quickstart, licence, v0.34.1 release notes and pricing, all read 16 September 2026.
Two ZDNET pieces and one New Stack how-to; none of them describes v0.34.1.
Two New Stack reports on releases, in March and August 2026.
The GitHub REST API figures for the repository, read 16 September 2026: attention, not satisfaction.
Two Hacker News threads and one repository issue, from March 2025 to April 2026.
Three independent review sites and one vulnerability-database listing, January to August 2026.
Date window
19 Mar 2025 to 16 Sep 2026
Editorial reviews 6 Sep 2025 – 26 May 2026 · News 31 Mar – 26 Aug 2026Official pages and repository figures describe v0.34.1 on 16 September 2026; no press, editorial or independent review of v0.34.1 was reachable, so those tiers describe the 0.19 to 0.33 lines and are dated.
Couldn’t read, so not used
- Ars Technica, MLX coveragebot check
- Tech Insider, LM Studio comparisonbot check
Nothing in this reading rests on either page, and neither is cited.
Read, then rejected
- Thoughtworks Technology Radar, Ollama · Assesses an April 2024 build, a different version line, and predates everything else in the sample.
- Ollama blog, all aboard open models · A company announcement of funding and developer counts: a maker's claim with nothing on the themes counted here.
- Local AI Master, version history · Release history rather than behaviour, so it counted nothing the themes rest on.
What they measured
Three hard readings: the repository's own figures, the published prices, and what the v0.34.1 release notes say they improved.
Repository figures, 16 September 2026
181074starsAs the GitHub REST API returned it
GitHub · read 16 Sep17892forksAs the GitHub REST API returned it
GitHub · read 16 Sep4013open issuesOpen, not abandoned and not a defect count
GitHub · read 16 SepAttention by a date, not quality and not satisfaction.
Published prices
0USD, FreeLocal models, no service fee
Ollama · read 16 Sep20USD/monthPro: $60 of usage credits a month
Ollama · read 16 Sep100USD/monthMax: $300 of usage credits a month
Ollama · read 16 SepFrom the pricing page on the date read.
v0.34.1 release notes, 14 September 2026
294msCold /api/tags on a large model library, down from 3.1 s in Ollama's own testing
GitHub · 14 SepWhere they agree
One command to a running model, a library that keeps up, and an API other software already speaks.
One tick per editorial review, in order of publication:TN The New StackZD ZDNETZD2 ZDNET
One command, and a model answers
2/3Install and first run, described by the official pages and the reviews. T1Official T2Editorial Other
A model library that keeps up
1/3A catalogue rather than a fixed set, refreshed with the release. T1Official T2Editorial T2News Other
A local API other software already speaks
1/3OpenAI-shaped calls answered on port 11434. T1Official T2Editorial Other
Free on your own machine, under a permissive licence
1/3MIT code, and the local path at $0 with no service fee. T1Official T2Editorial Other
The work stays where the model runs
1/3The reason the sources give for running it locally at all. T2Editorial T2News Other
What the repository publishes about itself
The GitHub REST API returned 181,074 stars, 17,892 forks and 4,013 open issues for ollama/ollama on 16 September 2026. T3Buyers
181074Stars17892Forks4013Open issues
The platform's own counts, not reviews we read, and attention rather than quality.
What keeps coming up against it
Memory sets the ceiling, and concurrency is not what the runner was built for.
Memory sets the ceiling
Documented across three tiers · how common among users unknownNeither the README nor the quickstart we read states a minimum amount of memory, so the official tier documents nothing here.
2/3February 2026: small models ran slowly on a 16 GB M1 MacBook Pro and the writer advises 32 GB. May 2026: a floor of 16 GB of memory, with 8 GB of video memory or Apple Silicon with 16 GB or more.
- ZDNET 16 GB M1 MacBook Pro, small models only
- ZDNET Floor of 16 GB, 8 GB video memory
March 2026: the Apple backend preview requires 32 GB of memory and supports one model.
The New Stack · 31 Mar
May 2026 and August 2026: 16 GB is the minimum and 32 GB the practical baseline, because a model that does not fit is a model that swaps to disk.
aifoss.dev · 14 MayFrancis Okafor · 28 Aug
Concurrency is not what it was built for
0/3Two independent reviews describe four parallel requests by default, no continuous batching and no paged cache, with sequential queuing under load. Other
The default context window is easy to get wrong
0/3A 4,096-token default in August 2026, and a model advertising 131,072 running at 2,048 in March 2025. Forum Other
A release can change behaviour under you
0/3An integration withdrawn and returned, a backend arriving as a preview, and a setting deprecated with the current release. T1Official T2News
The API is unauthenticated where it listens
0/3The Go vulnerability database listing for the module records missing authentication on model management operations, reported as that database states it. Other
Where they split
Whether the layer should exist is argued; how much context you get by default has moved.
Whether the layer should exist at all
A piece titled The local LLM ecosystem does not need Ollama, with 207 comments, argues the wrapper between you and the model is unnecessary.
Against that: A writer who stopped using a hosted assistant for the same work describes using this runner instead.
Both trueThe thread is not unanimous: the most upvoted reply in the part we read credits the project with solving first-run experience. Disagreement about the layer is not disagreement about the software.
How much context you get by default
A 4,096-token default, with the front of the prompt dropped past it without a warning.
Against that: A model advertising a 131,072-token context ran at 2,048 tokens until the size was set.
Our readThe default has moved between those dates. What both sides describe is a limit that is silent rather than a limit that is fixed.
Who it's for, who should pass
For one person with the memory to spare; not for a team behind one endpoint, or a 16 GB laptop.
It suits you if
- You want open-weight models on a machine you already own, with the weights and the prompts staying there.Official pages and independent reviews all describe this setup, and the local path is priced at $0 with no service fee.
- You write against an OpenAI-shaped API and want the same call to reach a local model.The README, the quickstart and the August 2026 independent review all describe the same call working at both ends.
- You are one person, or a few, prototyping against a model you host.Both independent reviews that measure traffic describe a single-user or small-team load as what this runner is built for.
Pass if
- You are counting on a 16 GB laptop for anything beyond the smallest models.The February 2026 hands-on piece advises 32 GB after running one, and the independent reviews put 16 GB as the floor rather than a comfortable figure.
- You need throughput behind one endpoint for a team.Both independent reviews that measure traffic describe a ceiling on parallel requests, and one names other runners as the migration path.
- You are about to listen on an address other machines can reach.The Go vulnerability database listing of 14 January 2026 records missing authentication on model management operations; we report that listing, not a verdict of our own.
The verdict
The default way to run open weights locally, on hardware that decides how much of it you get.
A one-command local runner with a wide library and an OpenAI-shaped API, whose ceiling is the memory of the machine it runs on and whose current version no reviewer we could reach has written about.
Confidence, by tier
Release notes, docs, licence and pricing describe v0.34.1 directly.
Three pieces, the newest from May 2026, covering earlier builds.
Two reports on releases, neither reviewing the current build.
Repository figures are attention by a date, never satisfaction.
Two threads and one issue, read as ordinary pages, counted as themes and never as ratings.
Three independent reviews plus one vulnerability listing, none of them about v0.34.1.
No video review was read for this reading.
- Editorial evidence
- 3–12 months old
- Newest report
- 26 Aug 2026
- Read
- 16 Sep · month 17
Free to download. Your graphics card sends the invoice.
Rests onThe licence file is the MIT licence and the pricing page lists the local path at $0, while five of the sources we read, across the editorial, trade-press and independent tiers, put memory or video memory between you and a usable model; no source we read counts how many users hit that wall.
Sources
18 sources, heaviest tier first. Every figure above comes from one of these.
- T1OfficialOllama v0.34.1 release notes14 Sep
- T1OfficialOllama READMEno date of its ownread 16 Sep
- T1OfficialOllama quickstartno date of its ownread 16 Sep
- T1OfficialOllama licence fileno date of its ownread 16 Sep
- T1OfficialOllama pricingno date of its ownread 16 Sep
- T2EditorialConnect to a Local Ollama AI Instance From Within Your LAN6 Sep 2025
- T2EditorialI tested local AI on my M1 Mac, expecting magic1 Feb
- T2EditorialI quit ChatGPT for a free, private, and local AI called Ollama26 May
- T2NewsOllama taps Apple's MLX framework to make local AI models faster on Macs31 Mar
- T2NewsClaude Desktop can now easily run Qwen, DeepSeek and Kimi models26 Aug
- T3Buyersollama/ollama repository figures, GitHub REST APIone API call, figures as returnedread 16 Sep
- ForumIssue 9890: Large context size completely breaks the usability of the model19 Mar 2025
- ForumOllama is now powered by MLX on Apple Silicon in preview31 Mar
- ForumThe local LLM ecosystem doesn't need Ollama16 Apr
- OtherGO-2025-4251: Ollama missing authentication for model management operations14 Jan
- OtherOllama 2026 Review: The Default Local LLM Runner14 May
- OtherOllama Review: 14 People, 8.9 Million Developers a Month14 Aug
- OtherOllama Review: Pricing, Pros and Cons28 Aug
MethodThis reading covers 18 sources dated between March 2025 and 14 September 2026 and read on 16 September 2026, across official documentation, trade press, independent reviews, the repository's own figures and developer threads, synthesised with AI; nothing was installed, prompted, run or tested.
Dates without a year are 2026.
The review as text
Ollama is the local model runner from Ollama Inc., and this reading is of v0.34.1, released on 14 September 2026 and read two days later. It installs on macOS, Windows and Linux, pulls open-weight models onto the machine in front of you, and answers on a local HTTP API on port 11434. The code is MIT-licensed.
We read 18 sources: five official, being the README, the quickstart, the licence, the v0.34.1 release notes and the pricing page; three editorial reviews and how-tos; two trade-press reports; the repository's figures from the GitHub REST API; three developer threads; and four review sites outside the trade press. They are dated between March 2025 and 14 September 2026. No source we could reach wrote about v0.34.1 itself, so the press, editorial and independent reviews all describe earlier release lines, and only the official tier and the repository figures speak for the version named above.
Consensus
The agreement is on the shape of the product rather than on this week's build, and none of the eight press, editorial and independent reviews disputes it: a local runner that installs in one command, carries a large and quickly refreshed model library, and speaks an OpenAI-shaped API on localhost. The repository figures give the scale, 181,074 stars, 17,892 forks and 4,013 open issues on 16 September 2026: how many people looked by that date, and not how many are satisfied. The published terms: the local path is $0 with no service fee, Pro is $20 a month with $60 of usage credits, and Max is $100 with $300.
Confidence is uneven by tier. The official tier is strong, because the release notes, the docs and the licence describe v0.34.1 directly. Every other tier is thin for this version, and the editorial tier is thin twice over at three pieces covering earlier builds. We read the consensus as moderate on what Ollama is for and weak on how v0.34.1 behaves.
Recurring strengths
One command, and a model answers. Six of the sources we read describe install and first run as the part Ollama got right, two of them editorial reviews: the README and the quickstart give one line per platform, and the ZDNET pieces of February and May 2026 both describe a first response with no key and no configuration file.
A model library that keeps up. Five sources, one editorial and two official: the README points at a library rather than a fixed set of models, the v0.34.1 release notes record backend updates shipped alongside the release, and the March 2026 report describes a new Apple backend arriving inside an ordinary release.
A local API other software already speaks. Five sources, among them the official quickstart and an editorial how-to: the server answers on port 11434 in the OpenAI chat format, so a tool written for a hosted model reaches a local one by changing an address.
Free on your own machine, under a permissive licence. Four sources, three official and one editorial: the licence file is MIT, the pricing page lists the local path at $0 with no service fee, and the May 2026 ZDNET piece lists the fees it stopped paying.
The work stays where the model runs. Three sources, one of them editorial: the May 2026 ZDNET piece keeps sensitive files off another company's server, the August 2026 independent review puts control of the data first, and the August 2026 trade-press report notes the models can run on the machine rather than at a provider.
Recurring complaints
Memory sets the ceiling. Five sources across three tiers describe it. The February 2026 hands-on piece ran small models on a 16 GB M1 MacBook and advised 32 GB. The May 2026 piece puts the floor at 16 GB of memory, with 8 GB of video memory or Apple Silicon with 16 GB or more. The March 2026 report gives 32 GB as the requirement for the Apple backend preview, and two independent reviews put 16 GB as the minimum and 32 GB as the practical baseline. Neither the README nor the quickstart states a minimum amount of memory. No source we read counts the users who hit that wall, and a count of complaints is not a failure rate, so the gauge beside this complaint reads unknown.
Concurrency is not what it was built for. Two independent reviews describe four parallel requests by default, no continuous batching and no paged cache, and say throughput flattens once real traffic arrives.
The default context window is easy to get wrong. Two sources. The August 2026 review describes a 4,096-token default that drops the front of the prompt past it without saying so. The March 2025 repository issue found a model advertising 131,072 tokens running at 2,048 until the size was set.
A release can change behaviour under you. Three sources: the August 2026 report describes a Claude Desktop integration that lasted days, was withdrawn and returned as a proxy in v0.33.0; the March 2026 report describes the Apple backend arriving as a preview for one model; and the v0.34.1 notes record a setting deprecated.
The API is unauthenticated where it listens. One source, the Go vulnerability database listing for this module, records missing authentication that lets an attacker perform model management operations, under CVE-2025-63389 and GHSA-f6mr-38g8-39rg, published 14 January 2026. We state that as the database states it.
Where reviewers split
Whether the layer should exist at all. On one side, the April 2026 Hacker News thread on a piece titled The local LLM ecosystem does not need Ollama, with 207 comments, argues that a wrapper between you and the model is unnecessary. On the other, the May 2026 ZDNET piece is written by someone who stopped using a hosted assistant for the same work. Our read: the thread is not unanimous, and its most upvoted reply credits the project with solving the first run.
How much context you get by default. One side, the August 2026 review, describes a 4,096-token default and a prompt front dropped past it without warning. The other, a repository issue from March 2025, found a model advertising 131,072 tokens running at 2,048. Our read: the default has moved between those dates, and both describe a limit that is silent rather than fixed.
Who it suits
You want open-weight models on a machine you already own, with the weights and the prompts staying there. The official pages and two independent reviews describe that setup, and the local path is $0.
You write against an OpenAI-shaped API and want the same call to reach a local model. The README, the quickstart and the August 2026 review all describe one call working at both ends.
You are one person, or a few, prototyping against a model you host. Both independent reviews that measure traffic describe a small-team load.
Who should pass
You are counting on a 16 GB laptop for anything beyond the smallest models. The February 2026 hands-on piece advises 32 GB, and the independent reviews put 16 GB as the floor.
You need throughput behind one endpoint for a team. Both independent reviews that measure traffic describe a ceiling on parallel requests.
You are about to listen on an address other machines can reach. The vulnerability listing of 14 January 2026 records missing authentication on model management operations; we report that listing, not a verdict.
One verdict a week: the most useful Master Review we finished, the complaint that kept appearing, and who should skip it. Send me the weekly verdict
Sources
- Ollama README, official, read 16 September 2026.
- Ollama quickstart, official, read 16 September 2026.
- Ollama licence file, official, read 16 September 2026.
- v0.34.1 release notes, official, 14 September 2026.
- Ollama pricing, official, read 16 September 2026.
- ZDNET, I tested local AI on my M1 Mac, editorial, 1 February 2026.
- ZDNET, I quit ChatGPT for Ollama, editorial, 26 May 2026.
- The New Stack, Connect to a Local Ollama Instance on Your LAN, editorial, 6 September 2025.
- The New Stack, Ollama taps Apple's MLX framework, news, 31 March 2026.
- The New Stack, Claude Desktop can run Qwen, DeepSeek and Kimi, news, 26 August 2026.
- GitHub REST API, ollama/ollama figures, tier 3, read 16 September 2026.
- Hacker News, The local LLM ecosystem doesn't need Ollama, forum, 16 April 2026.
- Hacker News, Ollama powered by MLX on Apple Silicon in preview, forum, 31 March 2026.
- GitHub issue 9890, Large context size breaks usability, forum, 19 March 2025.
- aifoss.dev, Ollama 2026 Review, other, 14 May 2026.
- Francis Okafor, Ollama Review: Pricing, Pros and Cons, other, 28 August 2026.
- AIwithKay, Ollama Review, other, 14 August 2026.
- Go vulnerability database, GO-2025-4251, other, 14 January 2026.
This reading covers 18 sources dated between March 2025 and 14 September 2026 and read on 16 September 2026, across official documentation, trade press, independent reviews, the repository's own figures and developer threads, synthesised with AI; nothing was installed, prompted, run or tested.
One verdict a week.
Every week, the most useful Master Review we finished: what the internet agrees on, the complaint that kept appearing, and who should skip it.