What devices are supported?
Any modern iOS or Android phone. The capture flow is designed for mobile use in the field.
→
Where is client data stored?
On your own servers. VideoSnap is deployed on infrastructure you control — we do not hold, process, or have access to your clients' video data. Each deployment is fully isolated with no shared infrastructure between organisations.
→
How long can videos be?
VideoSnap is optimized for short videos—typically 30 seconds to 5 minutes—to keep capture fast and processing reliable.
→
Can we white‑label or embed VideoSnap in our product?
Yes. VideoSnap supports embedded and white‑label capture, with customizable prompts, flows, and branding.
→
How does AI processing work?
Videos can be transcribed and analyzed to extract structured fields, summaries, classifications, and checks. You choose what outputs you want and how they map to your workflow.
→
Does customer data stay under our control?
VideoSnap is designed to support controlled enterprise data flows, including options that align with client‑owned infrastructure and policy requirements.
→
How do integrations work?
Structured outputs can be routed into your existing tools and pipelines using integrations that match your workflow.
→
Can we use our own AI providers or infrastructure?
Yes. VideoSnap supports client-owned AI providers and infrastructure so processing aligns with your security and governance requirements.
→
How does MCP integration work?
In the technical layer, MCP lets VideoSnap outputs be consumed by MCP-enabled tools and agents for automation and enrichment.
→
Does it integrate with workflow tools like n8n or Node‑RED?
Yes. These are common patterns alongside webhooks and existing pipelines for routing structured outputs.
→
How do we get started?
Most teams begin with a focused pilot around one workflow (claims, inspection, or evidence capture). We agree on the capture flow, output schema, and integration pattern, then run a 2–4 week pilot with clear success criteria.
→