faezor

AI-Accelerated Embedded Engineering

A new way to build embedded systems, IoT products, automotive ECUs, robotics, connected devices and PCBs.

faezor keeps one structured specification for your device and develops the circuit board, the housing and the firmware from it, then proves them together in simulation: one toolchain and one source of truth, with every decision traceable.

A delta-robot vision controller, built end to end with faezor.

A delta-robot controller made with faezor: its circuit board between the base and the cover of its sealed housing, with the specification items its parts answer.

faezorspecs

One specification that every module builds on.

Requirements, interfaces, constraints and the decisions behind them live in one structured document. The board, the housing, the firmware and the simulation all reference it and are checked against it, so they never drift apart. Change a requirement and you see exactly what it touches.

faezorspecsDelta-robot controller · specification

faezorpcbCircuit board

  • Reverse-polarity switch and transient clampPWR-01
  • Three stepper drivers with stall detectionMOT-01
  • Camera port with its own supply railsVIS-01
  • Pump and valve switches, vacuum sensor inputGRP-01
  • Hardware E-stop switch, over-voltage cut-offSAF-01PWR-01

faezorcadHousing

  • Connector opening with a sealing faceMEC-01
  • Camera window with an O-ring sealVIS-01MEC-01
  • Tongue-and-groove seal round the jointMEC-01
  • Pressure-compensation ventMEC-01

faezorfirmwareFirmware

  • Finds parts by colour in the camera imageVIS-01
  • Delta kinematics and smooth motor rampsMOT-01
  • Vacuum grip with seal detectionGRP-01
  • E-stop state and status to the PLC over CAN FDSAF-01

faezorsimSimulation

  • The robot cell in 3D: camera, arms, partsVIS-01MOT-01GRP-01
  • Breakpoints that stop the robot with the firmwareMOT-01SAF-01

The modules

From specification to a proven device.

faezor

One project and one conversation for everything.

In the middle is faezor: you describe what you need, it keeps the specification current and hands the work to the module that does it, in the right order and with everything the others already decided.

faezorspecs

Requirements become a specification.

Bring what you have: customer specifications, existing documents, datasheets, standards. faezor turns them into numbered, testable requirements, asks where something is open and keeps every revision.

  • Customer specification
  • Datasheets
  • Existing BOM
  • Notes and sketches

PWR-0124 V industrial supply: survives reverse polarity and 36 V transients.

MOT-01Drives three stepper motors, homes them without end switches.

VIS-01A camera looks down through the housing and finds parts by colour.

GRP-01Vacuum pump and release valve, with a vacuum sensor.

faezorpcb

The circuit board, engineered.

Component selection against your requirements and live distributor stock, schematic, placement and routing, electrical and design-rule review, and manufacturing data for the fab and assembler of your choice.

faezorcad

A housing around the real board.

Parametric CAD from the board's outline, holes, connectors and component heights: sealing joints, bosses and mounting points included. Clearances, walls and openings are checked on every change, ready for casting, machining or printing.

faezorfirmware

Firmware for the actual pins.

The pin map is generated from the schematic, so code and hardware cannot disagree. Every change is built and tested automatically, in an isolated environment.

/* pins.h - generated from the board's netlist */

/* U1 pin 39 PE9 - net M1_STEP: U2.STEP */
#define M1_STEP_PORT 'E'
#define M1_STEP_NUM 9

/* U1 pin 57 PD10 - net DRV_EN: U2.ENN, U3.ENN, U4.ENN, R35.1 */
#define DRV_EN_PORT 'D'
#define DRV_EN_NUM 10

/* U1 pin 30 PA6 - net CAM_PCLK: J2.PCLK */
#define CAM_PCLK_PORT 'A'
#define CAM_PCLK_NUM 6

faezorsim

Prove it before you build it.

The firmware runs on a virtual model of the board, its sensors and actuators in a physics simulation. You see behaviour and measurements before the first prototype is ordered. Built on Godot, a powerful, cross-platform open-source game engine.

Try it: a robot cell, live in your browser

faezorfleet

And after delivery: the devices in the field.

Onboard devices, roll out releases, set variables, read logs and open a remote terminal, for boards with a Linux host. Built on openBalena, an open-source fleet platform that runs on many devices worldwide.

Quality

Automatic tests for every domain.

Every change runs the checks of every module against the specification.

Simulation, live

Digital Twin included.

A delta robot sorts parts by colour. Its controller's firmware runs here, in your browser: it reads the camera, finds a part, computes the arm angles and drives the motors. Set a breakpoint, and the robot stops with it. Tap the belt to add a part.

Ownership

Your design, in standard formats.

Opens in the tools your team already uses. No lock-in.

Start

Start with your requirements.

Describe the device, attach existing specifications, datasheets or sketches. faezor turns them into the structured spec, asks where something is open, and starts the modules.

Add a sketch of your board: outline, where connectors and parts go.Add a sketch of your board.

faezor in your own agent

Claude, Codex, OpenCode, Copilot: any agent that speaks MCP.

The same projects over MCP: list your boards, start a design, follow its run, fetch the files.

https://faezor.ai/mcp

Streamable HTTP · OAuth sign-in with your faezor account · no API key

Codex OpenAI · CLI, IDE extension and app

Terminal
codex mcp add faezor --url https://faezor.ai/mcp
or ~/.codex/config.toml
[mcp_servers.faezor]
url = "https://faezor.ai/mcp"

The command opens your browser to sign in; after editing the file, run codex mcp login faezor. The CLI, the IDE extension and the app share the file.

Claude Anthropic · Claude Code, claude.ai and the Claude apps

Claude Code
claude mcp add --transport http faezor https://faezor.ai/mcp
claude.ai, Desktop, mobile: connector URL
https://faezor.ai/mcp

Claude Code: /mcp → faezor → sign in. Apps: Customize → Connectors → Add custom connector, paste the URL, Add, then Connect.

OpenCode Open source · terminal agent

opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "faezor": { "type": "remote", "url": "https://faezor.ai/mcp" }
  }
}

Then opencode mcp auth faezor, or sign in when OpenCode asks on first use.

Muse Meta · Muse Code

~/.config/muse/settings.json
{
  "schema_version": 1,
  "mcpServers": {
    "faezor": {
      "type": "streamable-http",
      "url": "https://faezor.ai/mcp",
      "mode": "optional"
    }
  }
}

Then muse mcp login faezor. With existing settings, add the entry under mcpServers.

Copilot GitHub · Copilot CLI and VS Code

Copilot CLI
copilot mcp add --transport http faezor https://faezor.ai/mcp
.vscode/mcp.json
{
  "servers": {
    "faezor": { "type": "http", "url": "https://faezor.ai/mcp" }
  }
}

Both ask you to sign in when the server first starts.

Needs a faezor account: your first PCB design is free. Create an account

Read the docs

Free while it is a beta

Sign-up is open.

Premium is not available yet. Leave your email and we will write when it is.

IncludedBeta, €0Premium, later
PCB designsOne free designMore designs
Every module and faezor's chatIncludedIncluded
Agent runs on your designUp to 5 a dayLonger runs
The KiCad project and every fileIncludedIncluded
Read-only share linksIncludedIncluded
The queueIn turnPriority
Board sizeSmall to medium boardsLarger boards, more layers
Start designing