A teammate, not a chat window
Brief MUZIK the way you brief a colleague. It plans the task, carries it out inside the tools your team already uses, and checks its own work on the way.
Plans the work
A request like “place and route the power section from this BOM” becomes an ordered plan with the steps, the parts, and the rules it will apply, before anything is touched.
Acts inside your tool
MUZIK drives the application directly: it opens the project, places components, routes traces, and saves, using the tool's own scripting and automation interfaces.
Watches the screen
After every step it captures the window, compares what it sees with what it expected, reads the tool's own logs, and corrects course when something went wrong.
Reads any document
Tool manuals, datasheets, standards, internal procedures. In any language and format, including PDF scans. MUZIK extracts what matters into structured records in its own database, where it can search them and your team can look them up.
Follows your house rules
Trace widths, impedance targets, preferred footprints, keepouts, tolerances, materials, and mesh settings live in a MUZIK.md file in your project and shape every session.
Snapshots every change
Before each change MUZIK copies the affected files into a snapshot folder. Undo any step, at any time. It never touches your own version control.
From a sentence to a routed board
Describe the task
Type what you need in the chat pane, with the project open next to it. Attach a BOM, a sketch, or nothing at all.
MUZIK plans
It reads the project files and your MUZIK.md rules, searches the tool's manual where needed, and lays out the steps it will take.
It executes and verifies
Each step runs in the application and is checked against a screenshot and the tool's logs. Mistakes are caught and retried.
You review and keep going
Every change is snapshotted. Accept the result, undo a step, or refine the request and let it continue.
Built for the tools hardware teams actually use
MUZIK works across electronics design, mechanical design, and simulation. Each integration is built against the tool's real automation interface and tested on real projects. MUZIK runs as a desktop application on Windows, Linux, and macOS.
Every tool gets the same loop: plan, act, verify on screen, and snapshot before each change.
KiCAD
PCB layout: placement, routing, design rule checks, netlist verification.
Autodesk Fusion
Mechanical design and the CAD side of the same product.
OpenRadioss and LS-DYNA
Simulation setup, materials, and mesh settings from your rules.
The same engineer, three kinds of work
MUZIK runs one loop, plan, act, verify, snapshot, whether the work is a board, a mechanical part, or a simulation deck.
Electronics design
Placement and routing in KiCAD against your approved footprint libraries and net-class rules.
- Place and route from a BOM and a schematic
- Design-rule and netlist checks before handover
- Approved footprints and trace widths only
Mechanical design
Features, changes and checks in Fusion, with your approved materials, tolerances and fillet rules applied.
- Mechanical changes with approved materials and tolerances
- Wall thickness, fillet and thread rules enforced
- Drawings and exports prepared for review
Simulation setup
Decks for OpenRadioss and LS-DYNA prepared from your materials library and mesh rules, run, and summarized.
- Materials, contacts and mesh settings from your rules
- Batch runs on servers and clusters
- Results summarized with the checks that passed and failed
Your standards, written once
Every team has rules that never make it into the tool: minimum trace widths per net class, the footprint library that is actually approved, wall thicknesses and fillet radii, approved materials, mesh sizes and element types. Put them in a MUZIK.md file at the project root and MUZIK applies them in every session, without being reminded.
The file is plain Markdown. It lives next to your design files, so it is versioned with the project, and every engineer on the team can read it and change it.
# MUZIK.md ## Units Millimeters everywhere. Copper weight 1 oz unless stated. ## PCB (KiCAD) Minimum trace width 0.8 mm on VBUS and 3V3. Use lib/approved.pretty only. No copper within 3 mm of mounting holes. ## CAD (Fusion) Wall thickness 2 mm minimum. Fillet every external edge, R1. Threads: M3 inserts only, no tapped plastic. ## Simulation (OpenRadioss, LS-DYNA) Shell elements, 2 mm target mesh, 0.5 mm minimum. Materials from lib/materials.k only. Report the energy ratio for every run.
Three ways to run MUZIK
Pricing depends on seats and deployment. Every option is updated and supported by LEXIRA. Write to us for a quote.
Online, provided by LEXIRA
The fastest way to start. MUZIK runs on your machines; the model calls and the document index run on LEXIRA's infrastructure. No API keys to manage. A usage allowance is included, and more can be purchased at any time.
- Ready minutes after install
- Usage allowance included, top up any time
- Nothing to host or maintain
Online, bring your own keys (BYOK)
The same desktop application, with the AI running against your own model provider account. You control the provider, the spend, and the data agreements.
- Your own provider keys
- You choose the models and spending limits
- Software subscription, no usage fees
Offline, on your infrastructure
Everything, including the models and the document index, runs on your own servers or air-gapped network. Nothing leaves your site. Installed and supported by LEXIRA.
- No outside connection required
- On-site installation and support
- Scoped per site
Questions we hear first
Which tools does MUZIK work with?
KiCAD for electronics, Fusion for mechanical design, and the OpenRadioss and LS-DYNA solvers for simulation. Each integration is built against the tool's real automation interface and tested on real projects.
Will it change my files without asking?
It works on the steps you asked for, and before every change it copies the affected files into a snapshot folder inside the project. Any step can be undone. MUZIK never writes to your own git repository.
How do I give it our design rules?
Put them in a MUZIK.md file at the project root, in plain Markdown. Units, trace widths, approved footprints, keepouts, tolerances, materials, mesh settings. MUZIK reads it at the start of every session.
Can we add our own documentation?
Yes. Datasheets, internal design standards, application notes, and past project files can be added to MUZIK's document index next to the tool manuals, and MUZIK searches them the same way.
Which platforms?
A desktop application for Windows, Linux, and macOS.
How do I get access?
MUZIK is in early access with design partners. Write to us with a short description of your projects and tools, and we will get back to you.
Add MUZIK to your team
We are onboarding a small number of design partners. Tell us which tools you use and what you would hand to a new engineer first.
Request early access