Today IFM is releasing K2 Horizon, a connected fleet of six models: 375B-A23B, 36B-A4B, 32B, 7B, 3.7B, and 0.9B. Across reasoning, mathematics, coding, agentic tasks, and general capabilities, K2 Horizon delivers top-tier performance in every size class—with the 0.9B, 3.7B, and 7B models setting new state of the art at their respective scales.

We are releasing intermediate checkpoints, training data or detailed data-construction recipes, open architecture, mixture compositions, training code, configurations, fine-grained logs, evaluation results, and final weights.

The models and code are released under the Apache 2.0 license. Datasets are released under their applicable licenses, such as ODC-BY; We disclose how the data was constructed and mixed when redistribution is not possible.

  • Hazzard@lemmy.zip
    link
    fedilink
    English
    arrow-up
    8
    ·
    6 days ago

    Intriguing. Should be interesting to compare this to Qwen3.8 (27B). I’ve been plenty impressed with Qwen’s ability, but boy does it like to overthink things, even after getting it off the default xhigh reasoning, it’ll take 20 minutes to plan something, thinking so much it’ll have to compress its context multiple times to reach a single answer. The quality of the answer is great, but there has to be a middle ground.

    • hirihit640@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 days ago

      We disclose how the data was constructed and mixed when redistribution is not possible.

      So sounds like some data is unreleased, I wonder how much.

      • inari@piefed.zip
        link
        fedilink
        English
        arrow-up
        6
        ·
        6 days ago

        My guess is they don’t really have the rights to release data copyrighted by others.

    • robber@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 days ago

      There is the Swiss project Apertus AI, and I think I’ve read about others but don’t remember the names.

      That being said, if the benchmarks translate to real utility, it is the first competitive open source model, I’d say.

  • lps2@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 days ago

    Can’t wait for it to hit ollama so I can easily add it into my flow. I really need a better ollama alternative where I can easily download, manage, and run gguf locally and tie it in with opencode, zed, and open-webui

      • lps2@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 days ago

        This was the article that had me looking for alternatives but nothing seems to have the same tight integration that ollama has with the 3 tools I use the most

          • lps2@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 days ago

            As far as I can tell, open-webui doesn’t have a way to manage gguf models via llama.cpp / llama-swap. It can leverage the models just not a great experience managing (downloading, deleting, etc). I can definitely adjust my workflow to use another tool, it just means an additional hurdle compared to my current flow but it sounds like it’s worth it from a performance standpoint

            • yellow [she/her]@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              2
              ·
              5 days ago

              Eh, are you really using that many new models where sshing into your server / cding into your model folder, wgetting a url and configuring your interfaces every now and then is that much of an issue? I can’t imagine using more than like one or two new models a month unless there’s some insane string of releases or something.

              Also, I mean, everyone’s setup is different, but there’s a significant amount of performance you’re potentially leaving on the table by not using llama.cpp, potentially in the double-digit percentages. (Plus, if you have a fairly recent Nvidia setup and are willing to wait a bit for the latest models, ik_llama.cpp is a fantastic fork that I’ve found can get way better performance on most models than even llama.cpp.)

    • Shimitar@downonthestreet.eu
      link
      fedilink
      English
      arrow-up
      13
      ·
      6 days ago

      Llama.cpp of course! After I did the switch, never looked back. Add llama-swap in front of you switch between models often.

      • e0qdk@reddthat.com
        link
        fedilink
        English
        arrow-up
        9
        ·
        6 days ago

        llama-server has router mode built-in; you don’t need separate software to swap models. I keep a list of my models in a presets.ini file.

        • Shimitar@downonthestreet.eu
          link
          fedilink
          English
          arrow-up
          3
          ·
          6 days ago

          Yes but llama server does not unload models to fit a different model. At least, didn’t managed to have just llama.cpp swap between models that fill up my vram… The second one would fail load.

          • BeefAndPoultry@lemmus.org
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 days ago

            You can set a maximum number of slots and it will automatically unload to load a different model, I just set mine to 1 slot so there’s only 1 model loaded at a time

          • e0qdk@reddthat.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 days ago

            Ah. I POST to ‘/models/unload’ when I switch models as part of my tooling – if llama-swap is doing that for you, then I get why you’d want it.

            • Shimitar@downonthestreet.eu
              link
              fedilink
              English
              arrow-up
              3
              ·
              6 days ago

              Yes, llama swap also give you a pretty web based statistics of all the calls and runs for every model with t/s and more statistics.

              It’s pretty neat… You can also load and unload models manually, define groups for models that fit together in vram and so on.

              It gives you that automation that people coming from ollama are used to.

              under the hood all it does is running llama serve. You convert your models.ini to a yaml file 1:1 (plus a few more flexibility).