Skip to content
Moduloa
← Index
MOD-01 · Stage 0, pre-revenue

Manufacturing

Active BuildProduction systems

Built to print. Billed at cost.Made again.

Moduloa is designed to build mechatronic products for the companies that design them. Our aim: take the complexity of production off our customers' desks, bring each unit's landed cost as low as the design allows, and keep making it for as long as the product lives.

Stage 0. A thesis, draft tools and dated predictions. No hub is certified, no customer has been charged, nothing has shipped. This page describes the system as designed.

From your design to your customer's door

  1. Your design
  2. The price
  3. The blueprint
  4. The route
  5. The parts
  6. Assembly
  7. The shipment
  8. The record
  9. The next order
  10. Where it stands
  11. Your move
Your design

You send the design. We build exactly that.

Moduloa is built for mechatronic products: a circuit board, its firmware, and mechanical parts in any material, from metal to fabric, joined however the drawing says, by screws, adhesive or tape. We do not design your product. We design how it is built.

Built to do

Will not do

  • Design your product or approve its design
  • Make circuit boards or machined parts, for now
  • Hold your finished stock

You own the design. Moduloa owns the process: every unit matches your released revision, measured and recorded. We flag what we see in a design and hand it back, and the record settles what came from where.

The Nordic standard delivery terms draw the same line between design and workmanship (NL 17).

The price

You pay landed cost. Moduloa earns on the subscription.

The quote is designed to be computed, not negotiated: an estimated landed cost, every line with its confidence, plus one yearly fee for the capacity and lead time you reserve.

In your unit price, at documented cost

  • The costed BOMEvery part bought at cost, every line shown.
  • FreightSuppliers to hub, and hub to the address each order names, quoted delivered (DAP).
  • Assembly and testAt a published rate card.
  • Duty and exchange rateDuty at cost where the delivery term includes it, the rate named to its series and date.

Where Moduloa earns

  • The capacity subscriptionSet by units a year and how fast they ship, one formula for everyone, a second hub qualified for your product included. Never sold past 85 percent of a hub's nameplate. A missed lead time comes back as service credit.
  • Hub feesHubs pay Moduloa for certification, the factory OS, blueprint deployment or routed production. Where a hub passes such a fee on, it is shown as its own line in your price.

Materials were about 73 percent of the value of US circuit board assembly shipments in 2021, so every BOM line is shown and reconciled against real invoices. The subscription is the premium for optionality that P-09 expects customers to pay. Nothing has been charged yet. The full model, with its limits · The terms

The blueprint

Written once, built the same way at every hub that runs it

Moduloa writes each build down once as a versioned blueprint: the BOM, a fixed sequence of steps, and the jig and test each step uses.

The jigs and fixtures that flash, position and carry parts are the one thing Moduloa is designed to make itself, to one standard, so every hub on a blueprint revision would use identical ones. The method travels with the blueprint, and the factory OS would version both.

Moving a qualified product to a new site takes a year or more for automotive-grade electronics. It is fast only where the new site runs the identical process. Intel moved products between fabs running its Copy EXACTLY! process with no requalification beyond a mask check; before that method, a new fab took about a year to match yields. Intel Technology Journal, Q4 1998. Whether that works between companies is P-27, due 30 June 2027. It is still open, and the Journal follows it.

How long a move takes today, by product
  1. Emergency moves between trusted suppliersdays to weeksshared designs, everything else dropped · MIT Sloan Management Review, the Toyota group and the Aisin fire, Skoda Auto, wiring harnesses moved in five weeks (2022)
  2. Automotive-grade electronicsa year or morequalification samples must come from the site that will deliver · Semiconductor Engineering, Automotive IC Shortage Drags On (2021), AEC-Q100 Rev J
  3. Defense parts6 to 9 months of testing for one part; about 2 years for a missile motor sourcegovernment source approval · GAO B-261954.4 (1996), GAO-18-45, Solid Rocket Motors (2017)
  4. High-risk medical devicesa 180-day FDA supplement, after the validation workmoving the site of a finished device · FDA, PMA Supplements and Amendments
  5. Pharmaceuticals18 to 30 months for a technology transfera new ingredient supplier alone takes 12 to 15 months · Outsourced Pharma, reporting a McKinsey survey (2020), Sardella, The US API Infrastructure (2021)

Published durations for each kind of product. Some are a regulator's review alone, some a whole transfer, so they are not added up.

The route

Each order takes the cheapest path that meets your lead time

Hubs would be certified by Moduloa by domain, such as medical or automotive, and by size class, on top of the ISO certificates each domain requires. Not every hub would carry every class, because that would be waste.

