Every engineering discipline. One project tree.
IndiSpec is an all-in-one engineering design and delivery toolkit. Electrical schematics, PCBs, CAD parts and assemblies, CFD reviews, calculation sheets, parts data and issued packages live together — on one version history, one collaboration surface, and one approval model for people and agents.
From the single-line diagram to the issued package
Each discipline is a page kind on the same project tree — not a separate product with its own login, file format and version history.
Electrical
Schematics and panel layouts, with the netlist behind them
Draw the electrical design on A3 sheets and lay the same parts out in the cabinet. The netlist, wire numbers and cross-references are derived from the drawing, so tracing a circuit and colouring a net never means maintaining a second copy by hand.
See capabilities →PCB
Code-first boards where the source is the document
A PCB is a tscircuit TSX program compiled in the browser to circuit JSON, then rendered as a board, a schematic and a 3D assembly. Every board or schematic gesture compiles back into the source, so the code, the drawing and an agent edit always describe one program.
See capabilities →CAD & CFD
Parametric parts, assemblies and analysis on the same project tree
A part is a FeatureScript-compatible source document evaluated by an OCCT-in-WASM kernel. Features, gizmos and parameters all compile to source; assemblies compose parts and imported STEP; the CFD study maps that geometry to a solver package and reviews the solved result in the app.
See capabilities →Calculations & documents
Sizing work, reference documents and the numbers that bind them
Engineering calculations belong next to the design they size, not in a spreadsheet that drifts. Calculation sheets recalculate live, documents can reference each other by value, and PDFs from suppliers are readable as project documents.
See capabilities →Engineering data
One part master feeding every drawing and BOM
Projects share one materials register: catalog parts, organisation libraries, project usage, panel BOMs and a generated rollup with documentation coverage. Vendor and EPLAN inventories are harvested into the same model instead of being retyped per project.
See capabilities →Delivery
Issue the package, not a folder of loose PDFs
Export is a designed artifact. Build a package with its contents page, manifest, scope and print options inside the project, version it with the design, and render it through the same pipeline every time.
See capabilities →Collaboration & agents
One project, many hands — people and agents on the same rules
Documents are collaborative in real time, projects are versioned like code, and work is tracked on a task board. The in-app assistant and isolated agent runs act through the same project and approval rules as a person, on their own branches.
See capabilities →A new discipline is a page kind, not a new product
Every document — a drawing sheet, a PCB, a 3D model, a report, a deliverable, a PDF, a task board — is a typed page on one of a small set of surfaces. They share the project filesystem, version control, collaboration and export machinery.
- One project filesystem with folders, drag/drop and a dependency graph
- One content-addressed version history for every document type
- One collaboration and approval model for people and agents
- One export pipeline that issues PDF/ZIP packages
Design, verify, deliver — and keep the record
The paperwork is not a separate afterthought. It is produced by the same project that holds the design.
Design
Sheets, boards, parts, assemblies and calculation sheets live in one project tree, in the discipline each needs.
Verify
Trace nets, colour potentials, check BOM documentation coverage and validate CFD geometry before it reaches a solver.
Deliver
Issue a versioned package with a contents page, manifest and print options — not a hand-assembled folder.
Collaborate & automate
Work together in real time, review on branches, track tasks, and hand routine work to an approved agent run.
The deliverable is part of the project
A package is designed, not assembled by hand the night before issue. Choose its pages, order, print options and scope; keep the contents page and manifest with it; re-run it whenever the design moves.
- Scope by project, zone or an authored page order
- Contents page and manifest travel with the package
- Per-package print options, including sheets coloured by net potential
- Re-run the same package when the design moves
A team of people and agents, with one audit trail
Two engineers can edit the same project in real time, review each other on branches, and hand a well-scoped task to an agent run that works in isolation and comes back as a reviewable commit. The assistant proposes; your approval policy decides.
- Realtime editing with presence and cursors
- Branches, restore and manual merge for whole projects
- Task board, comments and a cross-project work inbox
- Agent runs on isolated branches with an approval step
Shipped, in progress, and honestly planned
IndiSpec is built in the open against its own specification. Here is where the sharp edges still are.
Shipped, including EPLAN macro import.
Shipped slices with the code-first / source-is-the-model authoring.
Shipped on a single-working-tree model.
Two people cannot yet edit different branches at once; the merge target is the checked-out branch.
A Tauri shell over the same editors; offline parity is in progress.
Not decoded yet; embedded U3D models are.
Specified (power-budget diagnostics, plugin host) but not shipped.
Per engineer, all disciplines included
No module licences. Every paid plan includes every editor and the delivery pipeline; the difference is collaboration, control and support.
Bring the whole design into one place
Start on the free plan with a real project, or look through the toolkit discipline by discipline first.