Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

BoardRipper

Web-based PCB boardview viewer for board-level repair. Supports fourteen formats including BVR1/3, BRD, BDV, FZ, GenCAD, Mentor Neutral, XZZ, TVW, Allegro, Altium, KiCad and EAGLE. GPU-accelerated rendering with dockable panels.

Ficha actualizada 22 sept 2026, 19:25 · upstream 22 sept 2026, 19:17 · release v0.43.0

Ver códigoProblemas y ayudaRepositorio ↗Sitio oficial
00

Qué es BoardRipper

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

BoardRipper is a web-based PCB boardview viewer designed for board-level repair work. It supports fourteen different board formats including BVR1/3, BRD (Apple/Mac), BDV (Honhan/Tebo-ICT), FZ (ASUS encrypted), GenCAD, Mentor Neutral, XZZ (DES encrypted), TVW (Teboview), Allegro v15–v18, Altium PCB, KiCad and EAGLE. The application features GPU-accelerated rendering powered by PixiJS and WebGL, enabling smooth 60 fps performance even on integrated graphics cards down to Intel HD 4000-era hardware.

The interface includes dockable panels for component information, net lists, search results, PDF viewers, settings, debug logs, and a library panel. Users can open multiple boards simultaneously in tabs, toggle between top/bottom layers independently, perform multi-line searches across components with voltage and value annotations, and drag-and-drop board files or folders directly into the application.

A reference database maps board numbers to manufacturers, ODMs, and device models, while PDF schematics are automatically linked when both a board file and its corresponding schematic exist in the library. The app supports offline operation via a single-file build that runs entirely client-side without any server or shared data storage.

CASOS DE USO
  • Board-level repair of printed circuit boards using multiple formats simultaneously
  • Cross-referencing component pinouts between different board views and schematics
  • Offline inspection of PCBs stored on USB drives without internet access
  • Multi-layer board analysis with independent layer visibility
  • Batch processing of multiple boards from a library or folder
PUNTOS DESTACADOS
  • GPU-accelerated rendering at 60 fps using PixiJS and WebGL, supporting up to 10,000+ components
  • Support for fourteen board formats including BVR1/3, BRD, BDV, FZ, GenCAD, Mentor Neutral, XZZ, TVW, Allegro v15–v18, Altium PCB, KiCad and EAGLE
  • Dockable panel system with component info, net lists, search results, PDF viewers, settings, debug logs, and library panels
  • Self-update capability via signed Ed25519-signed updates without requiring a GitHub token or server-side verification
PRECAUCIONES
  • No board files are included in the distribution; users must provide their own boardview files and PDF schematics
  • The bundled reference database contains only metadata (board numbers, manufacturers) with no copyrighted content
  • Self-update functionality requires Docker and a host machine's Docker socket to function
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU4 vCPUrecomendación inicial
MEMORIA8 GBRAM estimada
DISCO10 GBalmacenamiento base
COMPLEJIDADmediumnivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Listo para automatizar

BoardRipper is primarily deployed as a server application accessible via web browser over the network. The recommended setup uses Docker Compose: run `docker compose up -d` to build and start the container, which mounts the `/library` directory for board file storage. Alternatively, pull the image directly with `docker pull ghcr.io/alexeyinwerp/boardripper:latest`. For a portable standalone solution, build the Go server with `CGO_ENABLED=0 go build -o boardripper .`, place it alongside the `dist/` folder and set an environment variable `STATIC_DIR=/path/to/static`. The Docker image is approximately 25 MB uncompressed (~13 MB compressed). Development uses Vite for hot-reloading the frontend at port 5173 while the Go server runs on port 1336.

✓Dockerfile
✓Compose
✓One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
Next.jsReactNode.jsGo
SERVICIOS
No detectados
BASES DE DATOS
No detectadas
PUERTOS
8081808051731336
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.