Latest

An open-weights, Apache 2.0 robot control model removes the licensing barriers that usually come with robotics foundation models, letting teams self-host and modify freely. Robotics engineers and embodied-AI researchers can fine-tune Praxis-1 on their own hardware instead of licensing closed systems. Compared with closed offerings from rivals such as Physical Intelligence, this gives startups a low-cost starting point for building real-world robot behaviour.

Official accountRunway ML@runwaymlSource

The move from tissue-level averages to single-cell-type resolution changes what genetics labs can do with variant interpretation: rare-disease teams can now pinpoint which specific cell type a variant disrupts rather than relying on broad tissue signals. Computational biologists and genomics researchers can start testing it immediately via the free AlphaGenome API for non-commercial work. Compared with prior variant-effect predictors, the conditional architecture and cross-modal imputation reduce the need to run every assay before planning follow-up experiments.

Cell-specific variant interpretation is a bottleneck in translating genome sequencing into clinical insight, and AlphaGenome 2 targets exactly that gap. Genomics labs, computational biologists, and biotech teams evaluating disease-causing mutations can use it to prioritise variants by affected tissue. Compared with AlphaFold, which resolved protein structure, this model moves DeepMind's tooling upstream into gene regulation, a space where competitors like Enformer and Evotec partnerships have been active.

Official accountGoogle DeepMind@GoogleDeepMindSource

The interesting shift is that the model's value comes from context — the same variant can be scored across many cell types, enabling tissue-aware interpretation of disease-linked variants that single-context tools miss. Computational biologists, genetics labs and variant-interpretation teams can start experimenting immediately through the free Colab tutorials without infrastructure setup. Commercial users are excluded from the current licence, so biotech teams should treat it as a research preview and watch how DeepMind prices commercial access later.

Official accountGoogle DeepMind@GoogleDeepMindSource

Adapting to a new experimental context from a few dozen cells changes the cost calculus for labs that previously needed large datasets or custom training to study cell-specific DNA effects. Experimental biologists working on immunology, inflammatory disease or blood development are the direct audience, since those are the use cases DeepMind named. Developers of computational biology pipelines should compare this against bespoke variant-effect models built per experiment.

Official accountGoogle DeepMind@GoogleDeepMindSource

The interesting signal is that RAG value here comes from multi-tenant access control and compute scaling on GKE, not raw vector search speed — criteria enterprise buyers often overlook. QA leads and platform teams evaluating retrieval infrastructure for internal LLM tools can study DeNA's published architecture write-up. Japan enterprise adoption also offers a reference point for teams in ASEAN and China weighing Milvus against managed alternatives like Zilliz Cloud or pgvector.

Milvus@milvusioSource

The non-obvious lesson is that stripping LLM calls out of steps where rules suffice was as important as adding retrieval, a design decision most teams skip. QA leads and engineering managers designing LLM pipelines for internal tooling can use the flow-by-flow review method as a checklist. Japan's DeNA is not an ASEAN player, but the closest concrete comparison is the 50% effort reduction benchmark, which teams can measure their own QA automation against.

Milvus@milvusioSource

The efficiency gap is the real story: verification work that historically took decades of expert effort was compressed into weeks by prover agents, suggesting formal methods may spread beyond niche kernels into mainstream security libraries. Security engineers and cryptography teams should watch this workflow, since spec-plus-prover pipelines could be applied to their own critical code. The check is still delegated to Lean, so trust rests on spec quality rather than the model alone.

elvis@omarsar0Source

The non-obvious insight is that gateway adoption is driven less by convenience than by switching costs: without one, changing model providers means rewriting adapters and fallback logic across the codebase. Backend and platform engineers building multi-model applications should evaluate gateways before adding their second provider. The examples span OpenAI, Anthropic, Gemini, Qwen and DeepSeek, which maps directly onto the provider mix most teams in China and Southeast Asia juggle when balancing cost and capability.

掘金本周最热@苏三说技术Source