BURNIN is a local-first reliability and endurance-test planning, execution, inspection, analysis, and evidence instrument for makers, engineers, repair technicians, and small manufacturers.
Open index.html in a modern desktop browser. No account, server, installation, or internet connection is required after the file is available locally.
Failure Concerns → Stressors → Test Cycle → Instrument → Run → Inspect
BURNIN keeps one cycle, one run, one specimen, one condition, and the complete campaign distinct. It also separates observations, inferences, unsupported claims, limitations, and remaining questions.
A four-step setup asks for:
- The artifact, normal function, frequency, and test purpose
- Failure concerns, normal environment, and hazards
- Available measurements, test duration, and optional local photos or diagrams
- The stop boundary, explicit assumptions, and recommendation rationale
The generated campaign is always labeled Draft — Review Required. Guided Mode favors representative use, repetition, recovery, interval inspection, and modest acceleration rather than extreme stress.
Advanced Mode retains the complete campaign system:
- Multiple conditions, runs, specimens, and controls
- Failure concern and stressor workspaces
- Damage vs. Acceleration Check
- Visual cycle builder
- Instrumentation planning and sensor mapping
- Manual run console and optional connected-data preview
- Inspection, photo comparison, teardown, and evidence inventory
- CSV analysis and compound failure criteria
- Deviation and validity review
- Claim-to-evidence traceability
- User-selected acceleration models
- Report builder, portable bundles, manifests, and recovery snapshots
- Four-step guided campaign setup
- Local photo and diagram attachments during setup
- Explicit assumption and recommendation-rationale register
- Advanced Command Center with plan-readiness checks
- Clear Guided and Advanced navigation separation
- Command palette with
Ctrl/Command + K - Contextual help with engineering boundaries
- Active-project deletion with name confirmation
- Guided setup and readiness sections in the evidence package
- Final responsive, contrast, focus, reduced-motion, empty-state, and navigation cleanup
- Schema 20 migration from all prior BURNIN releases
BURNIN is a planning and evidence tool, not a safety controller.
- The browser must not be used as a safety interlock.
- Emergency stops and protective systems must exist independently.
- Manufacturer limits and applicable standards take precedence.
- Accelerated testing can create hazardous and misleading conditions.
- Sample size and test duration affect the strength of conclusions.
- Passing a burn-in test does not prove universal reliability or regulatory compliance.
Projects, templates, setup images, imported run data, and recovery snapshots are stored in browser storage. Use Export Portable Bundle before clearing browser data or moving the project to another device.
Ctrl/Command + K— command palette?— contextual helpAlt + 1–9— primary workspacesAlt + A— AnalysisAlt + V— Review & ExchangeAlt + 0— ReportsCtrl/Command + Shift + R— create/open a runCtrl/Command + Enter— record a run-console event
index.html— complete standalone applicationREADME.md— this guideCHANGELOG.md— release history
BURNIN sends no project, test, measurement, image, or evidence data to external services. Optional browser connection previews only operate when the user explicitly initiates them.