| Requirements and specification | The AI engineer turns your idea into requirements and a product specification, and checks the design against them. | Writes documents and code from your prompt.[7] |
| What it is | AI hardware engineer equipped with native design tools | General AI coding agent[1] |
| Where it runs | Runs inside your web browser. No software to install. Your projects stay in the cloud. | Your terminal, code editor, the Claude desktop app, Slack, or the web[1] |
| Who does the design work | The Flux agent. Your engineers review and edit. | Developers give the coding agent software tasks.[7] |
| Schematic and parts | Built in. Chooses from 734,000+ public parts. | Not built in. You connect outside tools and part data with scripts.[1] |
| Board layout and routing | Built in | Not built in. You connect an outside board tool with scripts.[1] |
| Placement and routing | The AI engineer places the parts and routes the board like an experienced designer. Your engineers review and edit. | No built-in PCB trace-routing tools.[7] |
| High-speed design | The AI engineer plans DDR topology and timing budgets, routes differential pairs and length-matched buses, tunes length and skew, fans out BGAs with blind, buried, and microvias, and sets trace impedance from your stackup. It checks the routed board with S-parameters, TDR, eye diagrams, crosstalk analysis, and a signal integrity, power integrity, and EMC review. Your engineers review and edit. | No built-in PCB signal-integrity analysis.[7] |
| Parts and sourcing | 734,000+ public parts, with live prices and stock from distributors | No built-in electronics parts library.[7] |
| Simulation and design rule checks | SPICE, power delivery network, full-wave electromagnetic simulation, and signal integrity simulation, plus thermal and mechanical simulation and design rule checks. | Not built in. You connect outside simulators with scripts.[1] |
| Firmware | Writes firmware for each board it designs | Writes code, including firmware[1] |
| Wiring harnesses | Built in. Flux designs the wiring harnesses between the boards: connectors, pinouts, and wires, in the same project. | No built-in wire-harness design tools.[7] |
| Manufacturing files | Flux prepares Gerber, ODB++, IPC-2581, bill of materials, pick-and-place, and more. Flux can check the files before you order by checking copper gaps, silkscreen, board outline, BOM, and pick-and-place files. | Not built in. Your scripts or outside tools write the files.[1] |
| Quotes and orders | Quotes and orders for boards, 3D printing, CNC machining, and wire harnesses, from the project. | No built-in hardware quoting or ordering workflow.[7] |
| Import from other tools | Imports complete projects from Altium, OrCAD and Allegro, KiCad, PADS and Xpedition, CADSTAR, Eagle, Fusion Electronics, EasyEDA, DipTrace, and SOLIDWORKS PCB. Flux imports Labcenter Proteus SDF netlists with Specctra board exports. IPC-2581 revision B and C files become board projects with reusable footprint parts. IDF 2.0 and 3.0 board files become board projects with the outline, cutouts, drilled and mounting holes, part placements, and 3D part heights. | No built-in EDA project importer.[7] |
| Versions, branches, and merges | Full change history. The AI engineer forks a design into a second version, keeps both, and merges the changes that you pick. | No native hardware design version history.[7] |
| Who reviews the work | The entire team in one live browser project: electrical, layout, mechanical, and firmware engineers. | Developers review the code changes[1] |
| Product images, videos, and documents | Product images, product videos, datasheets, and regulatory documents, made from the design in the project. | Writes product documentation and code from your prompt.[7] |
| Mechanical CAD | Built in, kernel agnostic. From a single enclosure to a full robotic arm. | Not built in. You connect an outside CAD kernel with scripts.[1] |
| Mechanical simulation | Finite-element stress, thermal, and airflow simulation | No mechanical simulation workspace.[7] |
| Mechanical manufacturing | STEP, STL, and 3MF files, plus quotes for 3D printing, CNC machining, sheet metal, and laser cutting | No CNC manufacturing workspace.[7] |
| CNC toolpaths and G-code | The AI engineer writes the toolpaths, the G-code, a toolpath preview, and a setup sheet for the parts that it designed. | No CNC toolpath or G-code workflow.[7] |
| AI models | Frontier models across multiple providers, including Claude and OpenAI models | Claude models[2] |
| Tool licenses | Your Flux plan includes the editor, mechanical CAD, parts data, simulation, and manufacturing files. No other purchases needed. | Each outside tool needs its own license or account, for example a Fusion 360 license[6] |
| Team knowledge and rules | Define rules once for your whole organization. Every AI engineer applies them across every project, and Flux verifies each design against your rules. | CLAUDE.md files in each code repository, shared through version control[3] |
| Parallel work | A lead AI engineer divides a product into workstreams across projects, runs them in parallel, and reports back. Major changes pause for your approval. | Subagents and agent teams for code tasks[4] |