Dhruv Seth — PortfolioSheet 01/01—X 0000 · Y 00000Rev b4dbfbaScale 1:1
dhruvseth.in
  • Home
  • Projects
dhruvseth.in

© 2026 Dhruv Seth · India · Remote

HomeProjectsEmailLinkedIn ↗
Index/Projects/ForgeOps
Case study2026

ForgeOpsForgeOps

A local-first desktop workspace to design, scaffold and run your services.

Currently building
Role
Creator & Engineer
Status
In progress
Stack
React logoReactTypeScript logoTypeScriptElectron logoElectron
Links
Private
01 · Interface02 · Bridge03 · EngineCanvasInspectorLive logsTerminalPrivileged bridgeProcess supervisorGeneratorsWorkspace statePlugin host
Fig. 01 — System overviewSwipe to explore →
Summary

ForgeOps lets a developer sketch an application or service system on a visual canvas, generate real project folders from configurable templates, and run those projects — with live logs and a terminal — from the same interface. Everything runs on your machine, and every generated project is ordinary source code you own.

Measured
Runs on
Your machine
Generated code
100% yours
Cloud account needed
None
Contents
  1. 01The problem
  2. 02What it does
  3. 03Engineering highlights
  4. 04Principles
  5. 05Status

ForgeOps

ForgeOps is a local-first desktop workspace for building systems of services. You sketch the system on a visual canvas, turn each piece into a real, runnable project, and operate all of it — start, stop, logs, terminal — from one place. It's my biggest project, and it's under active development.

The problem

Every new service starts with the same ritual: scaffold a folder, wire up config, pick a port that isn't taken, write the scripts, then juggle a terminal tab per process to see what's running. Multiply that by a handful of services and the setup becomes the work. ForgeOps makes that repeatable, visual and fast — without hiding the code from you.

What it does

01
Design
Lay out services and their connections
02
Configure
Answer a short, validated form
03
Generate
A real project is written to disk
04
Run
Start, stop, build and test in one click
05
Observe
Live logs and a built-in terminal
Fig. — From sketch to running service
  • A visual canvas — drag services onto a graph, connect them, undo and redo, zoom across the whole system.
  • Real projects, not templates you're locked into — every generated project is ordinary source code you own, and it builds and runs without ForgeOps.
  • One place to operate everything — run, stop, build and test any service, watch its output live, and drop into a terminal already in the right folder.
  • Batteries for daily work — per-service task lists, Git tools, open-in-editor, and a bin to restore anything you deleted.

Engineering highlights

I'd show you more, but it's still being built — and the source code has asked for privacy until it's dressed for the occasion. 🙈

The headlines:

  • Real processes, real terminal — nothing simulated.
  • A strict privilege boundary between the interface and the system.
  • A self-healing workspace that recovers from crashes and drift.
  • Pluggable by design — new stacks and capabilities without touching the core.

Principles

  • Local-first. It runs on your machine, against your files. No account, no cloud workspace.
  • Your code stays yours. ForgeOps scaffolds and operates — it never becomes a dependency of what it generates.
  • Honest tooling. If something isn't supported yet, the UI says so instead of failing silently.

Status

In active development and used daily on my own projects. More generators and deeper workspace tooling are on the way.

Built with

  • Dhruv Seth
    Dhruv Seth
    Creator & Engineer
    LinkedIn ↗
Next sheet→
ProMetricXProMetricX

A gamified goal-tracking Discord bot for peer accountability.