Thai AI research
Contents

Thai-capable open models: what the investor could host

Research note, October 27, 2026, by Alexander Grabowski (B4L). Sources were retrieved on October 27, 2026. Figures are cited, and our own estimates are marked.

This note covers the open models that handle Thai and that the investor could host: who makes them, how they were trained, how good they are at Thai, what their licenses allow and what hardware serves them.

In short

The landscape in one table

Sizes are given as total parameters / parameters active per token. Mixture-of-experts (MoE) models use only a fraction of their weights for each token, which makes them fast for their size. Memory figures marked est. are our estimates of the weights alone: parameters x 2 bytes at BF16, x 1 byte at 8-bit and about x 0.5 at 4-bit, before the working memory that each conversation needs (the KV cache). Prices are converted at the B4L planning rate of 33 THB per USD.

Family and maker Latest version (Oct 2026) Size (total / active) Base model License and commercial self-hosting Maker's hosted API Minimum hardware to serve
ThaiLLM (national consortium led by BDI) ThaiLLM-8B and ThaiLLM-30B base models, opened January 2026[3] 8B dense; 30.5B MoE with 8 of 128 experts active (about 3.3B, as in its Qwen base)[42][84] Qwen3-8B-Base; Qwen3-30B-A3B[2] Apache 2.0: yes[32] Free Playground and API; outputs not for commercial use without BDI's written consent[27] 8B: about 16 GB at BF16, one 24 GB GPU (est.); 30B: about 61 GB at BF16 or 17 to 20 GB at 4-bit (est.)
Typhoon (SCB 10X; service run by SCB DataX) Typhoon 2.5, API release Oct 20, 2025; no newer general LLM on Hugging Face[9][85] 30.5B / 3B; 4B dense[86][87] Qwen3 30B-A3B Instruct 2507; Qwen3 4B[88] Apache 2.0 tag, plus OpenTyphoon Terms that must be accepted: legal review needed[89] Free beta, 5 req/s and 200 req/min; no paid API[9][90] 30B: one 80 GB GPU (A100 80GB or H100)[8]; 4B: about 8 GB (est.)
OpenThai, formerly OpenThaiGPT (AIEAT with iApp Technology) OpenThai 2.0, announced Aug 27, 2026; OpenThai 2.0 Legal[80][91] 27B dense, image and text; Legal: 30B / about 3B Qwen3.8-27B; Legal: NVIDIA Nemotron-3-Nano-Omni-30B-A3B text core[73] 2.0: Apache 2.0, yes; Legal: NVIDIA Open Model Agreement, yes[74] Free web chat; weights free, no API fees[49] 2.0: one 80 GB GPU, or a 40 GB GPU at 8-bit; Legal: one 80 GB GPU, or one 24 GB GPU with the 4-bit NVFP4 build[80][73]
Pathumma (NECTEC) Pathumma-llm-4b-think-4.0.0 (August 2026); pathumma-thaillm-8b-think-3.0.0[92] 4B; 8B ThaiLLM Thai continued-pretrained base; ThaiLLM-8B[52][51] 4.0: Apache 2.0, yes; 3.0: not stated on the card AI for Thai trial, 10 calls a day; 3.0 is also on the ThaiLLM API[93][34] 4B: "servable on a single GPU"[52]; 8B: about 16 GB (est.)
THaLLE (KBTG Labs) THaLLE-0.2-ThaiLLM-8B-fa (December 2025) 8B Merge of ThaiLLM-8B, Qwen3-8B and a finance model trained on CFA exams[53] Apache 2.0: yes[54] None found; served on the ThaiLLM API[34] About 16 GB (est.)
WangchanLION (VISTEC, AI Singapore, SCB 10X) WangchanLION-v3 (July 2025)[94] 8B Llama-SEA-LION-v3-8B-IT (Llama 3.1) plus 47B Thai tokens[95][96] Llama 3.1 Community License: yes, below 700 million monthly users, with "Built with Llama" credit[97] None found About 16 GB (est.)
SEA-LION (AI Singapore) v4.8 Nemotron MoE (card updated Sep 18, 2026); v4.5 (May 2026)[98][99][100] 120B / 12B and 30B / 3B; v4.5: 27B dense and a small Gemma E2B NVIDIA Nemotron 3; Qwen3.6-27B; Gemma-4-E2B MIT: yes[99][101] Free API, 10 req/min, proof of concept only[82][102] 120B: about 120 GB at 8-bit, about 60 to 70 GB at 4-bit (est.); 27B: about 54 GB at BF16, one 80 GB GPU (est.)
SeaLLMs (Alibaba DAMO Academy) SeaLLMs-v3 (2024), still the latest LLM[103] 7B; 1.5B Not stated on the pages read SeaLLMs license: yes, separate license above 100 million monthly users[104][105] Online demo only[103] About 15 GB (est.)
OpenJAI (Jasmine Technology Solution) OpenJAI-v1.0-14B (October 2025) 14B Qwen3-14B[7] Apache 2.0: yes[106] None found About 28 GB, one 40 to 48 GB GPU (est.)
Qwen3 and Qwen3.x (Alibaba) Qwen3; Qwen3.5 to Qwen3.8 are the bases Thai teams use in 2026[34][80] 0.6B to 235B / 22B Own pretraining; Thai among 119 languages[107] Apache 2.0 (confirmed for the dense models and 30B-A3B): yes[107][89] Not researched; resellers charge about 3 / 10 THB (USD 0.09 / 0.30) per million tokens in / out for Qwen3-30B-A3B[108] 30B-A3B: one GPU (est.); 235B-A22B: at least 240 GB at FP8[109]
Llama 4 (Meta) Scout and Maverick (Apr 5, 2025) 109B / 17B; 400B / 17B Own pretraining; Thai among 12 supported languages[110] Llama 4 Community License, a custom commercial license Not researched Scout: one H100 with 4-bit; Maverick: one 8-GPU H100 server at FP8[110]
Gemma 3 (Google) Gemma 3 27B; Gemma 4 (including a 31B) is also out[100] 27B dense Own pretraining; "over 140 languages," Thai not named[111] Gemma terms: redistribution allowed, use restrictions must be passed on[112] Not researched About 54 GB at BF16, one 80 GB GPU (est.)
gpt-oss (OpenAI) gpt-oss-120b 117B / 5.1B Own pretraining; no Thai-specific claim found[113] Apache 2.0: yes[114] Not researched; resellers charge about 1 / 5 THB (USD 0.03 / 0.15) per million tokens[19] One 80 GB GPU[114]
DeepSeek V3.x (DeepSeek) V3.2 on resellers' APIs[115] 671B / 37B[116] Own pretraining; no primary source on Thai found DeepSeek Model License, "supports commercial use"[116] Not researched; about 7 / 10 THB (USD 0.21 / 0.31, discounted) per million tokens via OpenRouter 8x H200 or 8x B200 at FP8; 4x H200 at 4-bit[83]

