Thinking Machines Lab Launches DeepSeek-Inspired Inkling 975B Parameter Model


TL;DR

  • License and Access: Inkling carries Apache 2.0 terms, while Thinking Machines Lab plans to publish Inkling-Small’s weights after testing.
  • Sparse Design: The 975-billion-parameter model activates 41 billion parameters per token through a DeepSeek-V3-inspired mixture-of-experts architecture.
  • Hardware Floor: Inkling’s 16-bit weights need a minimum of 2 TB of GPU memory, while a lower-precision version needs 600 GB.
  • Adoption Test: Mixed benchmark results, paid Tinker fine-tuning and managed hosting will shape Inkling’s practical uptake.

Thinking Machines Lab released Inkling on July 15 under the Apache 2.0 license after using Kimi K2.5 for early post-training data. Open weights let developers download and adapt the trained parameters, while the training data and complete development process remain private.

Inkling has 975 billion total and 41 billion active parameters for each token. Its scale gives U.S. developers another large model they can customize, although the design openly follows DeepSeek-V3.

Inkling’s mixture-of-experts architecture routes each token through six of 256 experts, alongside two shared experts, rather than activating the full network. Selective routing cuts the computation used per token and explains how a model with 975 billion total parameters uses a much smaller active set. DeepSeek introduced the predecessor architecture in late 2024.

What Inkling Requires to Run and Customize

Sparse routing does not remove the hardware barrier. Inkling’s full 16-bit checkpoint requires a GPU cluster with a minimum of 2 TB of aggregate GPU memory, equivalent to eight Nvidia B300 graphics processing units or 16 H200 units. A lower-precision edition cuts the minimum to 600 GB and can run on four B300 or eight H200 units, reducing memory demand without establishing identical accuracy.

Local operation still requires an inference deployment framework such as SGLang, vLLM, TokenSpeed, Unsloth or Hugging Face, adding software integration work to the hardware bill. Even the smaller footprint remains beyond a typical workstation, leaving self-hosting to organizations with costly multi-accelerator systems.

Inkling accepts text, image and audio as inputs but returns only text for coding, tool use and retrieval-augmented generation systems. Thinking Machines Lab trained Inkling from scratch on Nvidia GB300 NVL72 systems using 45 trillion training tokens spanning text, images, audio and video, but training scale does not guarantee reliable answers.

Developers can download the weights from Hugging Face, fine-tune Inkling through Thinking Machines Lab’s paid Tinker platform, or use Inkling Playground. Databricks made the model available through Unity AI Gateway for enterprise data, agent and coding workflows, while third-party inference providers offer another path for teams without local hardware. Downloading the weights gives adopters more control, whereas managed access changes who operates the accelerators without reducing Inkling’s underlying memory demand.