DFRTI has no relationship with Cellebrite and has not tested Inseyets. What follows is drawn from Cellebrite's public product pages and its October 2024 Inseyets FAQ, read on 2 November 2026, and it should be understood as the vendor's own description. Where we add our own view we say so. Independent, published comparisons of Inseyets against the older products were not found during this review, so none are cited.

On its website Cellebrite describes Inseyets as its flagship digital forensics solution within what it calls the Case-to-Closure platform. The products menu lists UFED, Physical Analyzer, Kiosk, CFID, Reader and C-TEK under the Inseyets heading. Cellebrite Premium sits outside that list under its own heading, and Cellebrite Guardian is presented as a complement to Inseyets rather than part of it.

The Names and What They Now Mean

Each entry gives the name as Cellebrite's pages use it today and the role the vendor assigns to it.

C
Cellebrite PA Cloud (earlier UFED Cloud)
Collection of cloud-account data using device-based tokens or known credentials, lawfully obtained. The FAQ lists it as part of the Inseyets bundle under the name PA Cloud.
Cellebrite Physical Analyzer (Inseyets.PA)
The decoding and analysis engine. Cellebrite's FAQ describes Inseyets.PA as version 10.x, built on a database for large data volumes, with features such as geolocation semantics and media origin. It states that Inseyets.PA and Physical Analyzer 7 share the same decoding abilities, with the Inseyets offering adding cloud and crypto features.
Cellebrite Premium
Cellebrite's offering for lawfully unlocking, decrypting and extracting from locked iOS and Android devices, including what it calls AFU and BFU access. The page shows it deployed alongside UFED. In the FAQ, Inseyets is described as unlock-ready with the unlocks package purchased separately.
Cellebrite Reader
The free review application for reports shared from Physical Analyzer, with search, filtering, timeline and bookmarking. It lets investigators and lawyers review evidence without a licensed workstation.
Cellebrite UFED (Inseyets.UFED)
The access and extraction engine of the suite. UFED stands for Universal Forensic Extraction Device. Cellebrite's page describes full file system extraction from a wide range of iOS and Android devices, triage, field and lab deployment and sending extractions on for decoding. The FAQ shows it was once a product line in its own right, sold as UFED 4PC software and as Touch hardware.
S
Streamline, Autonomy, Quick View, Triage, Commander
Workflow components the FAQ bundles into Inseyets: one-click processing from extraction to a UFDR report, automated multi-device processing, a pre-extraction preview, device prioritisation and central licence and permission management.

What Is Current and What Is in Transition

Cellebrite's FAQ answers the upgrade question directly. UFED 4PC users need an upgrade kit and a Cellebrite Max dongle. Touch 2 hardware is not supported by Inseyets, and Cellebrite recommends moving to a computer-based kit. Touch 3 needs an upgrade kit and the FAQ warns that it is not optimal and that some capabilities will not work as well. The FAQ also notes that the Turbo Link adapter was formerly known as the Cheetah adapter, which explains a name students will meet in older training material. Inseyets.PA 10.x may be explored on an existing licence, but only its decoding and analysis features will work without the full Inseyets purchase.

What we could not find on cellebrite.com is a published end-of-support date for Physical Analyzer 7 or for UFED 4PC. Cellebrite's own product update pages for 7.x releases remain online. Our reading, and it is only our reading, is that Physical Analyzer 7 and UFED 4PC are in transition rather than retired: still in use in many laboratories, still decoding what Inseyets.PA decodes, but no longer the products Cellebrite leads with. Laboratories that depend on them should ask their Cellebrite account contact for the support position in writing rather than rely on this article.

How to Write the Name in a Report

Product renaming is where reports go wrong. A reviewer will compare what you wrote with what the tool's own screens show.

  • Copy the product name and version from the About screen of the tool you actually ran, for example Cellebrite Physical Analyzer 7.x or Cellebrite Inseyets.PA 10.x, and give the full build number.
  • Say which component did what. Extraction by UFED, decoding by Physical Analyzer, review by Reader are three steps with three names and possibly three versions.
  • Distinguish the hardware kit from the software. UFED Touch is a device; UFED 4PC is software on a PC; Inseyets.UFED is the current software component.
  • Note any unlock or advanced access step under its own name and record the written authorisation that permitted it.
  • Keep the exported report format name correct. A UFDR file is a Reader report, not an extraction.

What an Examiner or Student Should Learn First

Our view as a vendor-neutral institute. The tool is the last thing to learn, not the first, because the tool will be renamed again.

  1. 01
    Where phone data lives

    SQLite databases, property lists, protobuf blobs, app sandboxes and keychain or keystore structures on iOS and Android. Every decoding tool is a parser for these. If you can read them by hand you can check the tool and explain it in court.

  2. 02
    What each extraction type reaches

    Logical, file system, full file system and physical acquisitions reach different data, with different completeness and different risks to the device. Learn the differences before learning which menu produces which.

  3. 03
    Lawful authority and documentation

    Written authorisation, consent where relevant, device isolation, photographs of the device state and a custody record. Advanced access to a locked device is a governed laboratory step under authorisation, never a shortcut.

  4. 04
    Validation of parsed results

    Pick several decoded artefacts in each case and confirm them against the raw database or file. Record what you checked. A parser that misses a table will miss it silently.

  5. 05
    Then the vendor workflow

    Extraction with UFED, decoding in Physical Analyzer, review and sharing through Reader, and the Inseyets workflow tools on top. Learn it on test devices you own, and read the release notes with each update because decoding changes between versions.

Keeping Up

Cellebrite publishes product update notes on its website for each release, and those notes rather than press coverage are the place to confirm what a given version does. Treat marketing language about capabilities as claims to be tested on your own devices, and keep your course notes written in terms of artefacts and acquisition types so that a renamed product does not make them obsolete. DFRTI's mobile forensics courses are taught that way and are not vendor training; the links below are to Cellebrite's own pages so that readers can check the current position for themselves.

This is an industry update written by the DFRTI editorial team from the sources below. It is not a vendor announcement and DFRTI has not independently tested any product named in it unless the text says so.

  • Cellebrite
  • Inseyets
  • UFED
  • Physical Analyzer
  • mobile forensics
  • product transition

Learn this properly

Go deeper with DFRTI

Free pages explain the ground. Structured courses, lab work and a mentor take you from knowing about it to doing it on a case.