One published rule set would send each order through qualified suppliers and certified hubs, on the path with the lowest landed cost that meets your lead time, and log its reasons. When a route goes wrong, the rule is fixed for everyone. An order can split across hubs already qualified for your product, most products would run at two, and each unit's record names its hub, blueprint version and part lots.

Over time, where demand persists, the route is designed to lean toward your customers: local suppliers qualify, and more of the product is made nearer the people who buy it.

Over time, nearer your customers: the evidence and its limits

Routing starts near the material, since China makes about 28 percent of the world's manufacturing value added. Where demand persists, local suppliers can qualify and supply the hub, as more than 100 in Kentucky now supply Toyota's plant there. Building near demand avoids the tariff on the finished product, about 11 percent on average in the US, against freight's historical 4 percent of import value, and it cuts transport emissions where it replaces air freight or long truck hauls, which emit many times more per tonne-kilometre than a ship.

The limits: Toyota's localization took about a decade, very high volume, deliberate supplier development and political pressure, and decades of export assembly in Mexico brought little local supply. Suppliers locate near many assembly plants within a day's drive, not one, so it takes a regional network of hubs. Replacing a container ship saves little carbon. Landed cost falls only where local production stays below importing plus duty, a gap automation narrows. The end state is on the record as P-16, due 2046, and is not proven.

The parts

Parts arrive at a line that is already set up

Suppliers would qualify once, against one published standard, and could then supply any customer, with a supplier you already use qualifying first. Xometry, Protolabs Network and Fictiv already audit suppliers before routing work to them, and Xometry and Fictiv first require a test part.

Because demand is reserved, the line is designed to be set up from the blueprint before the parts arrive, and taken down or duplicated as demand changes. Robots doing that setup is the design target, and each new layout would be validated for safety where it stands.

No paper, no pick lists: each part is designed to be scanned to its BOM line on arrival and carried to its station by mobile robots.

BCG puts setup and re-engineering at roughly 75 percent of a traditional robot deployment's lifetime cost: the cost a blueprint is designed to cut. That is the cost of automating a job, not the cost of a product. Even halved, it would stay the largest line.

Assembly

Built by the method, not by whoever is on shift

Assembly, flashing and test are designed to follow the blueprint step by step, every action recorded: station, executor, measurement, time. The floor is designed for robots, so the method never depends on who is on shift. People design, maintain and improve the system, and own its exceptions.

Humanoid assembly is the design target, added as robots prove it. By Moduloa's own index, today's humanoids are 10.1% of the way to humanoids that could run a Moduloa hub (as of 2026-10-02). Moduloa's own methods for the hard steps would travel in the blueprint, written against a hardware abstraction layer that does not yet exist for humanoids. Building or adopting one is part of the work.

The shipment

Packed one way, shipped to your customer's door

Packing and labelling are standard steps in every blueprint, the same at every hub. Each order is designed to ship from the hub to the address it names, your warehouse or your customer's door, so you need not hold stock. Benchmark and Sanmina already offer delivery straight to end customers.

Who imports in each market is settled before the first quote, because importing takes entities, bonds and real liability in each country.

The record

Your customer opens the box. You can open its record.

Every unit is designed to carry a code that opens its record behind your sign-in, and the same record by API: each part with its serial or lot, each step with its station and time, each test with its result.

Moduloa is designed to run the production quality system and own every production metric, so you need not staff production quality yourself. Design verification stays yours, and if you are the legal manufacturer of a regulated product, your own quality system still has to control Moduloa as an outsourced process (ISO 13485, clause 4.1.5); the unit record is designed to feed it. No sales layer and no status decks: you see what we see. Every product would have a named quality owner, and every complaint would enter the quality system with its response time on record.

A fault would be traced to the step, part and blueprint version behind it, and the fix would reach every hub running that blueprint through change control, validated at each site.

The unit record is described and its API is not written yet. Neither is built.

The next order

Order again, for as long as the product lives

A reorder runs on the same blueprint, qualified suppliers and tooling, at whichever certified hub the route picks. The blueprint that built the first unit builds the ten-thousandth, and the record shows it.

A chipmaker owes as little as six months' notice before a part's last order, so continuity is designed in: every part on your BOM would be watched, and you would be warned at the first notice. You choose a last-time buy, a qualified substitute or a redesign, and you see any substitute before it ships.

None of this runs yet. Here is exactly where it stands.

Where it stands

Step 1 of Stage 0, doctrine and artifacts, was completed on 16 July 2026: the thesis, the calculator, the scorecard and the contact map. Step 2 is next: 10 to 20 interviews with people who have run production, to find where the thesis breaks.

