Engineering mission control

Keep code, boards, and CAD working as one system.

Inventivus connects the coding, ECAD, and mechanical CAD tools your team already uses, then shows when a change in one leaves the others behind.

rover-2 / drivetrain

Drivetrain thread

Maya, Leo and Sam are talking it through

3 working
M

Maya now

Heads up — I moved current sense off PA3 in the schematic. It's on PA5 now.

typing
Message the drivetrain team

Built for robotics, drone, and aerospace teams of 3–30 engineers

The problem

Nothing is wrong in any single tool. The mismatch lives between them.

Every domain is internally consistent. Git is clean, the schematic is clean, the CAD is clean. The failure is that no one of them can see the other two.

  1. Mon 14:0201

    The schematic changes

    An engineer moves the current-sense line from PA3 to PA5 in EasyEDA and pushes rev 7. Perfectly ordinary change.

  2. Mon 14:0302

    Firmware doesn't know

    motor_ctrl.c still reads PA3. The task that closed against rev 6 is still sitting in the Done column, still looking correct.

  3. Tue 09:4003

    Mechanical doesn't know

    The board mount in Fusion 360 was modeled against the old connector position. Nobody re-checks it, because nobody was told to.

  4. Fri 16:2004

    The bench finds out

    Board goes in, standoff fouls the connector, firmware reads a floating pin. Two days of debugging for a change that was made on Monday.

A workspace tool can hold a link to the schematic. It cannot tell you the schematic moved after the task was closed.

How it works

The Machines view maps your project as a system, not a list.

Machines · Rover-2 drivetrain2 out of sync
motor_ctrl.cgit · a91f2eTask #218done · 4d agoPowerStage.schEasyEDA · rev 7MainBoard.pcbEasyEDA · rev 7Enclosure.f3dFusion 360 · v12BoardMount.f3dFusion 360 · v9
Software / gitElectronics / EasyEDAMechanical / Fusion 360Drifted from a linked revision

One graph, three domains

Tasks, commits, schematics, boards, and CAD bodies are nodes. Dependencies between them are edges you declare once.

Staleness detection

Inventivus tracks revision state in each connected tool. When a linked file moves past the revision a task was closed against, the node is flagged — automatically.

Semantic cross-referencing

It compares structure across domains: a firmware pin reference with no matching net in the schematic gets surfaced before the board is on the bench.

Familiar, and not

Your team already knows how to use this. It just understands things Notion never will.

There is no onboarding program and no data model to design. Day one looks like the workspace tool you'd otherwise default to. Day two is when the difference shows up.

Same as what you use now

Notion, ClickUp, Linear, Airtable — the parts that work, unchanged.

  • Task boards

    Columns, assignees, priorities. Same mental model as Linear or Trello.

  • Comments and threads

    Discussion attached to the work, not scattered across chat.

  • File sharing

    Drop files where the work is. No import ceremony, no schema setup.

What they can't do

Cross-domain revision awareness, not just links between documents.

  • Knows your git history

    Commits and branches are first-class nodes, not pasted URLs.

  • Reads schematic revision state

    EasyEDA revisions are tracked, so a rev bump is an event — not a stale link.

  • Watches CAD versions

    Fusion 360 versions tie back to the tasks and boards that depend on them.

Use your existing tools

EasyEDA and Fusion 360 are examples, not limits.

Connect your team's preferred coding, CAD, and ECAD software with one click. Inventivus brings its revision history into the same project graph.

Coding tools

Repositories, commits, branches, and files

GitHub, GitLab, Bitbucket, and more

ECAD tools

Schematics, nets, boards, and revisions

EasyEDA and other ECAD software

CAD tools

Models, assemblies, components, and versions

Fusion 360 and other CAD software

One-click setup. No migration or custom schema required.

Not another AI copilot

It reports the state of your system. The engineering call is still yours.

Inventivus does not generate designs, write firmware, or suggest what you should build. A model runs in the backend to help with detection work — matching pin references to nets, spotting structural mismatches — but it never speaks to you and never acts on your behalf. What you get is a fact: this changed, these things depend on it, they haven't caught up. Deciding what that means for the project is the part you're good at, and we're not interested in taking it from you.

Stop finding out on the bench.

Inventivus v1.0.0 is available as a desktop app for small hardware and software teams.