Software copyright expert witnesses for infringement and substantial similarity. AFC analysis, code comparison, OSS review, expert reports, and testimony.
We help courts and counsel determine whether software has been copied, literally or non‑literally, and whether similarities reflect protectable expression or unprotectable ideas, processes, and APIs. Our engineers tie legal theories to code‑level facts, applying methods such as Abstraction-Filtration-Comparison (AFC) to separate creative expression from functionality.
Why Cyberonix for Copyright Disputes
- Software‑only focus. Mobile, Internet and web, cloud, databases, AI/ML, and software security, so we can explain how modern stacks are actually built.
- Source‑code grounded. We examine source code repositories (e.g., Git, Subversion, CVS), build artifacts, binaries/bytecode, logs, and version history to assess access, copying, and independent creation.
- Clear substantial‑similarity analysis. From literal copying (line/string/token/AST/CFG) to non‑literal SSO under AFC‑style reasoning, always mapped to alleged protectable elements.
- Protective order (PO) discipline. Secure, access‑controlled workflows for code and confidential materials.
- Courtroom‑ready experts. See our case history in our experts’ CVs.
What We Do
- Registration and deposit review (scope/coverage across versions)
- Substantial similarity (literal and non‑literal) with element‑by‑element charts
- AFC analysis (filtering ideas, efficiency‑driven choices, etc.)
- Reverse engineering and decompilation (where appropriate) to compare implementations
- Open‑source software(OSS) identification & license compliance analysis
- Independent creation evaluation (timelines, authorship, design decisions)
- Artifact forensics (commits, CI/CD, logs, emails, Confluence, Jira, Slack exports)
- Work product: technical memos, demonstratives, expert reports, deposition, trial testimony
Copyright Issues We Address in Software Matters
Literal Copying (Direct Code Copying)
We analyze alleged literal copying using code-grounded comparisons and element-by-element charts, pinpointing whether similarities reflect copying, common dependencies, shared templates, or routine engineering patterns.
Non‑Literal Copying and Structure, Sequence, and Organization (SSO)
Software disputes often turn on higher-level similarity (architecture, module boundaries, workflows, data models, and interfaces). We assess alleged SSO similarity through a technical lens consistent with AFC-style reasoning, separating functional constraints from expressive implementation choices.
Abstraction‑Filtration‑Comparison (AFC) Support
We help counsel and courts operationalize AFC by:
- Identifying the alleged protectable elements at the right level of abstraction
- Filtering out unprotectable material (ideas, processes, efficiency-driven choices, constraints, interoperability-driven design)
- Comparing the remaining expressive elements in a reproducible way
Access, Opportunity, and Independent Creation
We examine development artifacts and timelines to evaluate whether similarity is better explained by independent creation, legitimate reuse, parallel development, or third-party components.
Open‑Source Software (OSS) Provenance and License Compliance
Where OSS is implicated, we identify OSS components and evaluate license obligations and provenance issues that can materially affect claims and defenses.
Registration Scope and Version Coverage
We support review of registration materials and deposit copies to clarify scope across versions, releases, and timeframes, especially when products evolved materially over time.
Common Software Copyright Dispute Scenarios
- Competitors releasing similar apps or SaaS features where the dispute hinges on whether similarity is expressive vs. functional
- Contractor/vendor development relationships with later disputes over reuse of code, modules, or product components
- Employee departures followed by fast-follow products and allegations of copied implementation details
- Rewrites and “re-implementations” where the question is whether the new implementation is independently created or derived from earlier code
- Shared codebases, shared dependencies, or common frameworks that can create apparent similarity without copying
- OSS incorporation disputes (license obligations, attribution, distribution triggers, and provenance)
Evidence We Commonly Analyze
Depending on what is available in discovery and how the software is distributed, our analyses may involve:
- Source repositories and version history (commits, diffs, merges, tags/branches, authorship signals)
- Build systems and release artifacts (build configurations, dependency manifests, CI/CD logs, packaged binaries)
- Binaries/bytecode and reverse-engineering outputs (when appropriate and permitted)
- Architecture and design materials (specs, diagrams, ADRs, internal wikis, runbooks)
- Runtime behavior evidence (logs, telemetry, network traces, reproducible tests)
- Product documentation and public materials relevant to functionality and operation
- Development workflow artifacts (tickets, code review artifacts, test plans/results) relevant to timelines and independent creation
Methodology: Substantial Similarity and AFC‑Style Analyses
While every dispute is fact-specific, our work typically follows a disciplined, reproducible workflow:
- Define the comparison scope: Confirm versions, release dates, and the specific works to be compared (including what is alleged to be protectable).
- Collect and normalize technical artifacts: Establish a defensible record for the relevant code, binaries, and documentation, including version history where it is probative.
- Perform direct (literal) comparisons where relevant: Compare code at multiple technical levels (e.g., line/string/token/AST patterns) and identify whether overlaps are meaningful or explained by common components, templates, or dependencies.
- Analyze non‑literal similarity with appropriate abstraction: Evaluate higher-level similarity claims (SSO) by mapping architectural and design decisions to alleged protectable elements, while separating functional constraints from expressive choices.
- Apply filtration explicitly: Distinguish what is likely unprotectable (ideas/processes, constraints, interoperability-driven structures, efficiency-driven choices) from remaining expressive content.
- Present results in attorney- and court-ready form: Clear charts, exhibits, and narratives that connect technical facts to the questions at issue, designed to be explainable at deposition and trial.
When to Bring Us In
- Pre-suit and early case assessment (what is actually similar, and why)
- TRO / preliminary injunction posture where timelines and “likelihood of success” depend on clear technical comparisons
- After initial pleadings to refine a technically defensible theory of copying (literal and/or non‑literal)
- During fact discovery when repository history, access paths, and development artifacts matter
- Expert discovery: reports, rebuttal, deposition strategy, and demonstratives
- Pre-trial and trial: tutorials and testimony support
Engagement Process
- Scoping and conflict checking
- Signing engagement agreement
- Signing protective order (PO) and secure evidence intake
- Early case assessment (documents, software development artifacts, and code)
- Deep analysis (code repositories, code version comparisons)
- Reports, depositions, and trial testimony
- Post‑hearing/trial support
Frequently Asked Questions
What does a software copyright expert witness do?
A software copyright expert witness provides technical opinions on whether software was copied (literally or non‑literally) and whether similarities relate to protectable expression versus unprotectable functional material, grounded in code and software engineering evidence.
What is Abstraction‑Filtration‑Comparison (AFC)?
AFC is a structured way to analyze similarity in software by (1) abstracting software to appropriate levels, (2) filtering out unprotectable elements such as ideas/processes and constraint-driven structures, and (3) comparing the remaining expressive content in a disciplined way.
Can you analyze non‑literal copying and SSO?
Yes. Many software disputes involve alleged similarity in architecture, workflows, and data structures. We analyze these issues using an engineering lens aligned with AFC-style reasoning, and we present results with clear charts and explanations.
What if we only have binaries or limited access to source code?
Where appropriate, we can compare implementations using available artifacts (e.g., binaries/bytecode, documentation, runtime behavior) while clearly stating constraints and preserving reproducibility.
Do you handle open-source provenance and license issues?
Yes. When OSS is implicated, we can identify OSS components and evaluate technical facts relevant to provenance and compliance.
What do you need to get started?
Typically: the copyrighted works and versions at issue, the accused works and versions, key dates, and the best available access path to repositories/build artifacts/binaries and relevant documentation.
Do you provide testimony?
Yes. Our work commonly includes reports, deposition testimony, and trial support.
Selected Prior Engagements
HEALTHeSTATE LLC v. The United States, ASM Research
- Retaining party: The United States
- Venue: The United States Court of Federal Claims
- Case No.: 18-034
- Counsel: United States Department of Justice
- Nature of suit: Intellectual Property – Copyright
Miants, LLC, et al. v. Kevin Lasser, et al.
- Retaining party: Miants LLC.
- Venue: State of Michigan, Oakland County Circuit Court
- Case No.: 2013-133695-CK
- Counsel: Mantese, Honigman, Rossman & Williamson, P.C.
- Nature of suit: Intellectual Property – Copyright
Warner Records, Inc., et al. v. Altice USA, Inc., et al.
- Retaining Party: Warner Music Group, Sony Music and Entertainment, Sony Music Publishing
- Venue: Eastern District of Texas
- Case No.: 2:23-cv-576-JRG-RSP
- Counsel: Oppenheim & Zebrak, LLP
- Nature of suit: Intellectual Property – Copyright
BMG Rights Management (US), LLC, UMG Recordings, Inc, Capital Records, LLC, Concord Music Group, Inc., and Concord Bicycle Assets, LLC v. Altice USA, Inc, and CSC Holdings, LLC Retaining party: BMG Rights Management (US), LLC, et al.
- Venue: Eastern District of Texas, Marshall Division
- Case No.: 2:22-CV-471-JRG
- Counsel: Steptoe LLP
- Nature of suit: Intellectual Property – Copyright
Related Expertise
Software copyright disputes often overlap with:
- Source Code Review
- Internet and Web
- Mobile Software
- Cloud Computing
- Database and Storage
- Software Engineering
- Artificial Intelligence
See, also, Trade Secret, Patent, and Breach of Contract practice areas
We Are Cyberonix
At Cyberonix, our software expert witnesses offer academically grounded, industry-tested insights in complex software disputes. We support litigation involving patents, trade secrets, copyright, breach of contract, and class actions through source code analysis, technical reporting, and expert testimony.
