ByteCase by Forensics ByteDownload Hub

ByteCase Roadmap

Where ByteCase is today, and where it could go next.

See what is available in the ByteCase Hub Local pilot, what we are improving next, and the longer-term direction for the modular suite and agency workflows.

Last reviewed October 20, 2026.

Hub Local

From pilot use to broader workflows.

ByteCase starts with the examiner's daily work: documenting evidence, making decisions, and moving a case forward. Shared deployment and supervisor visibility are longer-term directions built on those workflows.

Available now

Hub Local pilot

Hub 0.29 is a licensed Windows pilot for one examiner working with local cases. The current release is available for hands-on use and feedback.

  • Search and open local cases, review the active-case workspace, recognized records, activity, and workflow status.
  • Work with Intake, Evidence, Acquire, Verify, Objectives, Artifacts, Findings, and Workflow.
  • Review existing saved cases and export supported documents before activation; a signed offline license enables new work.
  • Use the current backup and recovery tools for local records. External evidence files still need separate handling.
Next focus

Make the pilot easier to trust and move

These are the near-term improvements guiding pilot work. Their order can change as examiners use the product.

  • Qualify Windows releases and check that an existing valid license continues to work after an update, without a new request for each version.
  • Make the case flow more guided: reuse saved department and examiner details in Intake, improve item-level evidence decisions and acquisition records, and save work in progress.
  • Give examiners a clearer move-to-new-computer path: verified backup, external-file inventory, restore preview, and activation on the destination computer.
  • Refine workflow exceptions, record handoffs, and the feedback loop from real pilot use.
In design

Connect review to the final record

These capabilities follow the pilot foundations and will be exposed only after their data and review behavior are ready.

  • Bring back Notes as a source-linked, resumable artifact review workspace with clear provenance.
  • Build Hub Report from saved examiner-authored records with review and preview before export.
  • Develop focused Timeline, Exhibit, and Closeout tools around linked case records and examiner decisions.
Longer term

Agency workflows and multiuser direction

These are product directions under exploration, not announced deployments or release commitments.

  • Explore an agency-local officer Intake form on the customer's network. Submissions would enter a pending queue; an examiner would accept, return, or reject each submission before it becomes a Hub case record.
  • Explore a separate agency-hosted, multiuser Hub with shared case records, assignments, and role-based access. An on-premises PostgreSQL server or an agency-controlled government cloud environment are possible deployment paths, subject to security and operational review.
  • Develop a supervisor dashboard as shared examiner workflows mature, so oversight is grounded in the case status, handoffs, and review records created by the people doing the work.

Explore the current Hub pilot →

Across the suite

Each tool has its own development stage.

These stages describe the individual ByteCase tools. A tool's stage does not mean every planned Hub integration is available.

Pilot Release

Signed Windows downloads available for examiner feedback, with release-specific scope and limitations.

Active Development

Implementation is underway around an established and documented product direction.

Product Design

The product direction is accepted, but workflows, interfaces, and capabilities may still change.

Development rules

Five questions before a feature belongs in ByteCase.

  1. Does it solve a demonstrated workflow problem?
  2. Will the generated record remain understandable and portable?
  3. Can the tool remain useful without unnecessary platform dependence?
  4. Have privacy, security, dependencies, and licenses been reviewed?
  5. Can the capability be described honestly at its current stage?

Suggest a priority

Examiner feedback can change the order.

Missing workflows, repetitive documentation, difficult handoffs, validation concerns, testing scenarios, and useful integration points all help refine the roadmap.

Share feedback Explore the suite →