OpenJev · OpenJev

OpenJev GGUF

Verified by Badgr · Serve

OpenJev GGUF is a 27B chat and text-generation model available through supported Badgr execution routes.

Last validated or meaningfully updated: 2026-10-10

Chat

✓ Verified by Badgr · llama.cpp · Serve

Last verified 2026-10-10

badgr serve --runtime llama.cpp --hf-repo openjev/openjev-GGUF --hf-file OpenJev-Q4_K_M.gguf --gpu RTX_4090 --funding paid --max-cost 1.5 --env LLAMA_ARG_N_GPU_LAYERS=999 --env LLAMA_ARG_CTX_SIZE=16384 --env LLAMA_ARG_N_PARALLEL=2
GPU
NVIDIA GeForce RTX 4090Reported by the provider, not confirmed inside the container
Time to verified
362s
Deployment
dep-7780d1fffb
  • ✓ llama-server loaded the 16.5 GB Q4_K_M file with the model card's settings (-ngl 999, -c 16384, -np 2)
  • ✓ The model card's own decision prompt returned the correct letter
  • ✓ Loop AI's helper/shim.py, unmodified with default settings, answered 3 of 3 choice questions correctly at 0.998-0.999 confidence
  • ✓ A combined choice, yes/no and score request returned in 1.5 s
  • ✓ final_state = VERIFIED
  • ✓ Teardown completed

Weights are licensed CC BY-NC 4.0 (research and non-commercial use); a commercial licence comes from Loop AI. The shim ran on a separate machine against the endpoint's OpenAI-compatible API. Three hand-written questions are a smoke test, not an accuracy measurement; the model card reports 82.8% on 1,789 rows for this file.

Raw evidence
final_state=VERIFIED failure_class=None providers_tried=1 spend_usd=0.0443 elapsed=362.4s
shim: complete-purchase click_place_order p=0.9994 | enter-discount-code click_coupon_field p=0.9994 | search-flights type_destination p=0.9984

Run from Badgr's local development environment. Documents that this deployment path works end-to-end for this model.

Availability

Not yet Badgr AI API

Not currently validated

✓ Dedicated endpoint

Available through Badgr

✓ Custom GPU deployment

Available through Badgr

Deployment profile

Architecture
qwen35 (GGUF)
Licence
CC-BY-NC-4.0
Minimum VRAM
~58GB
Context
16K tokens

Recommended: A100 80GB. VRAM is an estimate and increases with context, cache, concurrency, and runtime overhead.

Model identity

Base model
openjev/openjev
Languages
en
Updated
4 days ago
HuggingFace revision
24a4776974

Popularity and trust

Downloads (last month)

8.7K

Likes

12

Spaces using this model

2

Files and formats

Weight formats

GGUF

Repository files

16

Chat template

Not detected

GPU deployment scenarios

Estimated from parameter count and quantisation. Will switch to “Verified by Badgr” once a real run backs a tier.

Testing

A100 80GB

Short context, low concurrency

Small production

H100 80GB

8K context, 1-4 concurrent requests

Higher throughput

H200 141GB

32K context, continuous batching

Large production

A100 80GB

Higher concurrency

Estimated — multimodal inputs, long context, and concurrency all increase real VRAM use beyond this estimate.

Also runs well on H100 80GB, H200 141GB. Available in United States, Europe, Asia Pacific.

Serving compatibility

RuntimeStatusNotes
vLLMEstimatedUsed for Badgr dedicated endpoints
TransformersUnknownBasic fallback
llama.cppVerified by BadgrConfirmed by a real badgr serve run (deployment dep-7780d1fffb)
SGLangUnknownNot evaluated
OllamaUnknownNot evaluated
DiffusersUnknownNot evaluated
PyTorchUnknownNot evaluated
TensorRT-LLMUnknownConversion may be required
TGIUnknownNot evaluated

Ready-to-run Badgr configurations

Quick test

badgr serve openjev/openjev-GGUF --max-cost 2

Validated dedicated endpoint command

badgr serve openjev/openjev-GGUF --gpu A100 80GB --max-cost 10

Advanced configuration (defaults to automatic)

  • Runtime
  • Quantisation
  • GPU and GPU count
  • Context length
  • Maximum concurrency
  • Region
  • Maximum hourly spend
  • Persistent or capped runtime

Estimated pricing

Provider estimate: cold start

3–8 min

Provider estimate: endpoint cost

$1.40 – $1.40/hr

Idle cost

$0 when stopped

Per-token throughput cost is not shown here: Badgr has not benchmarked this model yet, and this page does not display figures it cannot back with real data.

Recommended Badgr routes

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: Good

Last checked: Live marketplace price not available yet

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: Live marketplace price not available yet

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: Live marketplace price not available yet

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: Good

Last checked: Live marketplace price not available yet

A100 80GB · Europe

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: Live marketplace price not available yet

A100 80GB · Asia Pacific

Estimated

starting from $1.40/hr

Badgr estimated starting price

Best for

LoRA Training, vLLM Endpoint, Qwen 2.5 32B Instruct

Startup: 3–8 min

Reliability: High

Last checked: Live marketplace price not available yet

Known limitations

  • Memory use increases with context length and concurrency.

Related troubleshooting