Skip to content
/ airelien.dev
Go back
Aurélien AMSELLEM

My personal Olares Market — 28 apps hand-tuned for the Olares One, one click away

A custom Olares Market hand-tuned for the RTX 5090M of the Olares One. 28 ready-to-install apps: llama.cpp, vLLM, DFlash, Voxtral ASR/TTS, vision, music. How to add it to your device in 30 seconds.

Hi there.

You just got an Olares One (or you’re thinking about it), and you might wonder why I keep posting “88 t/s”, “184 t/s”, “80 t/s with DFlash” numbers on this blog. Well, all those configs live in a personal Olares Market you can add to your device in 30 seconds. Today, here’s how, plus a tour of the 28 apps inside.

What this market is

The official Olares Market is beclab/apps — the default catalog baked into your device, full of generic apps for every Olares model.

Except the One has an unusual GPU: RTX 5090 Laptop, 24 GB GDDR7, sm_120 consumer Blackwell. And every generic app leaves a huge amount of throughput on the table because they target Ampere or Ada by default.

So I built mine: orales-one-market. It’s also an official Olares market source (same API, same protocol), but every app is hand-tuned for the 5090M: Hadamard rotation (TurboQuant), q4_0 KV cache to double the context, native sm_120, NO_VMM when HAMi gets in the way, vLLM with speculative decoding wired up. In short, what I publish on the blog runs in production on my device through these apps.

How to add it

Three steps, really:

  1. Open Olares Market on your device
  2. Go to Settings → Add Source
  3. Paste this URL:
https://orales-one-market.aamsellem.workers.dev

That’s it. The market syncs every 5 minutes; apps appear in the store next to the official catalog. Install whichever you want, they run in your isolated Olares Kubernetes cluster, done.

The 28 apps at a glance

LLM inference via llama.cpp (text)

All on b8667 + TurboQuant (Hadamard rotation) + q4_0 KV cache:

Vision via llama.cpp

DFlash speculative decoding

LLM inference via vLLM

EXL3 / TabbyAPI

Voice / Audio (ASR + TTS)

Creative / Music

Why a fork instead of pushing everything upstream

Because the official market targets every Olares (mini, pro, One). Configs there are necessarily generic. On the One, that leaves 30-50% of t/s on the table compared to sm_120-specific tuning. So I keep my market in parallel for those who want the max, and I keep contributing upstream to beclab/apps when relevant (I’m actually the only external contributor on that repo).

TL;DR

URL to add in Olares Market → Settings → Add Source:

https://orales-one-market.aamsellem.workers.dev

28 ready-to-install apps, hand-tuned for the 5090M of the Olares One. Syncs every 5 minutes, updated whenever I tune a new config. If it saves you a weekend of benchmarking, mission accomplished.

See you next time!


Disclosure — If you don’t have an Olares One yet and what you see here makes you want one, ordering through this referral link gets you $400 off ($3,599 instead of $3,999) and pays me $200. I’m mentioning this out of transparency — and yes, incidentally, it helps keep the blog alive (hosting, domain, and the time I spend writing here). Link valid until late June 2026.

Share this post on:

Comments