Intelligence for engineers who build the real world.
seib is building an Industrial Foundation Model (IFM) for industrial engineering and Physical AI. seib Cowork puts it on your teams’ desks, as a coworker that asks before it changes anything.
- Model
- seib IFM in training
- Coworker
- seib Cowork pilots open
- Scope
- Product intent to physical action
- Approved by
- Request pilot access
- seib IFMStatus In trainingWhere Runs in the EUThe Industrial Foundation Model, purpose-trained on verified industrial engineering work and built to span product intent through to physical action.Explore the model
- seib CoworkStatus Pilots openWhere Cloud in the EU, or on premisesA desktop coworker built first for engineers and open to everyone in the organisation. It plans, reads, queries your systems and delivers finished work, asking before every change.See how Cowork works
Engineering is complex. Change is constant. Time is critical.
In high-mix, NPI-driven factories, products, variants, processes and equipment change constantly, but engineering and commissioning stay too manual and too slow to keep pace.
- 1
Too many systems
Data and tools are siloed across the engineering stack. Requirements, CAD, process plans and controls each live in their own format, and the work of reconciling them falls to people.
- 2
Change outpaces engineering
New products, variants and processes emerge constantly. Engineering and commissioning stay manual, so the factory is always catching up to a product that has already moved on.
- 3
Scarce expertise
Critical knowledge lives in people's heads. That creates risk when they are unavailable and a bottleneck whenever more than one line needs them at once.
- 4
Delay is expensive
NPI and line changes take too long and hit business performance directly. Every week of ramp-up is a week the line is not producing what it was built to produce.
One model across the full engineering lifecycle.
seib IFM is being built to connect product intent to physical outcomes, with every draft clearing a real toolchain of its own before it becomes something you review.
- 1
Product intent
Requirements, CAD, BOM, variants and tolerances, to be read as structure rather than as documents to search.
- 2
Process design
Workflows, operations, quality checks and cycle-time targets, derived from what the product actually is.
- 3
Automation engineering
PLC, robot, vision and tooling code, produced in the target language and simulated before anything is released.
- 4
Factory context
Machines, cells, constraints and real-time data: the plant as it is today, not as the drawing says.
- 5
Physical action
Commission, operate, adapt and improve, with every change held for a person to approve.
The training approach, modalities and safety posture are on the model page.
A model, not a wrapper around one.
Most industrial copilots are a chat window in front of a general-purpose model. seib is being trained on the thing it’s supposed to be good at.
An AI coworker for your engineers, and for everyone they work with.
Built first for engineering and open to the whole organisation, seib Cowork plans the task, reads the documents, queries plant and business systems, and delivers finished work. It shows every change exactly and waits for a person to approve it.
How a task runs.
- 1
Ask
Pick the project folder and write the task in plain words. Knowledge bases and connected systems are already there.
- 2
Plan
Cowork shows its plan first, and asks a clarifying question with ready-made choices when the task is unclear.
- 3
Read
Documents, spreadsheets, mail, PLC exports and the company's own manuals and procedures. Every file read and query appears as it happens.
- 4
Approve
The edit, the SQL statement, the mail, the command: shown exactly, as a diff. Allow it, edit it first, or refuse it.
- 5
Deliver
Finished work opens in a preview: reports, spreadsheets, review comments, drafted replies. Answers cite the document and page.
- 6
Undo
Every file is copied before it changes, so any edit can be undone, one at a time or all at once.
Reads run directly. Writes always ask.
- Databases
- Microsoft SQL Server, PostgreSQL, MySQL and MariaDB, SQLite
- Plant data
- OPC UA (browse, read, history), MQTT and Sparkplug B, AVEVA PI, InfluxDB
- Business systems
- SAP (OData), Jira, Azure DevOps, ServiceNow, any REST API with OpenAPI, GraphQL, MCP servers
- Documents
- SharePoint and OneDrive, project folders, read-only reference folders
- Exchange and any IMAP/SMTP server, Microsoft 365, Gmail. Drafts only by default
- Knowledge
- Your organisation's knowledge bases, searched with page-level citations
Two ways to run it.
- Cloud, in the EU
- seib model hosted in the EU
- Nothing to install on servers. The seib model runs in the EU; project files stay on the engineer's workstation, and only what a step needs is sent, over TLS.
- On-premises
- Your servers, your network
- For organisations that want their own internal model: the seib model, embeddings, knowledge store and policy on your hardware, with no route to the internet.
- Your model, on your servers
- The on-premises edition is designed so every part runs inside the company: the seib model on your GPU servers, knowledge bases on your storage, accounts and policy on your servers.
- Your permissions, unchanged
- Connectors are defined once, centrally, with no passwords in them. Each engineer signs in with their own account, so every system keeps its own permissions.
- Your record of every step
- Each task keeps a tamper-evident, hash-chained audit trail: the request, every action, and who allowed it. Export it as CSV or JSON Lines.
Mission and vision
- Mission
Foundation intelligence for industrial engineering.
seib helps manufacturers understand what needs to change in the factory when the product changes, across engineering, commissioning, and the Physical AI that runs on the floor.
- Vision
Industrial systems that understand and adapt themselves.
Systems that can reason, learn and evolve like the best engineers. One layer of intelligence the plant can think with, rather than a dozen tools it has to be translated between.
Built for the industries that build the world: automotive, electronics, industrial equipment, consumer products, aerospace & defense and energy.
A simple question needs no form.
One line is enough: a technical detail, a procurement question, or where the model is. It reaches a person who can answer it, not a support queue.
Request pilot access.
Not a waitlist. Tell us the problem and we’ll tell you honestly whether seib is ready for it.
- 1A person reads your request and replies within a few business days.
- 2A short call about the line, the toolchain and what's slow today.
- 3A Cowork pilot starts with one team, read-only connectors and two or three knowledge bases.