How they were trained

Nobody in Thailand trains a language model from scratch. The national base models are continued pretraining of Alibaba's Qwen3 on about 63 billion tokens: 31.5 billion of Thai web text, 24 billion of English web text and 8 billion of curated data such as research articles and news.[1][2] The company models fine-tune either ThaiLLM or a foreign base directly. Typhoon 2.5 and OpenJAI start from Qwen3, and WangchanLION-v3 from Llama 3.1.[88][7][95] SEA-LION v4.8 and OpenThai 2.0 Legal build on NVIDIA Nemotron.[99][73] NSTDA's own illustration shows why: training an 8B model from scratch would take two decades on an eight-GPU workstation, or about 87 days on LANTA's roughly 700 GPUs.[55]

Model (maker) Work done Hardware Where Time and data
Typhoon 2, 1B to 70B (SCB 10X) Continued pretraining One node, 8x H100[6] Not stated About 44B Thai tokens
Typhoon-S-8B (SCB 10X) Post-training of ThaiLLM-8B 8x H100[47] Not stated About two days
Typhoon OCR and ASR (SCB 10X) Fine-tuning 4x H100; 2x H100[117][118] Not stated ASR: about 17 hours on 11,000 hours of Thai audio
OpenThaiGPT 1.6 72B and R1 32B (AIEAT, iApp) LoRA fine-tune 8x H100[119] GPUs donated by Siam AI[120] Not stated
OpenThai 2.0 27B (AIEAT, iApp) LoRA fine-tune 3x H100 in the spec table; 8x H100 for "training and evaluation" in the credits[80] Siam AI About 143,000 checked rows
OpenJAI-v1.0 14B (Jasmine) Fine-tune 8x H100[7] Jasmine's in-house GPU farm Under one day, about 462M tokens
Pathumma 3.0 8B and 4.0 4B (NECTEC) Post-training 16 nodes, 64x A100 40GB[51][52] LANTA supercomputer Not stated
ThaiLLM-8B and 30B (BDI consortium) Continued pretraining GPU count not disclosed LANTA[5] About 63B tokens
THaLLE-0.2 (KBTG) Model merge Can run "on hardware without GPUs"[46] KBTG Not stated
SEA-LION v3 9B (AI Singapore) Pretraining 64+8 H100[121] SingTel cloud 10 days, 200B tokens
SEA-LION v4.8 120B (AI Singapore) Post-training About 2,688 H200 GPU-hours[99] SMC H200 cloud, Singapore About 14 days on one 8-GPU node (est., 2,688 / 8 = 336 hours)

