Deploy Self Inspection your way
White-label hosted, embedded SDK, or API-only. Concrete requirements, timelines, and limits for each - written for the person who has to make it fit the existing stack.
3
Deployment models - hosted, embedded, or API-only
1
Pipeline behind all three - same AI detection and expert review
0
Inbound firewall changes - HTTPS outbound only
Self Inspection deploys in one of three ways
All three run against the same AI detection and expert review pipeline; the difference is who owns the interface.
A branded capture flow on your own domain, hosted by Self Inspection, live in under one week.
How long does it take to deploy?
Deployment time depends on the integration approach. White-label hosted deployments take under one week. Embedded SDK deployments take 2–6 weeks depending on your app's release cycle. API-only deployments depend on your engineering team's capacity, but typically take 4–8 weeks.
What infrastructure changes do we need?
None on the inbound side. Self Inspection runs in the cloud and requires HTTPS outbound to api.selfinspection.com from your servers (if doing API integration). For browser-based capture, no firewall changes are required. We support standard SSO via SAML 2.0 and OIDC on Enterprise plans.
Three ways to deploy Self Inspection
Pick by how much of the interface you want to own, not by how sophisticated the option sounds. Most customers start with the standard hosted flow and move to SDK or API later if they need to.
White-label hosted
Under one week- Best for
- Teams that want inspections running now, with their brand on the flow
- You build
- Nothing. Supply brand assets and a DNS record
Embedded SDK
2–6 weeks- Best for
- Products with an existing mobile or web app users already open
- You build
- The surrounding screens; the SDK provides capture
API-only
4–8 weeks- Best for
- Teams with their own capture flow or a strong UI opinion
- You build
- The whole interface, against our REST API
Migration from your current inspection process
Real deployments are rarely greenfield. There is an existing process, existing history, and people who are good at the old way.
Infrastructure requirements
The short version: nothing inbound, no appliance, no VPN. Longer version below.
HTTPS outbound to api.selfinspection.com from your servers, for API integrations only. No inbound firewall changes, and browser-based capture needs no network work at all.
Bring your architecture questions to the demo
Twenty minutes with someone who can answer them, not route them.
FAQ
Yes. White-label deployment is included on Enterprise plans. You get a custom-branded landing page, capture flow, and report PDF on a custom domain (e.g., inspect.yourbrand.com). The capture flow structure is fixed for AI accuracy reasons, but colors, logos, and copy are fully customizable.
Yes. Native iOS (Swift) and Android (Kotlin) SDKs let you embed the Self Inspection capture flow inside your existing mobile app. A JavaScript SDK is also available for web embedding. SDK access is included on Volume and Enterprise plans.
On-premises deployment is not currently supported. The AI model and expert review pool require cloud-hosted infrastructure to deliver the speed and accuracy guarantees. Customers with strict data residency requirements can choose US-only or EU-only data residency.
Yes. All Self Inspection accounts include a sandbox with the same API surface as production but using test inspection data. Sandbox inspections are free and don't count against monthly volume.