FAQs

Frequently asked questions

Why on-device instead of cloud?

Latency, reliability, and economics. Cloud vision calls take at least 1 second end-to-end from a real phone on LTE — Captur takes 30ms. Cloud APIs need a signal your users don't always have. And you'll never run into LLM capacity constraints or unsustainable token costs.

Why not just prompt GPT-5 or Gemini with the image?

LLMs are fine upstream — for content moderation or rich multimodal reasoning. They're the wrong primitive for real-time mobile validation: 1–5 seconds per call, no offline, non-deterministic outputs, per-call cost that scales with your business. An LLM can describe a photo. Captur decides whether it's the right photo.

How is this different from Core ML or ML Kit?

Core ML is iOS-only; ML Kit is Android-focused. Captur is cross-platform from one policy — Swift, Kotlin, React Native, Flutter — and ships model updates over the air rather than through an app-store release. You define policy in business terms, not against raw model output.

What happens when the model gets it wrong?

Every false positive and false negative is captured and triggers an automated improvement cycle. The model improves with your edge cases. Updates ship over the air. Policy versions are auditable. You can override the model from your app at any time.

What about privacy and compliance?

On-device means most data never leaves the user's phone. SOC 2 Type 2 and GDPR compliant. PII can be detected and rejected before any image leaves the device.

What does pricing look like?

Committed consumption-based, with a paid pilot for new customers. We size against your expected volume and use case. Talk to us

Real-time image AIand SDKs for mobile apps

Validate every photo your users capture — in 30ms, on the device, even offline.

GDPR

Privacy by design: no unnecessary personal data in transit, and flows that align with EU requirements.

SOC 2 Type 2

Controls and processes built for enterprise security expectations, including audit-ready operations.