Digital forensics software, online-safety education, technical knowledge systems, infrastructure builds, field notes, and purpose-built web projects.
The areas I am actively building, studying, documenting, or turning into practical resources.
ByteCase and future tools focused on documentation, verification, organization, and repeatable technical work.
Safe Screens Weekly and practical guidance for families, schools, and community partners navigating online risks.
Hashimoire, field notes, playbooks, templates, artifact references, infrastructure, and defensive-security research.
Ownership-first static websites, useful service content, quote workflows, and low-maintenance deployments.
Featured projects
The two projects that best represent the technical and public-safety directions behind ForensicsByte.
A modular digital forensics workflow suite for organizing case documentation, preserving verification records, and building repeatable examiner workflows.
A parent-focused digital safety project helping families understand online risks before they become crises.
Growing systems
Project hubs that grow through planning, implementation, experimentation, and lessons learned.
A living DFIR and defensive security field reference for tool notes, playbooks, artifact paths, snippets, detections, templates, and repeatable workflows.
A long-form homelab and infrastructure build focused on Proxmox, TrueNAS, segmented networking, VPN access, private DNS, backups, monitoring, and practical self-hosting.
A practical web-build project focused on fast, low-bloat websites for service businesses using static-site workflows, clear structure, quote forms, and local trust signals.
ForensicsByte is not only a finished-project shelf. It is also a record of progression: the tools, ideas, workflows, and technical judgment I am sharpening over time.
Acquisition concepts, report structure, evidence handling, mobile device workflows, computer collection, and the practical limits of tools.
Controls, policy, risk, logging, endpoint management, incident readiness, and the operational side of making technology defensible.
Python tools, Proxmox and NAS planning, static sites, documentation systems, low-bloat web builds, and workflows that make technical work easier to repeat.
Practical writing on digital forensics, cybersecurity, evidence workflows, tools, builds, and lessons learned.
Accountability and empathy are not opposites. A look at occupational trauma in law enforcement, the hidden burden carried by ICAC investigators and forensic personnel, and why meaningful mental healthcare should be treated as part of professional readiness.
A forensic acquisition needs more than a tool report. An acquisition packet documents the evidence item, tool and version, method, hashes, outputs, limitations, storage location, and handoff notes so the work can be understood later.
The original evidence item, forensic image, logical extraction, export, generated report, and working copy are all connected, but they are not interchangeable. A defensible workflow names, stores, hashes, and documents each layer clearly.
This site is built as a living resume, portfolio, and field-notes archive. If your project fits the lanes shown here, I am open to aligned consulting around cyber, forensics, investigative technology, documentation, workflow improvement, and practical web builds for service-based businesses.
Intake design, acquisition documentation, verification records, evidence-process structure, and practical support for digital forensic workflows.
Security process improvement, policy support, risk-minded documentation, incident readiness, and plain-English technical writing.
Clear, low-bloat websites for service providers that need credibility, clean structure, useful content, and simple ways for customers to make contact.
Explore the projects, read the field notes, or reach out when something here aligns with a problem you are solving.