Skip to content
macro

Manufacturing intelligence · Trusted data exchange

Understand everything.Expose only what you choose.

Macro is building the trusted data layer for manufacturing. Trace yield and quality problems across your factories, partners, and suppliers, while every company keeps control of what it shares.

Built for
Semiconductor and electronics manufacturers
Runs
Hosted, or in an environment you control
Stage
Early. Building with design partners

Corvane Semiconductor

OEM · Final test

Owner: Corvane
LotCompoundBin 7FPY
AL-24147MC-51070.37%97.8%
AL-24148MC-51075.91%91.4%
AL-24149MC-51075.79%92.0%

Talus Assembly & Test

OSAT · Assembly records

Shared on approval
LotLineCureRecipe
AL-24147Line 1v1.8
AL-24148Line 3v2.1
AL-24149Line 3v2.1

Ostrin Materials

Supplier · Lot certificates

Shared on approval
LotReceivedSpecPrice
MC-5107Oct 2In spec
MC-4821Sep 4In spec

Finding · INV-0142

Evidence from 3 companies

Continuity failures track lots that combine compound MC-5107 with cure profile v2.1.

Illustrative · synthetic records Evidence Stays with its owner

01The problem

The answer is usually in someone else's data.

A single chip passes through a foundry, materials suppliers, an assembly house, and a test floor before it reaches your customer. When yield drops, each holds a piece of the story, and good reasons to keep it.

Section A–A · QFN-48 package

7.0 mm0102030405060708
  1. 01

    Evidence is scattered

    One excursion can involve a materials lot, a process change, a tool, and a test program. Each is owned by a different team, often at a different company.

  2. 02

    Sharing is all or nothing

    A partner can send a full export or nothing. A full export carries recipes, prices, and other customers' volumes, so the answer is usually nothing.

  3. 03

    Investigations run on email

    Engineers trade spreadsheets and wait on replies while suspect material keeps moving down the line. The context that would close the case sits one company away.

02The platform

One layer between every system and every partner.

Three capabilities that work as one: connect the data, understand what it means, and collaborate across company lines without giving up control.

01Connect

Bring every signal into one model.

Ingest historical and live data from MES, test, SPC, equipment, and quality systems, plus the feeds your partners already send. Macro reconciles lot IDs, timestamps, and genealogy into a single manufacturing graph.

  • Historical backfill and live streams
  • Lot genealogy across sites and companies
  • Hosted, or run in an environment you control
See connected sources

System view

01 · Connect

macro

01 Connect

Ingest · reconcile · genealogy

02 Understand

Detect · correlate · explain

03 Collaborate

Request · approve · audit

Where it runs

Customer-controlled

Data plane in your VPC or on‑prem. Raw records stay inside your boundary.

Hosted by Macro

The fastest way to start, with a separate environment per company.

How data arrives

Historical backfillLive

02Understand

Find the signal. Show the evidence.

Models watch yield, bins, and parametrics continuously. When something moves, Macro correlates it with material, process, and equipment changes, and an AI analyst explains what it found with citations to the underlying records.

  • Proactive anomaly detection
  • Correlation across lots, changes, and tools
  • Answers that cite their sources
Open an investigation

System view

02 · Understand

macro

01 Connect

Ingest · reconcile · genealogy

02 Understand

Detect · correlate · explain

03 Collaborate

Request · approve · audit

Evidence graph · CV-7

Bin 7 ↑MC-5107PCN-2291TP 4.3TestersWafer lots

Analyst

Failures concentrate in MC-5107 lots. A process change at the OSAT could also explain them; line data is needed to tell which.

03Collaborate

Share the answer, not the database.

When an investigation needs a partner's data, Macro drafts a scoped request. The partner sees exactly what would leave, keeps sensitive fields restricted, and can answer with a derived insight instead of raw records.

  • Field-level, purpose-bound requests
  • Owner approval, expiry, and revocation
  • A record of every disclosure
Try Trusted Exchange

System view

03 · Collaborate

macro

01 Connect

Ingest · reconcile · genealogy

02 Understand

Detect · correlate · explain

03 Collaborate

Request · approve · audit

Partner boundary · Talus (OSAT)

  • Assembly lineShared
  • Cure profile versionShared
  • Line 3 failure trendDerived
  • Cure recipe
  • Other customers' lots
  • Unit pricing

Approved by Talus · purpose INV-0142 · expires in 30 days · every disclosure logged

03Intelligence

From a falling yield curve to a short list of causes.

Macro does the first day of an investigation for you and shows its work: evidence, what it ruled out, and what it still can't see.

Yield drops. Macro notices first.

