Nido

Nido is a self-hosted property-tracking workspace built as a modern monorepo. It combines a Go backend, a React frontend, and SQLite into a focused application for managing properties, custom fields, tags, engagement, and analytics.

Why I built it

The project explores how an operational workspace can stay useful without becoming noisy. The interface is authenticated and data-first, with the backend exposing structured APIs for a frontend that remains easy to navigate and extend.

Data safety

Nido treats operational data as something worth protecting. Its migration workflow supports pre-migration SQLite backups, controlled migration strategies, portable JSON exports, restore workflows, and migration status checks.

Architecture

The frontend communicates with the Go backend through typed service modules. SQLite remains the system of record, while the repository keeps the application, server, command-line helpers, documentation, and configuration organized in one workspace.