What we build
The product with its boards, PCBs and stackups, laid out the way the real product is laid out.
Engineering knowledge management for hardware companies
The Business Brain for Hardware Companies.
XKEMA holds the connections between your projects, products, boards, BOMs, components and documents — so your team decides on the full picture, not on whatever is still in someone's head.
No card No migration first English
Connected around the hardware you actually build
- Projects
- Products
- Boards and PCBs
- BOMs
- Components
- Revisions
- Documentation
What XKEMA does
Not an ECAD. Not an ERP. The layer that was missing between them.
Your ECAD knows how to draw the board. Your ERP knows how to buy it. In between sits everything else — which revision shipped, what was on it, which document describes it — and none of that lives in a system. It ends up spread across folders and conversations.
That is what XKEMA keeps. It is why we call it the business brain of a hardware company.
What we build it from
The bills of materials — and behind every component in the library sits all of the company's information and knowledge.
What explains it
Schematics, Gerbers, datasheets and reports, attached to the thing they describe instead of to a folder.
An ordinary Tuesday
“We need another run of the 2018 board”
You open the project folder. Three BOMs with nearly identical names, two Gerber zips, and a schematic PDF nobody can confirm is the one that shipped.
No file is missing. What is missing is how they fit together: which revision came off the line, with which bill of materials, described by which document.
And it almost always ends the same way — ask whoever designed it. If they still work here.
Five projects, and you cope. Two hundred projects and fifteen years of history, and this becomes what your engineers actually do all day.
- /proyectos/2018/sonda-x/
- BOM_v3.xlsx
- BOM_v3_revisada.xlsx
- BOM_final_OK.xlsx
- gerbers_revC.zip
- gerbers_revC_2.zip
- esquematico_antiguo.pdf
- /backup_javier/
- /no_usar/
Does it warn me when a part goes obsolete?
But nobody knows why that component was chosen at the time. You end up redoing analysis that was already done, losing hours, or replacing it with an oversized part just to be safe.
What was this board actually built with?
There are several versions of the BOM, changes scattered across folders and nobody is sure which one reached manufacturing. Before touching anything, you have to reconstruct which components it really carried.
The solution
XKEMA knows how everything relates.
XKEMA does not only store each product. It also keeps its revisions, the bills of materials that go with them, the documentation behind them and the relationships between all of those. So when a component, a board or a revision changes, you can see what depends on it, what may be affected, and what information the previous decision was made with.
ProjectsCreate the project
Productsequipment, boards and PCBs
BOMsconnected to the board that was built
XKEMA
the connections
Componentsone record, every design
Documentsattached to what they describe
Revisionsa new version never erases the old one
Information in a hierarchy
Start from the product, the board or a part number, and you reach everything else.
Nothing ends up orphaned
A document belongs to a project, a board or a component. Never to a folder called “documentation”.
It belongs to the team, not to a person
When someone moves on or leaves, the structure stays exactly where it was.
Going back to an old design
Seven years later, you know exactly what was built.
A customer asks for another batch of a product that has not been built for years. The problem is not finding the files: it is knowing which revision actually reached production, which bill of materials it carried and which documentation belonged to it. With XKEMA, that history is still inside the product.
- Rev A Prototype schematic, Gerbers, 138-line BOM
- Rev B Pre-production schematic, Gerbers, 141-line BOM
- Rev C Production the one that shipped schematic, Gerbers, 142-line BOM, test report
Sample data.
-
1 min
You open the product
You see its boards, the PCBs that go with them and every revision that has existed.
-
2 min
You identify the production revision
Rev C was the one that was built. The earlier ones are still available, but you no longer have to work out which of them was the right one.
-
3 min
You know exactly which components it carried
The bill of materials is tied to that specific revision. There is no need to compare six spreadsheets to reconstruct what reached manufacturing.
-
4 min
Electronic components
Manufacturer, part number, properties and datasheet, on the record somebody already filled in.
-
5 min
You have everything you need in front of you to decide
Schematics, Gerbers, bill of materials and reports stay connected to the right revision. You can check the design without reconstructing its history first.
Product structure
XKEMA understands the product the way your team understands it.
A piece of equipment contains boards. Each board has its PCB, its stackup, its revisions and its bill of materials. And each of those items has its own documentation and data. In XKEMA those relationships are part of the system: they do not depend on a folder structure or on somebody remembering where they left each thing.
- Teams, sharing and engineering tables — the whole product, not a flat list of files.
- PCBs and stackups — Layers, materials and thicknesses on the board's own record.
- Engineering tables — Power, requirements and interfaces, inside the product and versioned.
ORION CONTROL UNIT
-
Main Control Board
Rev C
- PCB ·
- You pull up its bill of materials ·
- Schematic, Gerbers, test report
- Power Supply Board Rev B
- Power budget ·
BOMs and component library
from the line in the list to the record in the central library.
In a spreadsheet, “STM32F407VGT6” is a string of characters. In XKEMA it is a component entered once — manufacturer, properties, datasheet — and reused by the BOM of every design that needs it.
| Ref | MPN | Manufacturer | Description | Qty |
|---|---|---|---|---|
| U1 | STM32F407VGT6 | STMicroelectronics | Cortex-M4 MCU, LQFP-100 | 1 |
| U4 | TPS62130RGTR | Texas Instruments | 3 A buck converter | 2 |
| U7 | SN65HVD230DR | Texas Instruments | CAN transceiver | 1 |
| C12–C18 | GRM188R71H104KA93D | Murata | 100 nF capacitor, 0603 | 7 |
| L2 | 744314220 | Würth Elektronik | 2.2 µH inductor | 1 |
| J1 | 1734035-2 | TE Connectivity | 2-way connector, 3.5 mm pitch | 1 |
- Manufacturer
- STMicroelectronics
- MPN
- STM32F407VGT6
- Class
- Microcontroller
- Package
- LQFP-100
- Supply
- 1,8 – 3,6 V
- stm32f407-datasheet.pdf Datasheet
- an4488-getting-started.pdf Application note
the component record
A component is registered once in the library and the different bills of materials all reference that same record. That way you do not end up with three names, four datasheets and conflicting versions of the information for the same component.
- Electronic components, materials and substances in the same catalogue.
- Each type of component stores only the properties it actually needs.
- Datasheets and technical documentation tied directly to the part they belong to.
Sample data.
Documentation and viewers
Hardware technical documentation, inside the project — XKEMA
When you need the documentation, you can open it directly in XKEMA without hunting for the file first or launching another tool.
- Built-in viewers: PDF, Gerber, stackup, BOM and engineering tables.
- Read-only links that expire, for showing one document outside the team.
- Files are validated by their actual content before they enter the system.
Schematics and PDFs
They open in the browser, right next to what they belong to.
The board record
Design, revision and documentation reachable from one place.
Central library
Properties, part number and technical documentation gathered in the same library.
Revisions and long-term context
Keep moving forward without erasing the history.
Upload a new version of a document, a BOM or an engineering table and XKEMA stores it linked to the previous one instead of replacing it. The chain is on record, with who uploaded it and when.
It does not try to be Git for hardware, nor to compare two files line by line. It solves something far more everyday: being able to come back in five years and understand which version there was, which came next, and what ended up being part of the product.
- New project opened and structured
- Design in your ECAD
- Documentation tied to the product
- Revision a new version never overwrites the last one.
- Production one specific version gets built
- Redesign When all of this has to be opened years later.
- v4 Current version uploaded by Ana R. · 12/03/2025
- v3 J1 connector change uploaded by Javier M. · 04/11/2024
- v2 Design review fixes uploaded by Ana R. · 22/06/2024
- v1 First version uploaded by Javier M. · 09/02/2024
Sample data.
No promises XKEMA does not yet keep
XKEMA does not currently check manufacturer and distributor status, so it will not warn you automatically when a component goes obsolete. What it does keep is where it is used, what documentation is attached to it, and the context you need when the time comes to replace it.
Where it fits
Keep designing where you always have. XKEMA comes along.
XKEMA does not try to replace KiCad, Altium or whichever tool you use. It takes care of everything that sits around the design: revisions, bills of materials, components, documentation and the relationships with the rest of the product.
- Design in your ECAD
- Export
- XKEMA
- Manufacture
Files are uploaded by hand. There is no integration with any design tool today.
Start without complications
Your first product in 10 minutes.
There is no need to prepare a migration or reorganise years of documentation. Start with a real product, create its structure and add the information you already have as you need it.
-
Create the project
Start with a real product. You do not need to prepare a full migration before you begin.
-
opened and structured
Equipment, boards, PCBs and stackups organised the way they really exist in the product.
-
You pull up its bill of materials
Lines point at library records, and those records get reused across your other designs.
-
Where the documentation ends up
Schematics, Gerbers, datasheets and reports, attached to the thing they describe instead of to a folder.
-
You carry on working as usual
New revisions arrive, components change and new designs appear. XKEMA keeps the history and the relationships between them.
Carlos Antonio Benito
Founder of XKEMA
Why this exists
I built XKEMA because I was tired of rebuilding
It kept happening to me: you would open an old project and the files were all there, but working out what had actually been built, which revision was the valid one, or why a particular component had been chosen could take hours.
The problem was not missing documentation. The problem was that everything lived apart, and the context ended up staying in the head of whoever had worked on the design.
That is why I started XKEMA: I wanted a bill of materials to know which board it belongs to, every component to have a single record, and revisions to keep their history instead of replacing one another.
The idea is simple: that in five years you can open a product and understand it without having to reconstruct everything that happened five years earlier.
If this problem sounds familiar, try XKEMA with one of your products and tell me where it still hurts. I will answer you myself.
FAQ
What people usually ask
Do I have to stop using my design tool?
No. XKEMA doesn't replace KiCad, Altium or anything else — it doesn't draw schematics and it doesn't route boards. It organises the project and the information around the design.
Do I have to load everything at once?
No, and I'd advise against it. Start with one product: create its project, upload its documentation, enter the components it uses. That's enough to tell whether the model suits you.
How do I get access?
XKEMA opens by invitation. You leave your email on the waiting list and we write to you when there is room. No card required.
What exactly can I manage in it?
Projects with folders and documents; a library of components, materials and substances; equipment, boards, PCBs and stackups; bills of materials tied to the thing they describe; power, requirement and interface tables; and viewers to open all of it in the browser.
How do revisions work?
A new version of a document, a BOM or an engineering table is stored linked to the previous one rather than overwriting it. What it doesn't do is compare two revisions line by line.
Can I show a document to someone outside the company?
Yes — generate a read-only link with an expiry date for that one document. Whoever receives it needs no account and sees nothing else.
Does it warn me when a part goes obsolete?
No. XKEMA doesn't query manufacturer or distributor status, and I'd rather say so than let you find out. What it does do is keep BOMs and components properly tied together, which is what saves the work when you have to find out where a discontinued chip was used.
Does it work for one engineer, or do I need a team?
It works just the same for one person. Work always belongs to a team, and yours is created when you sign up; if someone joins later, it's already set up.
Where are our files stored?
In cloud object storage, with access checked on every download. Every upload is validated by its actual content rather than its file extension.
Not covered here? Just ask me.
Put one product in and see how much of your history comes back
Leave me your email and I will write when there is room. If you would rather I showed you first, tell me and we will arrange it.
No card No migration first English and Spanish