Name: Immutis Verification Protocol
Brand: Immutis
Availability: InStock

Question 1

What does Immutis do?

Accepted Answer

Immutis cryptographically verifies that photos of shipments, warehouse inspections, and quality checks came from a registered device and were not edited after capture. Logistics companies, warehouses, and manufacturers call our API to prove evidence is authentic.

Question 2

Who is Immutis for?

Accepted Answer

Operations teams, warehouse managers, QC supervisors, and logistics companies who need to prove what happened at handover, during inspection, or at quality check. If you need evidence that holds up in disputes or audits, Immutis proves it.

Question 3

How is this different from cloud storage?

Accepted Answer

Cloud storage just saves files. We cryptographically bind each photo to the device hardware, GPS location, timestamp, and operator at the moment of capture. Edit the file afterward and the signature no longer matches — revealing tampering instantly.

Question 4

Can I verify data without using the capture SDK?

Accepted Answer

Yes. POST /v1/verify accepts any file. We compute the SHA-256 hash and check if it matches a known trusted capture. If the file was not captured through our SDK, you still get a hash and can compare it against your own records.

Question 5

What devices are supported?

Accepted Answer

The Trust Anchor SDK supports iOS 15+ (Secure Enclave) and Android 8+ (Keystore). No extra hardware required — it uses the phone or tablet's built-in secure element. Your warehouse staff and delivery drivers already have these devices.

Question 6

How fast is the API?

Accepted Answer

Average response time is under 50ms. The verification is pure cryptographic math — no ML inference, no external API calls, no delays. Integrates seamlessly into your existing logistics workflows.

Question 7

How do I integrate it?

Accepted Answer

Our REST API includes a POST /v1/verify endpoint. Send a file or capture ID. Get a JSON result. We also offer webhooks so your system is notified the moment verification completes — perfect for automated claims processing.

Question 8

What is the confidence score?

Accepted Answer

Confidence is computed from device attestation level, signature validity, and time since capture. Hardware attestation + valid signature = 0.98+. Software-only keys score lower. Rejected captures score 0. Use this to automate which captures need manual review.

Question 9

What happens when I hit my usage limit?

Accepted Answer

We return a 429 status with a clear message. You can upgrade instantly in the dashboard. No hard limits — we will not drop your traffic unexpectedly.

Question 10

Do you support webhooks?

Accepted Answer

Yes. Configure a webhook URL in your dashboard and we will POST verification events to it in real time. Useful for triggering automated claims workflows or updating your logistics system.

Question 11

Can I self-host or run on-premise?

Accepted Answer

Not yet. We are fully managed on Supabase + Render. Enterprise customers can request a dedicated instance with custom deployment options.

Question 12

What languages do you support?

Accepted Answer

Any language that can make HTTP requests. We provide SDKs for iOS (Swift) and Android (Kotlin). The REST API is language-agnostic.

Question 13

How does billing work?

Accepted Answer

Usage-based. You pay per verification call. Starter tier: 1,000 free/mo. Growth: $49/mo for 50,000. Scale: $199/mo for 250,000. Enterprise: custom. Overage is $0.002 per call.

Question 14

Is my data secure?

Accepted Answer

Every capture is signed by the device's hardware security module. Data is encrypted at rest (AES-256) and in transit (TLS 1.3). Tenant isolation via Supabase Row Level Security.

Question 15

Do you store the actual files?

Accepted Answer

Yes, for captures made through our SDK. Files are stored encrypted in Supabase Storage. You control retention. For API-only verifications, we only store the hash and result.

Frequently Asked Questions