Typhoon 2.5's own training compute is not published. Together AI says in a vendor case study that SCB 10X used its GPU clusters and serverless inference to train and deploy Typhoon models, so at least part of Typhoon's work ran on rented cloud.[122]

The pattern is clear. Apart from the work on the LANTA supercomputer (ThaiLLM's continued pretraining and NECTEC's Pathumma post-training) and AI Singapore's regional pretraining on 72 H100s, every team above did its work on one 8-GPU node or less. Even the continued pretraining of a 70B model (Typhoon 2) fit on one node. We read NECTEC's use of 64 A100s as taking what LANTA offers rather than as a need, because SCB 10X post-trained the same ThaiLLM-8B base on 8 H100s in about two days.[47] Most teams rented or borrowed their GPUs (Siam AI donated OpenThai's), and Jasmine is the only team in our sources that trained on its own in-house GPUs. We conclude that a single 8-GPU server, of the kind the investor is considering, matches the scale at which Thai model work is actually done.

How good they are at Thai

All the published comparisons below are self-reported by the makers and run on their own test setups, and they often compare models of different sizes. We found no neutral leaderboard for 2026 that covers all these families on one test setup. The numbers show a direction; they do not rank the models.

The general base already scores high. On OpenThaiEval (Thai national exams), OpenThai 2.0 scores 0.842, its plain Qwen3.8-27B base 0.820, Typhoon 2.5 0.742 and Pathumma think 3.0 (8B) 0.660, all measured by iApp.[80] The Thai fine-tune adds two points over the general model it came from. Typhoon 2.5 uses only about 3B active parameters, so the comparison is not like for like.

A general model beat the Thai fine-tunes on Thai knowledge. In Jasmine's table, plain Qwen3-14B scores 57.5 on the Thai MMLU-ProX test, ahead of OpenJAI (54.7), OpenThaiGPT 1.5 14B (49.3), Typhoon 2.1 12B (45.2) and GPT-4.1-nano (39.8).[7] OpenJAI did edge out Qwen3-14B on Thai instruction following (39.4 vs 38.1), and on Thai chat (MT-Bench) all of them score about 8.0 to 8.1 except OpenThaiGPT 1.5 at 6.9.[7]

Fine-tunes win on Thai but sometimes lose overall. Typhoon-S-8B beats Qwen3-8B on SCB 10X's Thai-only suite, 71.20 vs 66.66, and on Thai chat, 7.89 vs 7.08. Across the full English and Thai suite, however, Qwen3-8B averages 54.02 against Typhoon-S's 49.99, and Qwen3-8B also follows Thai instructions better (80.47 vs 76.45).[47]

Domain fine-tunes help in their domain. KBTG's THaLLE-0.2 scores 0.779 on the Thai M3 Exam in thinking mode, against 0.706 for Qwen3-8B and 0.720 for ThaiLLM-8B-Instruct.[53] OpenThai 2.0 Legal recalls sections of the Thai Revenue Code better than Qwen3.6-35B (0.40 vs 0.36), but when the law is supplied in the prompt, both score 0.99 at citing the applicable sections of the Civil and Commercial Code.[73]

The national base adds Thai skill, mostly at the small size. ThaiLLM-8B lifts the ThaiExam average from 0.314 to 0.483 over Qwen3-8B-Base, while English MMLU dips from 0.769 to 0.757.[1] ThaiLLM-30B gains less over its Qwen base: 0.595 to 0.648.[2]

Specialists matter for reading and speech. On Thai handwriting, SCB 10X's 2B Typhoon OCR 1.5 has a character error rate of 0.054, against 0.261 for the 27B OpenThai 2.0, in iApp's own test.[80]

Vendors make larger headline claims. SCB 10X says Typhoon 2.5 "Matches GPT-4o and Claude Sonnet 4 in benchmarks," but it publishes the tables only as images and says the model is "Not yet for deep reasoning."[88] AI Singapore says Qwen-SEA-LION v4 ranked 6th of 59 on its SEA-HELM benchmark, which includes a Thai exam, and first among open models under 200B at release.[123]

In our reading, a strong recent general open model (Qwen3.x class) is already good at Thai, and on some tests better than Thai fine-tunes of similar size. Thai fine-tunes add value where the task is specifically Thai: natural Thai phrasing and culture, Thai law, finance and medicine, and above all handwriting OCR and speech recognition, where small specialist models beat large general ones. The investor should check this on the workloads it intends to serve before choosing.

Licenses and terms that matter for a commercial host

Most Thai and general weights allow a company to host them and sell the service (license texts as read in October 2026):

Typhoon needs a legal review. The Typhoon 2.5 weights are tagged Apache 2.0, but the model card adds that "By using this model, you agree to the OpenTyphoon Terms and Conditions."[89] Those terms, operated by SCB DataX Company Limited, acknowledge that models may be distributed open source and say the terms "apply to and govern the use of the Services regardless of the method of access."[81] They forbid using the Services or Output "to train, fine tune, or otherwise improve any Artificial Intelligence Models," forbid "competitive benchmarking, data scraping, or model extraction" without written consent, and are governed by Thai law in Thai courts.[81] Pulling the other way, SCB 10X's FAQ says it "claims no rights in Outputs you generate using Typhoon."[126] If the terms bind self-hosted weights, a host could not use Typhoon to generate training data for its own models and could not publish comparisons against it. We recommend that the investor have a Thai lawyer review this before any product depends on Typhoon.

ThaiLLM's weights and its Playground carry different terms. The downloadable ThaiLLM weights are Apache 2.0, and BDI calls them "open license" and open-weight.[5] The free Playground and API are different: outputs may not be used commercially without BDI's prior written consent, inputs may be used to train BDI's models, and inputs must not contain personal data.[27] A commercial service must therefore self-host the weights rather than resell the API.

Hosted APIs today

Maker Service Price and limits Fit for production Where it runs
BDI (ThaiLLM) Playground and OpenAI-compatible API; serves four Thai 8B models plus two stock Qwen models[34] Free[27]; no official rate limits found No: outputs not for commercial use without consent Compute from NT and SIAM.AI CLOUD[5]; privacy notice allows transfer to servers abroad, e.g. Singapore or the US[67]
SCB 10X (Typhoon) Free API, beta "research showcase" that collects usage data[126] 5 req/s and 200 req/min for the 30B and 12B models; OCR 20 req/min[9][127] No paid API: Together AI "API Pro" ended Dec 31, 2025; AWS API "expected" Q1 2026, still "Coming soon"[90][9] Not stated
AI Singapore (SEA-LION) Free API, keys from the Playground 10 req/min per user[82] No: proof of concept only; production via cloud partners[102] Not stated
NECTEC (Pathumma) AI for Thai platform: app, API and download[128] Trial: 10 calls a day per service; more on request[93] Paid tiers not found Not stated
AIEAT and iApp (OpenThai) Free web chat for OpenThai 2.0 Free; weights free with "no API fees"[49] Paid iApp API prices not captured Not stated
KBTG, VISTEC, DAMO, Jasmine None found (THaLLE runs on the ThaiLLM API)

Before the paid Typhoon API ended, it cost about 6.6 THB (USD 0.20) per million tokens for the 12B model and about 29 THB (USD 0.88) for the 70B model.[90] For production use, SCB 10X now points customers to Float16's hosted service or to self-hosting on rented GPUs.[90] Float16 lists H100s in its Thailand region at about 143 THB (USD 4.32) an hour.[129] Thai AI Cloud advertises a Bangkok inference API "From $0.09 per million tokens" (about 3 THB) with prompts kept in Thailand, a vendor claim that does not name the models.[130]

For the investor, the point is that no maker of a Thai model offers a paid, production-grade API hosted in Thailand as of October 2026. Third-party GPU clouds fill part of the gap, and that gap is where a Chiang Mai host would compete.

Hardware to serve them

Memory decides what fits on one GPU. The table gives the weights only; the conversation cache needs room on top.

Model Memory needed Fits on
8B dense (ThaiLLM-8B, THaLLE, Pathumma 3.0, WangchanLION) About 16 GB at BF16 (8 x 2 bytes, est.) One 24 GB GPU (est.)
30B MoE (ThaiLLM-30B, Typhoon 2.5) About 61 GB at BF16 (30.5 x 2, est.); about 17 to 20 GB at 4-bit (est.) One 80 GB GPU; SCB 10X specifies an A100 80GB or H100 for Typhoon 2.5 in production[8]
OpenThai 2.0 27B 17 GB at 4-bit, 29 GB at 8-bit (GGUF files) One 80 GB GPU at BF16, or a 40 GB GPU at 8-bit[80]
OpenThai 2.0 Legal 30B MoE About 24 GB at 4-bit One 80 GB GPU, two 40 to 48 GB GPUs, or one 24 GB GPU with NVFP4[73]
gpt-oss-120b About 61 GB at 4-bit One 80 GB GPU[114][131]
OpenThaiGPT 1.6 72B (dense) 144 GB at FP16, 72 GB at 8-bit, 36 GB at 4-bit[120] Two 80 GB GPUs at FP16 (est.)
Qwen3-235B-A22B At least 564 GB at BF16, 240 GB at FP8, 141 GB at NVFP4 4 to 8 GPUs[109]
DeepSeek V3.x 671B Native FP8 8x H200 or 8x B200 (one server); 4x H200 or 4x B200 at 4-bit[83]

Throughput is also within reach of one server. SCB 10X says one H100 serves Typhoon 2.5 at more than 3,000 tokens per second across 64 concurrent requests (a vendor claim), which works out to about 47 tokens per second per request (our arithmetic, 3,000 / 64).[88] NVIDIA's TensorRT-LLM tables show Qwen3-30B-A3B, the architecture under Typhoon 2.5 and ThaiLLM-30B, at 9,938 output tokens per second on one RTX PRO 6000 and 26,971 on one B200; these are offline ceilings and say little about interactive service.[132] In an independent test, gpt-oss-120b on one RTX PRO 6000 handled 50 concurrent prompts at about 32 milliseconds per token, roughly 30 tokens per second per user.[131] The note on hardware covers server options, prices and power.

What this means for the investor

This section gives our judgment and advice; B4L plans and researches on the investor's behalf.

  1. Host a portfolio of models. The national ThaiLLM API already works this way, with four Thai 8B fine-tunes next to two stock Qwen models.[34] We recommend that the investor plan for one strong general model (gpt-oss-120b, or a Qwen3.x MoE of 30B to 35B) for reasoning, code and English, plus Thai specialists: OpenThai 2.0 27B for Thai documents and knowledge, OpenThai 2.0 Legal for law, Typhoon 2.5 for fluent Thai chat and tool use (after the legal review), and Typhoon OCR and ASR for handwriting and speech.
  2. Size it at about one GPU per large model. gpt-oss-120b (about 61 GB), Typhoon 2.5 (about 61 GB at BF16), OpenThai 2.0 at 8-bit (a 40 GB GPU) and OpenThai 2.0 Legal at 4-bit (24 GB), sharing a GPU with Typhoon OCR 1.5 (8 to 12 GB), come to about 200 GB of weights on four GPUs of 80 to 96 GB (est.).[8] That is half of an 8-GPU server. The other half can host a larger general model or run fine-tuning, which is exactly the work every Thai team has done on one 8-GPU node.
  3. Prefer clean licenses for anything sold. We recommend that the investor build paid services on Apache 2.0 or MIT models (ThaiLLM, OpenThai 2.0, Qwen, gpt-oss, SEA-LION) by default. The CNX Vinyl plant assistant, planned in a related B4L study, assumes a self-hosted Typhoon model (see the brief); we recommend keeping a fallback based on OpenThai or ThaiLLM ready until the Typhoon terms are cleared.
  4. The market has a gap that a Chiang Mai host could fill. Thai model makers offer only free proofs of concept with rate limits, and none sells a production API from Thailand. A Chiang Mai host that serves these models under a Thai contract, with data kept on the investor's own hardware, would offer something they do not, though Thai GPU clouds such as Float16 and Thai AI Cloud (Bangkok) compete for the same customers.
  5. Evaluate models on the target workloads. The published scores are self-reported and inconsistent. We recommend that the investor test the shortlist on the Thai workloads it intends to serve (for example manuals, customer chat and forms) before choosing, bearing in mind that publishing a comparison against Typhoon may count as "competitive benchmarking" under its terms.

Open questions