Behind the nine stops are five projects on one shared foundation: CHEQUER for the price, PYX for the suppliers, WAYBILL for the route, JACQUARD for the floor and TOUCHMARK for the record, all designed to stand on the factory OS data model, not yet written, and the EX-100 example. Every open task is on the task board.

Stage 0

Before the first factory

The pre-factory period: thesis testing, network building, learning, and artifacts.

0–3 monthsDoctrine and artifactsComplete · 2026-07-16
3–6 monthsInterview and validateIn progress · since 2026-07-16
  • 10–20 expert callsOpen
  • Thesis revised: only if the interviews expose a flawOpen · conditional
  • First partner / customer hypothesesOpen
6–12 monthsProof artifactsNot started
  • Factory OS data model sketchOpen
  • Modular cell libraryOpen
  • Tooling standard v0.1: modular-cell fixture interfacesOpen · scope →
  • Sample quote modelOpen
12–24 monthsSystem design and pilot preparationNot started
  • Pilot product categoryOpen
  • Candidate hub criteriaOpen
  • Advisor groupOpen
  • Funding logicOpen
24–36 monthsHumanoid readiness and first pilot designNot started
  • Humanoid readiness scorecardOpen
  • Robot task libraryOpen
  • Pilot hub planOpen
  • Investor thesis v0.5Open

LockedStage 1, the first factory, opens when Stage 0 is complete: a real product run through the blueprint, the factory OS and certified-hub discipline, with humanoid assembly added as it matures.

Your move

Where you come in

It takes software builders, manufacturing veterans, patient capital and pilot partners with real products. Who this takes

Build log

What has happened

2026-10Manufacturing

Six bets on our own work recorded

The register now holds claims about Moduloa itself, frozen and dated like the rest. They bet on groundwork, not finished systems: a first open factory OS data model by March 2027, a first supplier qualification standard, a first worked EX-100 quote and a first contributor delivery by May, a first jig set by August, and a first named pilot by the end of 2027. Missed dates are scored wrong in public. See P-30 to P-35 →

2026-10Manufacturing

Monthly recap: September 2026 published

September's four field notes found the framework under construction as robot evaluation, two new standards and an honest account of integration cost, and found each piece built beside the work rather than inside it: the qualified process, the site and the people who make a cell produce. Read it →

2026-09Manufacturing

Monthly recap: August 2026 published

August's eight field notes converge from different directions: the compliance date and the tariff rate moved again, the ramp curve and the reference cell arrived early, and the interface between a robot and the system that holds the order turns out to be the layer still missing. Read it →

2026-08Manufacturing

Monthly recap: July 2026 published

The first monthly recap synthesizes July's twelve field notes: a first half tracing the humanoid execution layer, where the value keeps landing beside the robot, and a second half that turns inward to price the framework itself: capacity, admin, landed cost, and currency. Read it →

2026-07Manufacturing

Track merged in: the unit record absorbs MOD-03

The product-lifecycle exploration converged with the flagship: structured production data from first part to last is now the unit record. Per-part identity under the marking requirement, build history minted as sub-assemblies close, and customer APIs. The brand keeps a short list, and lets work converge. The merge note →

2026-07Manufacturing

Journal opened: weekly researched field notes

A public journal for research on humanoid robotics, manufacturing economics, and reshoring, refreshed each week by an automated deep-research pass and recapped each month. First note: the state of humanoid work in mid-2026. Read the journal →

2026-07Manufacturing

Who this takes: the team page published

The honest requirements: a serious software organization with IT/OT security at the core, manufacturing veterans from Asia and beyond, capital that understands platform economics, and pilot partners with real products. Deadlines and weekly automated review added to the predictions register. Read it →

2026-07Manufacturing

Predictions register recorded: the first 25 claims on the record

The thesis boiled down to its falsifiable core: claims about humanoids, manufacturing economics, Norway, and Moduloa itself, frozen with audit horizons at 2031, 2036, 2046, and 2056. Read them →

2026-07Manufacturing

Tier calculator and hub scorecard published, v0.1

The two artifacts the thesis names for Stage 0, built as client-side tools with URL-encoded state so every result is a permanent, shareable link. The models are deliberately simple drafts, published to be challenged in the expert interviews.

2026-07Manufacturing

Working thesis v0.2 compiled

Vision, production tiers, factory OS, certified hubs, business model, risk register, and the Stage 0 execution plan, written down so it can be reviewed honestly later. Read it in full →

Documentation, decisions, and build logs accumulate here. Everything is public.
Discussion

Add to this

Corrections, evidence, and disagreement are welcome. This is knowledge in the open. Anyone can read; sign in with GitHub only to post or react, and it appears here instantly.

Ask Datum