Ornith 1.5 122B

Ornith AI's model, with open weights. Forcebench has run it in 1 configuration on the Local board. API is models reached through a hosted service; Local, models served on Forcebench’s own hardware.

On the Local board

Models served on Forcebench’s own hardware. Ornith 1.5 122B is ranked by its one configuration: the 14th-highest score of 16 models, not clearly different from 6 other models. Scores are within 3 attempts (c@3) with 95% intervals; each configuration is compared with the highest-scoring one by whether their 95% intervals overlap. Every configuration on the board →

33%
within 3 attempts (c@3), 95% CI 28–38 · thinking on · 14th-highest score of 16 models, not clearly different from 6 other models
13k
output tokens per task · median 8.8k, p90 33k
2007 s
median per task, every attempt counted, on 1× NVIDIA DGX Spark (GB10, 128 GB) · 90th percentile 9098 s
20%
no answer within the 32,768-token budget
Every configuration of Ornith 1.5 122B on the Local board
ConfigurationRank all configsWithin 3 attempts c@3 · 95% CITokens mean · median · p90No answerLatency median per task, every attempt counted
NVFP4 experts, FP8 attention (NVIDIA ModelOpt) · vLLM · thinking on · 1× NVIDIA DGX Spark (GB10, 128 GB)highest score26
33%95% CI 28–38
13k8.8k · 33k20%2007 s

Latency depends on the hardware: compare it only between configurations on the same hardware.

Suites, at its highest-scoring configuration
thinking on · NVFP4 experts, FP8 attention (NVIDIA ModelOpt) · vLLM · 1× NVIDIA DGX Spark (GB10, 128 GB): within 3 attempts (c@3) on each suite with 95% intervals, against the median of the Local board's models, each at its highest-scoring configuration.
  • 95% interval
  • Local board median
40%, 95% interval 22–61%
28%, 95% interval 13–51%
35%, 95% interval 17–59%
35%, 95% interval 18–57%
0%, 95% interval 0–18%
11%, 95% interval 3–33%
11%, 95% interval 3–33%
58%, 95% interval 36–77%
72%, 95% interval 49–88%
39%, 95% interval 20–61%
28%, 95% interval 13–51%
40%, 95% interval 20–64%
11%, 95% interval 3–33%
65%, 95% interval 43–82%
17%, 95% interval 6–39%
    Show the numbers
    Per-suite scores of Ornith 1.5 122B's highest-scoring configuration on the Local board, with the board's median
    Suitec@3 95% CILocal medianTasks
    Apex
    40%95% CI 22–61
    70%20
    Salesforce APIs
    28%95% CI 13–51
    42%18
    CI/CD
    35%95% CI 17–59
    44%17
    Salesforce CLI
    35%95% CI 18–57
    38%20
    Salesforce docs
    0%95% CI 0–18
    12%17
    fflib Enterprise Patterns
    11%95% CI 3–33
    17%18
    Flow
    11%95% CI 3–33
    17%18
    Governor limits & pushback
    58%95% CI 36–77
    76%19
    Lightning Web Components
    72%95% CI 49–88
    83%18
    Nonprofit Success Pack
    39%95% CI 20–61
    56%18
    Packaging
    28%95% CI 13–51
    28%18
    Permissions & access
    40%95% CI 20–64
    57%15
    Scratch org definitions
    11%95% CI 3–33
    11%18
    SOQL
    65%95% CI 43–82
    85%20
    Trigger Actions Framework
    17%95% CI 6–39
    42%18

    In the studies

    Want this for your team?

    Azul Labs runs Forcebench privately for two kinds of Salesforce team.

    Choosing a model to run yourself?

    A private benchmark of your shortlist

    Open-weight models at the quantisations and reasoning efforts you could run on infrastructure you control, tested on your kind of Salesforce work, with a written recommendation.

    • Private tasks written from your work only ever run on local models; they are never sent to an API.
    • Re-testing after any change of model, quantisation or engine is available.
    • Typical turnaround is 2–3 weeks; large models take about a day of machine time per configuration.

    Building or buying a Salesforce AI tool?

    A private evaluation of your tool

    Your tool on held-out tasks it has never seen, against API baselines (models reached through a hosted service) and Local ones (served on Forcebench’s own hardware), with a written report on where it holds up and where it fails.

    • It can start as a smaller pilot, about 30 held-out tasks with your tool against two baselines, before a full evaluation.
    • Repeat evaluations after your releases are available.
    • Typical turnaround is 2–3 weeks.

    Fixed fee, quoted up front. The quote depends on the number of tasks and the number of models, tools or configurations tested.

    Or email leo@azl.au · azl.au