The official line is blunt: design PCBs with AI, in the browser, free to start. I wanted the part after the slogan — which Copilot model to pick, what it is allowed to change, and where I still have to be the lead.
This is my walkthrough after the flux.ai redirect landed me on the product homepage and I kept going into Copilot docs. It is not a substitute for sitting in the editor.
Why it stuck
The homepage promise I care about is live component data: inventory, pricing, alternates. When I asked Copilot for a PD controller, I wanted a part I could buy this week. That is a different product from a chat window that hallucinates a resistor value and shrugs.
Plan, schematic, layout, manufacture — each stage is written as a check-in. Docs are explicit: Copilot modifies the schematic with your approval. I did not see a “ship to fab while you sleep” toggle.
No local install is the collaboration pitch: versioning, permissions, a link instead of a zip. I reviewed a project on a laptop that has never seen an ODB++ plugin.
What Copilot sounds like
These are editorial cards in Copilot’s own domains: plans, datasheets, reviews, architecture, netlists, Python from the Code Tool, and a SPICE-shaped check. They are not screenshots of a picture model. Flux does not sell image or video generation on the pages I opened.
Plan check-in for a USB-C PD sink before copper moves
Datasheet parse on an STM32G0 — map, not a substitute PDF
Review flags on a 4-layer IoT node I still had to own
Architecture blocks for a coin-cell BLE node
(export (version D)
(design (source usb_c_pd_sink) (tool "Flux Editor"))
(components
(comp (ref J1) (value USB4125-GF-A) (footprint USB_C_Receptacle))
(comp (ref U1) (value STUSB4500) (footprint QFN-24))
(comp (ref U2) (value TPS62130) (footprint QFN-16))
(comp (ref U3) (value ESP32-S3-WROOM-1))
)
(nets
(net (code 1) (name VBUS) (node (ref J1) (pin A4)) (node (ref U1) (pin 5)))
(net (code 2) (name +5V) (node (ref U2) (pin VOUT)) (node (ref U3) (pin 2)))
(net (code 3) (name GND) (node (ref J1) (pin A1)) (node (ref U2) (pin GND)))
)
)Netlist-shaped connectivity after a Copilot wiring pass
# @code: LDO dissipation vs dropout, 5V in → 3V3 @ 250mA
# Editorial example of the Python Copilot's Code Tool can emit.
vin, vout, iout = 5.0, 3.3, 0.25
pd = (vin - vout) * iout # 0.425 W
theta_ja = 160 # °C/W, SOT-23-5 typical from the datasheet I attached
tj = 25 + pd * theta_ja
print(f"Pd={pd:.3f} W Tj≈{tj:.0f} °C at 25°C ambient")
if tj > 125:
print("Move to a DFN or add copper under the tab.")Code Tool Python: LDO dissipation versus package
* @simulator: 5V buck, 3A step — check inductor current before layout
.param vin=5 vout=3.3 fsw=500e3
V1 vin 0 {vin}
* simplified: current-mode buck behavioral source
Rload vout 0 1.1
L1 sw vout 2.2u
Cout vout 0 44u
.tran 0.2m
.probe I(L1) V(vout)
.endSimulator-style buck check before layout freeze
What it is
I typed flux.ai and landed on the official Flux website at www.flux.ai/p. The H1 there is “Design PCBs with AI.” Under it, Flux calls itself the world’s first AI hardware engineer: you give it a job, it plans, explains, and executes inside a full browser eCAD you can edit any time.
That split matters. Copilot is not a separate chatbot you paste netlists into. It lives in the Chat tab, or from a right-click on the canvas. It can see project metadata, components, nets, datasheets, layout silk and traces, even comment locations. Docs are honest about a limit I needed: Flux primarily works with schematics and currently has limited understanding of PCB layout and trace positioning. I will not pretend it is a drop-in replacement for a senior layout contractor on an eight-layer HDI run.
The job list on the homepage matches the docs: research and planning, part search, datasheet parse, generated netlists, design reviews, firmware help, testing and debugging, auto-layout. Specialized mentions include @file, @library, @calculator, @code, @help, and @simulator. Code here means Python for analysis and charts, plus firmware assistance — not a secret image studio.
I also noted the human remainder: real-time collaboration, SSO and project permissions, SOC-2–aligned language on the FAQ, and a support path at help@flux.ai. None of that makes this notes page official. It makes the product a serious editor with an assistant, which is rarer than another landing page that says “AI” six times.
Hardware they show
Under “Ship real hardware,” the official site lists eight directions, from meshed IoT to hardware accelerators. I did not invent extra verticals. If your board is a toaster timer, you can still start — the list is a catalog of examples, not a bouncer.
Connected sensors, edge nodes, and smart infrastructure boards.
On-device intelligence for real-time decision-making hardware.
Sensor-driven robotic controllers you can fork and edit.
Audio, vibration, and signal-processing modules.
Flight controllers, telemetry, and navigation-class boards.
Energy routing, conversion, and regulation hardware.
Precision control, monitoring, and process hardware.
Specialized compute engines for AI and signal workloads.
Chat models
Docs put a picker at the bottom of chat. I am not translating the names. Next Gen (Beta) is the newest, with vision and the highest reasoning. Advanced Reasoning is the slow thorough one. General is the default. Speedy is the short-question model. They all spend ACUs. I start on General unless the question is obviously a lookup or obviously a fight.
Newest Copilot model: streaming, vision on schematics, highest reasoning for novel board problems.
Slower, thorough Copilot: signal integrity, power distribution, multi-layer calls that need a long think.
Default Copilot: fast everyday schematic work, part picks, and balanced ACU cost.
Fastest Copilot: short lookups, yes/no checks, and brainstorming when latency matters more than depth.
Flux publishes those four in its model-selection reference. I did not add a fifth “image model.” Vision on those models is for reading schematics you attach, not for inventing product shots.
Jobs in the product
I grouped the homepage’s AI menu into pages I can keep honest: AI Auto-Layout, architecture, part research, netlists, design reviews, and code / firmware. If Flux did not put the phrase on the site, I did not make a category for it.
Placement and routing inside the browser editor, with your keep-outs still in charge.
Block diagrams and plans you approve before Copilot spends copper.
Library search plus datasheet parsing against live inventory.
Connectivity dumps you can read, export, and take to fab tools.
Context-aware review that is more than a binary DRC pass/fail.
Python from the Code Tool, plus firmware help beside the schematic.
Who this is for
If your schematic review already happens on a link, Copilot is an extra reader in the same tab. I would not migrate a ten-year Altium vault overnight. I would start a new IoT node here and keep the legacy board where it is.
The homepage talks about forking featured projects and templates. That is the on-ramp I would use before I trusted auto-layout on a board I must fab twice.
Transparent AI is an official talking point: reviewable, reversible, with you in control. If your process cannot accept a silent net rename, you are in the right product category — and you should still read the diff.
If your only asset is a finished KiCad PCB file, the FAQ I read says layout import is not supported yet. Bring symbols, or start the board in Flux. I would not sell you a miracle converter.
How I would start
The homepage’s Plan stage is “tell it what you want to build.” I would write constraints: layer count, USB-C or not, antenna keep-out, fab house. Then I would make it show the plan before it drops symbols.
Unless the first question is “what is pin 12,” I would not jump to Next Gen (Beta) for a hello-world LED. I would switch up only when the answer feels thin or the board gets mean.
Gerbers, drill, BoM, pick-and-place, netlist — that is the official export list. I would open the Gerbers in a viewer I already trust before I sent money to a fab.
| If the job is | I open |
|---|---|
| Everyday schematic and part picks | General |
| Pin lookups and fast yes/no | Speedy |
| PDN, SI, nasty debug | Advanced Reasoning |
| Novel architecture, extra vision pass | Next Gen (Beta) |
| Placement and routing in the editor | AI Auto-Layout |
Questions
Flux is a browser-based electronics CAD with Copilot sitting in the project. The homepage I landed on after flux.ai redirected to the official Flux website sells an AI hardware engineer: you describe a job, it plans, then it can research parts, draw schematic, place, route, and emit fab files. I treat that as a partner in the editor, not a black box that ships a board while I sleep. This page is my independent notes. It is not Flux’s own site.
The homepage that resolved for me is the official Flux website at www.flux.ai/p. Docs live at docs.flux.ai. Help is listed as help@flux.ai on the same homepage. I do not treat social posts as product truth. Primary buttons on this overview open a local next-step dialog; they do not log you into Flux.
The model picker in the Chat tab lists four: Next Gen (Beta), Advanced Reasoning, General, and Speedy. Official docs call General the default for everyday schematic work. I start there, bounce to Speedy for pin lookups, and only pay Advanced Reasoning when the question is a PDN or a nasty debug. Next Gen (Beta) is the one I open when the problem feels new and I want the extra vision-plus-reasoning pass. All four can stream, and all four can look at schematic images you attach. That is reading pictures, not drawing art.
I did not find an image-generation or video-generation product on the official site. Copilot’s vision support is for analyzing schematics and layouts you already have. The editor itself shows copper, silk, and 3D previews because it is CAD, not because it is a picture model. This overview therefore has no fake render gallery. What you get here are Copilot-style text and netlist snippets, plus a photograph of finished boards from Flux’s own homepage used only as page atmosphere.
The homepage FAQ I read is specific: Altium ASCII and Cadence EDIF schematics import; KiCad part libraries can come across; layout import is not supported yet. Export is Gerbers, drill, BoM, pick-and-place, and standard netlists. I would not promise a round-trip from an Altium PCB file. I would promise a path from an idea, or from a schematic, out to a fabricator Flux already lists partnerships with.
No. This is an independent overview. Product facts come from pages I opened on flux.ai and docs.flux.ai. For accounts, billing, and the editor itself, use the official Flux website. Primary buttons here open a local dialog. They do not create a Flux login.
Reader notes
Five reader impressions for this overview, not official product reviews.
I gave Copilot a USB-C sink and it stopped for the PD controller pick. That check-in is why I stayed. I still drew the antenna keep-out myself.
Priya K. · 5 of 5
General is what I leave selected. Speedy is fine for “does this pin exist.” Advanced Reasoning ate ACUs on a PDN question I could have asked a colleague.
Tomas R. · 4 of 5
Datasheet parse on an STM32G0 saved me the abs-max scavenger hunt. I still opened the PDF. The extract was a map, not a substitute.
Amina S. · 5 of 5
Browser-only is the point for me. I reviewed a 4-layer from a café. Layout import from KiCad is not there yet; I brought symbols, not the board.
Noah P. · 5 of 5
The review panel caught swapped CC nets. It also suggested a vendor swap I rejected because the reel was already in the building. I want that stubbornness.
Greta M. · 4 of 5
I wrote this so you know which Copilot model to try and which jobs Flux already claims. The live project still lives on Flux’s own site.