Limited UndergroundOpen project workshop

About Limited Underground

One workshop. Separate projects.

Limited Underground is the parent workshop for practical software, vehicle tools, field hardware, and resilient communication systems. Each project keeps its own purpose, technology, evidence, and limits.
Why the workshop exists

Build the useful part first.

Limited Underground is a shared home for the work—not a claim that every project is a radio, an off-grid system, or the same kind of product.

The common standard is practical scope, local control where it matters, visible evidence, and no invented certainty.

Project family

The public names and their roles.

Public display names stay separate from engineering repositories, package identifiers, and stable technical routes.

Offline group communication and awareness

Limited Underground Trail

ESP32-S3 firmware, LoRa-class radio planning, BLE GATT, Kotlin Android, and a Windows loader inspection shell.

Open project
Linux server and dedicated LoRa network gateway

Limited Underground Trail Server

Debian 13.6.0, a dedicated USB-connected Trail LoRa device, ASP.NET Core, PostgreSQL/PostGIS, Caddy, MapLibre, and PMTiles.

Open project
Supplemental vehicle data display

Limited Underground Display

C++17 telemetry components, CAN and J1939 parsing, normalized signals, display-neutral view models, alarms, and recovery contracts.

Open project
Local-first vehicle analysis software

Husky Performance

by Limited Underground

Windows desktop software with local analysis, import, reporting, and packaged operator workflows.

Open project
Practical modular business operations

Small Business Suite

by Limited Underground

Windows business software with local persistence, modular workflows, validation, reporting, and multilingual UI.

Open project
Ideas held until their boundaries are credible

Future Projects

No stack is selected until a project has a bounded purpose and evidence plan.

Open project
Working principles

One standard across different kinds of work.

01

Start with a bounded purpose

A project should solve a specific problem before it grows into a product family.

02

Keep the base useful

Optional services, phones, repeaters, and vehicle links should extend a system rather than disguise a missing foundation.

03

Publish the boundary

Build-tested, hardware-tested, field-validated, and production-ready are different claims.

04

Design for change

Boards, displays, transports, and hosting can change without forcing unrelated projects into one identity.

Identity boundary

Shared ownership without blurred products.

Limited Underground Display is the display-project name and public repository; stable OG engineering identifiers remain where compatibility requires them. Husky Performance and Small Business Suite keep separate “by Limited Underground” attribution. Limited Underground Trail App is the Android client developed with Trail and does not yet have a separate public repository.

Working identity pending attorney clearance. Stable routes and technical identifiers remain separate so future naming decisions do not break software or evidence.

Public discussion

Follow the work where the evidence lives.

Project questions and reproducible technical feedback currently belong in the relevant public repository. Private prototype records remain in the authenticated Owner Lab.

Explore GitHub