TurboPLM manages the things a hardware team actually lives in: the part master, the multi-level bill of materials, revisions and their lifecycles, manufacturing processes, and the engineering change control that keeps all of it honest — then follows the product past release, into what was built and what came back from the field. Start on ours in a minute, or run the whole thing on your own hardware.
Free for one person and up to 100 parts, with no card. Or run it on your own hardware — the whole thing is open source.
| Part | Qty | Rev |
|---|---|---|
| ASM-1100 Frame Assembly | 1 | A |
| MEC-2001 Carbon Fiber Arm | 4 | A |
| PUR-4001 M3×8 Cap Screw | 16 | A |
| ASM-1120 Power Module Assembly | 1 | A |
| ASM-1121 Battery Pack Assembly | 1 | B |
| PUR-4005 Li-ion Cell 18650 | 8 | A |
| ELE-3007 LED Navigation Light Set | 1 | A |
Under three minutes through the real application — the part master, a four-level bill of materials, a structure comparison, a change notice with its dispositions and signatures, CAD in the browser, the CAD BOM reconciled against engineering, serial and lot traceability, and the analytics over the top. No narration; captions carry it.
Recorded before the most recent additions, so materials planning, the document vault, redline review and item-level access are not in this cut — the capabilities above and the live demo below cover them.
Not a document dump with a parts list bolted on — a real product data model with the rules enforced on the server.
Lettered revisions with a lifecycle state machine — In Work, In Review, Released, Obsolete. Released revisions are immutable, enforced server-side, not by convention.
Find numbers, quantities, units, reference designators, an indented structure tree, cycle prevention and where-used. Children resolve to their latest released revision — and a child that has none is shown at its working revision and flagged unreleased, rather than quietly omitted.
Diff any two revisions — or two entirely different products — as one aligned tree. Freeze a structure as a named baseline and compare baselines to each other.
Date-effective BOM lines with an “as of” view, substitute parts per line, and option-driven variants resolved by a configurator.
Typed requirements with decomposition, linked to the parts that satisfy them and the documents that verify them, plus a coverage matrix.
Every upload is a new version, never an overwrite, linked to the parts, revisions and changes it belongs to. The whole history stays downloadable.
Take the lock before you edit and nobody else can upload over you. Locks show who holds them and expire on their own, so a colleague on holiday never blocks the drawing.
STEP, IGES and BREP tessellated server-side by an OpenCascade kernel, plus STL, glTF, OBJ and 3MF — orbit and inspect an assembly with no plugin and no desktop licence.
Pin a comment to a point on a 3D model or an image and thread the discussion there; PDFs and other formats take document-level notes. When a redline turns out to be a real change, escalate it into a change request that carries the whole thread with it.
Read the assembly structure straight out of a STEP file, match products to parts, and reconcile all three views: what was modelled, what engineering released, and what manufacturing consumes.
Per-revision routings: sequenced operations with work centers and setup/run times, each consuming materials — the mBOM alongside the engineering one, reconciled against it.
Declare the stock a machined part draws — alloy, form, net quantity, scrap factor. Explode a build of any quantity into gross material totals and estimated cost, with the parts that declare no material listed just as loudly, because those are the holes you would otherwise order against.
Record what was actually built, not just what was designed. Ask which shipped serial numbers contain a suspect lot and get the list, with the chain of consumptions that put it there — plus an as-built versus as-designed report showing every substitution and unplanned draw.
A unit in the field is not the unit you shipped. Book a repair against a serial number, record the part that came out and the one that went in, and the genealogy updates — so the as-maintained structure stays true years after release.
Nonconformances with severity, quantity and disposition that escalate straight into a change, and CAPAs whose Verify step refuses to advance without a root cause and a corrective action, and whose Close step refuses while any linked nonconformance is still open.
Requests triaged into change notices, affected items with from → to revisions and stock dispositions, effectivity by date or by serial number, and a printable notice for the floor. The rules it enforces →
Signature requirements per role or named signer, password re-entry at the moment of signing, and a printable record carrying printed name, meaning and timestamp. The authentication method is recorded on every signature, so the strength of each one stays auditable. Change what a signer attested to — the affected items, their revisions, their dispositions — and the signature voids itself.
Restrict an individual part, document, change, project or build unit to named people and groups. A restricted item answers exactly like one that does not exist — absent from lists, absent from search, and a plain 404 on a direct hit, because a “forbidden” reply already tells an outsider it is there.
A restricted child on a BOM you can read stays as a Restricted row with its quantity intact — never silently dropped. Roll-ups say so when a total could not be completed, so no one mistakes a censored number for a small one.
Projects with an ordered gate set and deliverables bound to parts, documents, requirements or changes. A gate refuses to pass while an earlier gate is open or a required deliverable is outstanding.
Unit costs rolled through the multi-level BOM, with the parts whose cost is unknown named rather than quietly counted as zero.
Approved manufacturer lists per part, then RFQs with quote comparison, lead time, MOQ, automatic lowest-price flagging and award tracking.
Invite a supplier to quote and they get their own scoped login. They see the lines and their own prices — never a competitor's price, never who won, never an RFQ they weren't invited to.
Drop in a distributor's CSV export — Digi-Key, Mouser, Farnell/Newark and RS Components are recognised from their column headers alone — map the columns once, and see every row classified as new, an update or a problem before anything is written. A careless import is how a part master fills with duplicates.
Most lightweight tools let you edit a BOM and call it a day. TurboPLM treats a change as a governed object, because that is the part auditors, customers and your own future self care about.
A customer programme under NDA, an export-controlled assembly, an acquisition still unannounced — most PLM either gives everyone the whole database or forces you into a second system. TurboPLM lets you close a single item without splitting your product record in two.
404, byte for byte the same as an item that never existed — a “forbidden” reply would confirm it is thereA running instance, seeded with a four-level quadcopter product — two variants that share subassemblies, released and in-work revisions, process plans, a declared material catalog with one part deliberately left unspecified so the planning gap is visible, drawings under vault control with live redline threads, serialised build units with their as-built genealogy, field service records, and changes in flight. Create an account and click around.
Sign up with an email and password, or continue with Google. Accounts are read-only, so you can explore the whole system without changing the shared demo data.
Looking for your own private workspace instead? Start free — nothing shared, nothing read-only.
Prefer your own copy? git clone, docker compose up -d --build,
and you have the same thing on your laptop in a couple of minutes — demo data included.
Get the source →
The live demo is read-only and shared. This is the real thing: your own workspace, your own parts, yours to change. Both plans are the same software — every module, nothing held back for the paid one. The only differences are the two limits below.
No card required. No expiry — it does not turn into a trial.
One price for the whole organisation, not per person.
Start on Free and move up from inside your workspace, the day a second person needs in or the day you reach part 101.
There is no trial of Pro to forget to cancel, and no card on file on Free to charge. Already have an account? Sign in. Would rather run it on your own hardware? The open-source version is free too, with no limits at all.
Product structures, costs and supplier terms are among the most sensitive data a hardware company has. TurboPLM is built to run where you decide.
Run it on a laptop, a NAS or a VM. No seat counts, no usage telemetry, no per-user tax on inviting a colleague.
Your data sits in a database you can query, dump and back up yourself — no proprietary store, no export fee.
Scoped API keys, signed webhooks, ERP-shaped item and BOM export, CSV import that shows you what will change before it writes.
TypeScript end to end, a documented contract between the API and the client, and a schema you can extend.
Clone the repository and bring the whole stack up with Docker Compose — the application, the database and the CAD service, seeded with demo data, in a couple of minutes.
Open source under the GNU AGPL v3: read it, run it, change it, and use it for anything at all. The one obligation is reciprocal — if you modify TurboPLM and offer it to others over a network, your changes have to be published too.
Every one of these works on your own installation just as well as on the hosted
version — including the one that puts it there. Nothing here is a route into our
servers: if you want the open-source build running on your hardware and never to speak to
us again, that is a service we sell, at a price, below.
The software is free to run, and plenty of teams run it alone. These are for the times you
would rather not — a migration you only want to do once, an integration into systems that
are already load-bearing, or a second opinion on decisions that are painful to reverse.
Prices are starting points, not quotes: scope moves them, and you get a fixed number before
anything begins.
Your existing part master and bills of material — spreadsheets, an old PLM, or exports from CAD — loaded, structured and reconciled, with the numbering and revision scheme agreed first. Into your own installation or the hosted version, whichever you have chosen.
Wiring TurboPLM to the systems around it: item and BOM sync, CAD exports, and the handoff to purchasing and production.
The open-source build, running on your servers, your cloud or your NAS — hardened with backups, TLS, accounts and access groups, then handed over with a runbook so you operate it without us. No licence, no seat count, no ongoing fee unless you want one.
Part numbering, revision strategy, release gates and change process — the decisions that are cheap to make once and expensive to revisit after three thousand parts carry them.
TurboPLM is open source, so every bug fix and security patch is published and yours for free, whether you pay us or not — you are never buying access to a fix. What a support agreement buys is priority, a response time you can plan around, and somebody who performs the upgrade instead of writing you instructions.
GitHub issues, answered when we get to them. Every release, every fix and every security patch, same as anyone. Plenty of teams need nothing else.
A reply within one working day. Your bugs triaged ahead of the queue. Security patches flagged to you directly rather than found in a changelog, with upgrade notes for your version. You run the upgrade; we tell you what is in it and what to watch.
Everything above, and we do the work: scheduled upgrades performed on your instance in a window you choose, your backups restored into a scratch database and verified each quarter, and a same-day reply when something is wrong.
What none of these cover: your hardware, your network, your own database tuning, and code you have changed yourself. The licence lets you modify TurboPLM freely — but a fork is a different product, and supporting one is a conversation rather than a plan.
Tell us what you build and where your product data hurts. We will come back with a straight answer on how we can help. No obligation.