First-pass yield on CV-7 fell from 97.8% to 93.9% in a week. Macro opened an investigation on the second day below the control limit.

INV-0142

CV-7 first-pass yield decline

Investigating · Synthetic data

First-pass yield · CV-7 · daily

93.9%▼ 3.9 pts vs. 4-week baseline

48,680 units tested this week

Macro reports counts, rates, and open questions, not made-up confidence scores. Correlation is labeled as correlation until someone confirms a cause.

Open this investigation

04Trusted Exchange

Share what the investigation needs. Keep everything else.

Trusted Exchange is how Macro moves evidence between companies. The owner decides what leaves, in what form, and for how long. Every disclosure is recorded.

Try it · You are Talus, the data owner

Simulated with synthetic records

Request EX-0419

Corvane Semiconductor → Talus Assembly & Test

Purpose
INV-0142
Scope
20 lots · Oct 1–10
Access
30 days

Talus decides

Data owner

  • Assembly line

    Which line built each lot

    Policy P-04 · shareable with approval

  • Cure profile version

    Version identifier only

    Policy P-04 · shareable with approval

  • Mold press ID

    Equipment used per lot

    Policy P-04 · shareable with approval

  • Cure temperature & time

    Process recipe parameters

    Locked

    Policy P-01 · recipes never leave Talus

  • Line 3 continuity trend

    Across every product on the line

    Policy P-05 · aggregates only, 3+ customers

What Corvane receives

Live preview · 5 of 20 rows

LotLineCurePressRecipe
AL-24145Line 3v2.1
AL-24146Line 3v2.1
AL-24147Line 1v1.8
AL-24148Line 3v2.1
AL-24149Line 3v2.1

Derived insight · from Talus4 customers aggregated

On Line 3 since Oct 4, continuity failures are elevated only where MC-5107 meets cure v2.1 (4.9% vs. 0.5% for other compound lots).

2 fields shared · 1 derived · 2 withheld. Other customers' lots, pricing, and capacity are never part of the request.

Simulated. Nothing is sent; this is a product concept.

Audit trail

  1. 09:41Corvane · P. RamanRequested 5 fields for INV-0142 · 20 lots · 30 days
  2. 09:44MacroApplied Talus policies · recipe locked by P-01

01

Owners stay in control

The company that holds the data decides what leaves. Requests can be declined, narrowed, or answered with a summary.

02

Purpose-bound requests

Every request names the investigation it serves, the records in scope, and how long access lasts.

03

Field-level permissions

Share a lot ID without the recipe. Share a version number without the parameters behind it.

04

Derived insights

Answer with an aggregate or a yes/no instead of raw records, so other customers stay invisible.

05

Explicit approvals

Nothing moves until a named person on the owner's side approves it.

06

Expiry and revocation

Access ends on schedule, or sooner if the owner revokes it.

07

A complete audit trail

Both sides can see who requested, approved, and viewed what, and when.

Status

Designed with partners

Trusted Exchange is in design with manufacturers. This page and the demo simulate these controls; they do not enforce them yet.

Walk through the full flow

05Approach

Start with one costly question. Grow from there.

Value inside one company first, then across one relationship, then across the network. Trust is earned one exchange at a time.

  1. 01

    Inside one company

    Connect the test, quality, and lot data you already have. Investigate one real, costly excursion from first signal to next steps.

  2. 02

    Across one partnership

    Add one partner and one scoped exchange. Prove the controls on a real question before scaling them.

  3. 03

    Across the network

    Reusable trusted connections and continuous monitoring across suppliers and manufacturers, available to the people and AI systems you approve.

Runs where your data needs to live.

Start on Macro's hosted environment, or keep the data plane inside your own boundary. Partners connect the same way in both models.

Hosted by Macro

Fastest start

A separate environment for your company. Your systems send data to it; partners exchange through it.

Customer-controlled

Data stays in your boundary

The data plane runs in your VPC or on‑prem. Only approved outputs ever cross the boundary.

06 / Design partners

Build the first version with us.

We're working with a small group of manufacturers to shape Macro around real investigations. If yield, quality, or supplier data slows your team down, we'd like to learn from you.

Who we're looking for

  • Semiconductor manufacturers
  • OEMs and hardware brands
  • Contract manufacturers and OSATs
  • Materials and equipment suppliers
  1. 01

    Bring one real problem

    An excursion, a supplier question, or a dataset you wish you could share safely.

  2. 02

    Shape what we build first

    Working sessions with the founding team. Your workflows set the priorities.

  3. 03

    Start without production risk

    Begin with synthetic or historical data. Live systems come later, on your terms.

Design partner inquiry

We use these details only to reply to you. No newsletters.