Below you will find DeepHow's IT requirements and Documentation.

HARDWARE:

Mobile Devices for Video Capturing:
 DeepHow will work on most smartphones, and tablets, and run on a mobile OS as listed below, although we have tested on the subset below:

• iPhone 8 and later
• iPad Air and later
• Samsung Galaxy J3 and later
• Google Pixel 3a and later

Noise Cancelling Headsets:
DeepHow should work with most noise-canceling headsets, although we have tested extensively with the following:

• BlueParrott B350-XT 

SOFTWARE:

Supported Mobile OS Versions for Video Capturing:
iOS - 13.0

Android - 10

DeepHow Mobile Apps:

DeepHow Capture App:
Android - https://play.google.com/store/apps/details?id=com.deephow.cap.global.prod 
iOS - https://apps.apple.com/us/app/deephow-cap/id6447629287

DeepHow Navigator App:
Android - https://play.google.com/store/apps/details?id=com.deephow_player_app
iOS - https://apps.apple.com/us/app/deephow-player/id1494927486?ign-mpt=uo%3D4

Supported Browser Versions:

• Chrome: 93.0.4577.82 and above
• MS Edge - 100.0.1185.36 to 100.0.1185.39 and above

Supported Operating Systems (Minimum Versions) for Desktop / Laptops:

• Windows - Windows 10 and above
• Mac OS - 10.15 and above
  
  

INFRASTRUCTURE:

Firewall Configuration:

Below are the endpoints which will need to be whitelisted and ports that will need to allow traffic. 

Ports: 
Port 80 - http (DeepHow will continue to function on 443 if 80 is unavailable)
Port 443 - https

Email Access:
IP Address - Whitelist 149.72.43.152
Originating account - Whitelist   * @deephow.com and @deephow.ai (any DeepHow email)

Endpoints:
Google Firebase Endpoints:

• www.googleapis.com
• securetoken.googleapis.com
• mobilenetworkscoring-pa.googleapis.com
• people-pa.googleapis.com
• userlocation.googleapis.com
• storage.googleapis.com
• oauthaccountmanager.googleapis.com
• safebrowsing.googleapis.com
• storage.googleapis.com/deephow-public
• ns1.google.com
• ip-api.com
• deephow-prod.firebaseio.com
• deephow-prod.firebaseapp.com
• firebasestorage.googleapis.com
• firestore.googleapis.com
• firebaselogging-pa.googleapis.com

WHITELISTING

• As we continue to improve our delivery platform, we have added additional endpoints that must be enabled to ensure there is no interruption to your platform. To make these updates, work with your IT team to whitelist the new endpoints. Questions? Reach out to our Support Team.

Please Note: If your org is using an MDM, you will need to make the necessary adjustments.

DeepHow Endpoints:

*.deephow.app - Whitelisting as a wildcard will allow all endpoints below, this is an optional step and not required if all endpoints are whitelisted. 
* If you are using IPv4 and IPv6 you will need to whitelist both. 

*Denotes new endpoints as of 7/9/2024 (Maven)
*https://chat-api.deephow.app
*https://deephow-ai-api.deephow.app

*Denotes new endpoints as of 9/1/23
* https://qrcode-server.deephow.app 
* https://transcode-cfr-processor.deephow.app 
* https://deephow-api.deephow.app
* https://language-server.deephow.app 
* https://video-server.deephow.app
* https://workflow-server.deephow.app
* https://player-server.deephow.app
* https://admin-server.deephow.app
* https://text-search-server.deephow.app
* https://deephow-external-api.deephow.app
* https://analytics-exporter-server.deephow.app
* https://bigquery-server.deephow.app
* https://views-likes-server.deephow.app
* https://cross-modality-search.deephow.app
* https://recommendation-api.deephow.app
* https://analytics-server.deephow.app 
* https://metabase.deephow.app
* https://matomo.deephow.app

The following will be deprecated.   (as indicated by --)
-- https://video-dot-deephow-prod.uc.r.appspot.com
-- https://sign-dot-deephow-prod.uc.r.appspot.com
-- https://admin-dot-deephow-prod.uc.r.appspot.com
-- https://views-likes-dot-deephow-prod.uc.r.appspot.com
-- https://search-dot-deephow-prod.uc.r.appspot.com
-- https://storage.googleapis.com/deephow-public
-- http://ip-api.com
-- https://language-dot-deephow-prod.uc.r.appspot.com/

-- https://player-dot-deephow-prod.uc.r.appspot.com/
-- https://sign-dot-deephow-prod.uc.r.appspot.com/
-- https://qrcode.deep.how/
-- https://us-central1-deephow-mvp-5b6ae.cloudfunctions.net/wordHttp/
-- https://video-processing-api-kfk24stg4a-uc.a.run.app/
-- https://bigquery-server-kfk24stg4a-uc.a.run.app/
-- https://dh-conversions.s3-us-west-2.amazonaws.com
-- https://cdn.deephow.ai
-- https://ocsp.pki.goog:80/
-- https://recommendation-api-v2-dot-deephow-prod.uc.r.appspot.com/ 
-- https://cross-modality-search-dot-deephow-prod.uc.r.appspot.com/ 
 

Bandwidth:

Mobile app sync:

• http://apple.com/  
• https://itunes.apple.com/

SSO Communication:

• http://microsoftazuread-sso.com/
• http://autologon.microsoftazuread-sso.com/
• http://aadcdn.msftauth.net/
• http://msftauthimages.net/
• http://login.microsoftonline.com/

Zscaler communication:

• http://aadcdn.msftauth.net/
• http://msftauthimages.net/
• https://data.flurry.com/
• http://www.zscaler.com/

SSO:
DeepHow currently supports SSO using OAuth 2.0. DeepHow uses OAuth to overcome the security and scalability threats of password anti-pattern, OAuth 2.0 provides a consistent, flexible identity and policy architecture.

DeepHow uses JWT tokens as claims. JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.

Encryption and/or signing certificates 
The DeepHow application currently uses encrypting and/or signing certificates. DeepHow uses SHA256 secure hash algorithm. All our data communication processes are encrypted both in transit and at rest.