Skip to content

For AI running on devices and in the cloud.

Know where your AI struggles in the real world.

See where model behavior changes across releases, runtimes, and devices. Inspect captured inputs, outputs, and feedback, then turn selected examples into datasets for evaluation and training.

Input/output capture is optional · No credit card required

Pick a modality
product-scanner · v4.2Production
Cloud fallback6%up 4 pts
Fleet confidence0.87down 0.03Fleet avg
Runtime errors2.1%no change
p95 latency340msno change

Product recognition dropped on one iPhone cohort.

Mean prediction confidence · daily

7 days agomodel v4.2 rollouttoday

iPhone 14 · Neural Engine 1,240 scans0.44
iPhone 14 · CPU 9,860 scans0.90
Affected cohort sent more requests to cloud-classifier-v3Fallback requests +22%

Confidence by class: bottle 0.38 boxed item 0.41

Observed after the model rollout · cause not yet confirmedInspect affected devices ↓
Works with
Core MLMLXTFLiteONNX RuntimeML KitExecuTorchllama.cpp
OpenAIAnthropicGemini

See the product

From a bad prediction to a better model.

WildEdge flags models that drift from their own history. This one lost 17% confidence after an app update, with no crash and no error.

View full screenshot ↗
WildEdge overview flagging the effv2s-brand-s0 model with confidence down 17.4 percent, next to the latest captured car photos

Integrations

Connect your models.

Add an SDK to collect inference telemetry. Enable input and output capture when you need examples for review.

Python
uv add wildedge-sdk

Transformers · PyTorch · TensorFlow · Keras · ONNX · MLX · llama.cpp · Ultralytics · timm · OpenAI · Anthropic · OpenAI-compatible APIs

Android
implementation("dev.wildedge:wildedge-android:0.1.0")

TFLite · Play Services TFLite · ONNX Runtime · ML Kit · LiteRT · LiteRT LLM · Gemini · Custom models

iOS & macOS
.package(url: "https://github.com/wild-edge/wildedge-swift.git", from: "1.1.0")

Core ML · TFLite · ONNX Runtime · ML Kit · ExecuTorch · llama.cpp · OpenRouter · Gemini · Custom models

Read the integration docs ↗

What happens on real devices

The same model behaves differently across devices.

Where your model actually runs
NNAPI GPU CPU
ChipsetExecution pathp95 latency
Tensor G3Pixel 8, Pixel 8 Pro 94% 180ms
Snapdragon 8 Gen 2Galaxy S23, OnePlus 11 91% 210ms
Tensor G2Pixel 7, Pixel 7a 92% 340ms
Exynos 1380Galaxy A54, Galaxy M54 88% 520ms
The bottom two chipsets can run on NNAPI. Most of the time they fall back to CPU, and take nearly 3x longer.
See what the SDK records

Work with your coding agent

From production failure to the code behind it.

Give your coding agent access to WildEdge production telemetry. It can investigate affected devices, inspect traces, and connect runtime failures to your code.

Connect your coding agent Powered by WildEdge MCP
coding agent

› Our brand classifier looks worse lately. What changed, and where?

✓ Compared model versions by device
✓ Split A15 iPhones by accelerator
✓ Checked latency and user feedback

App 1.38 shipped effv2s-brand-s0 v12. The drop only happens on A15 iPhones running v12 on the Neural Engine.

A15 confidencev11v12
Neural Engine0.770.31
GPU0.760.77

Latency is unchanged, so the model runs normally and returns wrong answers. User feedback on these phones rose from 7% to 28% of scans.

Likely cause: a v12 layer that the A15 Neural Engine computes incorrectly in fp16. Quick fix: set computeUnits = .cpuAndGPU for v12 on iPhone14,x, then compare layer outputs on an A15 device.

Evidence: version × device × accelerator · feedback rate · latency

Device to cloud

Follow one request across device and cloud.

When a local model hands work to a cloud model, inspect both steps in the same trace. See where time was spent and connect the response to the recorded user outcome.

Compare WildEdge with other tools
Example tracetr_01J8Y2Q41.04 s total
  1. Device requestiPhone 14 · iOS 18.1received
  2. Core ML inferenceproduct-scanner v4.2 · Neural Engine0.44 confidence
  3. Cloud fallbackcloud-classifier-v3 · eu-central842 ms
  4. User outcomesuggestion shown in applicationaccepted
Model v4.2Raw input not retainedReview-ready

Private deployment

Deploy WildEdge where your data lives.

Run WildEdge on-premises or in your own cloud. Structured records use an open table format, with captured inputs and outputs in object storage.

Input/output capture is optional On-premises deployment Bring your own cloud Explore compliance evidence ↗

Pricing

Try WildEdge free. Choose a plan as your usage and deployment needs grow.

Free

$0

No credit card required

  • 3 projects
  • 100k events / month
  • 14-day telemetry history
  • 250 MB of input/output uploads / month
  • 14-day captured-file retention
  • Dataset creation, label review & export
Start Free

Pro

$299 / month

Billed monthly

  • Unlimited projects
  • 1M events / month
  • 90-day telemetry history
  • 10 GB of input/output uploads / month
  • 90-day captured-file retention
  • Dataset creation, label review & export
  • Email support
Start Free

Enterprise

Let’s talk

For private deployments and scale

  • Everything in Pro
  • VPC, on-premises & air-gapped options
  • Your own object storage
  • Custom retention, SSO & audit logs
  • Dedicated support & SLA
Explore Enterprise

Need more upload capacity? Talk to us about additional capacity ↗

Event and upload allowances are shared across your company’s projects and reset each monthly usage period. Input and output files both count toward the upload allowance. Adding a file to a dataset does not extend its retention; export files you need to keep before they expire. Training integrations require an account with the destination provider.