Open source
Built in public.
Licensed to fork.
Tools I actually use — architecture analysis, nesting, async workers, and a local-first household stack — published as MIT repos, npm, and PyPI. No telemetry, no waitlist.
Issues and PRs welcome. Most of this started as solving my own problems and stayed public.
$ pip install vaultkeep
$ npm install @sssoman/ember
✓ MIT · local-first · no cloud required
github.com/sarweshsoman · pypi.org/project/vaultkeep
npmjs.com/package/@sssoman/ember
Published packages
Hearth ecosystem
Four pieces that stay loosely coupled: schema, documents, scheduling, and the Frappe app. Each repo is usable on its own.
Public repositories
ArchSentinelRust
Local-only architecture analysis — cycles, god files, dead code, no telemetry.
Async Task EnginePython
FastAPI + Redis job workers with retries, delayed jobs, and Docker Compose.
AnvilTypeScript
Desktop visual API builder that scans Django projects and merges DRF code.
PynestPython
SVG nesting for laser, plasma, and CNC — pack parts onto sheets with rotations.
HearthFrappe
Household policies, assets, and loans with family circles and reminders.
WarrenPython
Personal NSE paper-trading CLI. Research sandbox, not financial advice.
How I try to ship it
Local-first
Prefer code that runs on your machine. ArchSentinel never sends a repo anywhere. Vaultkeep does not talk to object storage.
MIT
Fork it, embed it, disagree with it. READMEs include install paths for both source and packages.
Frappe / ERPNext
Day job and side work in that ecosystem — Hearth is the public artifact; implementations stay with the clients they belong to.
Use it, break it, send a PR.
Start from a repo or a package. If something is wrong, open an issue — that is how most of these projects grew in the first place.