If you run Hailo accelerators, Microchip's close of the deal on September 21 removed your biggest supplier risk — a startup running out of cash — and left the second-biggest one exactly where it was. Microchip publishes a pledge not to discontinue parts with business activity in the past three years "if they can be manufactured." That pledge is about silicon. It says nothing about the Hailo Dataflow Compiler, the closed tool every model must pass through before a Hailo chip can run it — and that tool ships as a free download under a revocable licence that caps Hailo's liability at $100. The fix is paperwork, and the time to ask for it is now, while Microchip is still courting Hailo's customers.
What Microchip Bought, and What It Actually Promised
Microchip bought a distressed edge-AI chipmaker with a real installed base, and its only public commitment to that base is a plan, not a term. The company announced completion on September 21, less than two months after it signed the definitive agreement on July 24 with a target of closing by the end of the September quarter. Terms were not disclosed, and Microchip says the deal is not expected to have a material impact on its results. Hailo brings the Hailo-8, Hailo-10 and Hailo-15 processors and, per Microchip, "more than 100 customers" and a developer community "exceeding 10,000 users." The closing announcement quotes Mark Reiten, Senior Corporate Vice President of Microchip's Intelligent Compute Business Unit.
The customer-facing sentence in the closing announcement is this one: "Microchip plans to continue supporting Hailo's existing product portfolio, software environment and customer engagements while driving future innovation across AI acceleration, vision processing and intelligent edge computing." Note the verb. Plans to is intent in a press release. It is not a supply agreement, and it does not say for how long.
The seller was not negotiating from strength. Hailo raised $120 million at a $1.2 billion valuation in April 2024, according to Globes; a planned SPAC merger that would have valued it at under $500 million then fell through. Shareholder Delek Automotive lent it $9 million in January at 1.5% a month, and on June 8 Hailo cut about 110 of its roughly 220 employees. Delek is writing off most of its investment, and Calcalist reported industry estimates that the purchase price was "only a fraction" of Hailo's earlier valuations.
One line from the June layoff deserves more attention from customers than it got. Hailo said its core products "have already reached commercial maturity and are distributed by a global network of partners, allowing it to cut internal support teams" (Globes). Before Microchip arrived, front-line support for the installed base — which Calcalist put at over 500,000 units sold — had already moved out of the building.
Why Microchip Is the Best Owner Hailo Customers Could Have Drawn
The strongest case for relaxing is a good one: Microchip is one of the chip industry's loudest advocates for keeping old parts alive, and it writes the commitment down. Its product longevity statement says its annual end-of-life rate was approximately 0.2% in 2022 and 2023 — the vendor's own figure, but a published one. Its "Client-Driven Obsolescence" practice pledges "not to discontinue products with business activity in the past three years (potentially longer for specialized sectors) if they can be manufactured," and says end of life is "only deemed inevitable or permanent when critical components or manufacturing capabilities cease to exist."
Compare that with what a customer had in June: a supplier on emergency loans, a failed listing and half its staff gone. For anyone who designed a Hailo-8 into a camera, a robot or an industrial PC with a ten-year field life, solvency was the risk that kept procurement up at night. It is gone.
It matters beyond Hailo's direct customers, too. Raspberry Pi says its AI HAT+, which carries a Hailo-8 or Hailo-8L at 26 or 13 TOPS and starts at $70, "will remain in production until at least January 2030." That promise — which a lot of prototype-to-pilot vision projects quietly depend on — now rests on Microchip's supply rather than a startup's runway.
Where the Pledge Stops: at Parts That Can Be Manufactured
Microchip's longevity pledge covers manufacturable silicon, and it names its own exception. Three limits matter for Hailo buyers.
It is a practice, not a contract. The document is titled "Our Practice on Product Longevity." It does not mention acquired product lines, and Microchip has not said publicly whether Hailo part numbers inherit it.
Hailo's chips are not made in Microchip's fabs. The pledge leans on Microchip's "ownership of several manufacturing facilities," which it says gives it control over manufacturing of "most products," and it also cites "strategic partnerships with external manufacturers." Hailo's chips come from an outside foundry; the Hailo-8 is built on TSMC's 16nm process. Microchip's separate End-of-Life Policy promises "the maximum LTB/LTS period possible, contingent on the availability from the critical component supplier or inventory levels," and warns that if either is exhausted, the end-of-life date "could coincide with the date of the EOL notification." For a Hailo part, the critical supplier is someone else's fab.
It is about chips. Neither document mentions software, compilers, SDKs or development tools.
None of this predicts that a Hailo part goes away. It identifies which risks the pledge moves onto Microchip's books, and which stay on yours.
The Compiler Is Where the Lock-In Actually Lives
The Hailo Dataflow Compiler (DFC) is the offline tool that takes a trained model in TensorFlow, TFLite or ONNX, quantizes it from float32 to int8, and emits a Hailo Executable Format (HEF) binary — the only form a Hailo chip executes. Hailo describes it as the tool "for offline compilation and optimization of user's models for Hailo devices" in its AI Software Suite. There is no second compiler. If you cannot run the DFC, you cannot put a new model on the chip.
The rest of the stack is more open than people assume. The runtime, HailoRT, is MIT-licensed, with its GStreamer plugin under LGPL, and the Hailo Model Zoo is MIT. The compiler is the exception. Asked on Hailo's community forum whether a paid licence was needed, the answer was that "the software is free of charge and available under the EULA that you agreed to when signing up for the Developer Zone."
Read that EULA. The licence is "limited, non-exclusive, non-assignable, non-transferable, revocable." It permits use "in conjunction with Hailo's proprietary products previously purchased by You" and bars reverse engineering. Hailo "shall make reasonable commercial efforts" to provide support "during Hailo's normal business hours," along with updates "which are made generally available." You may assign the agreement "only with the prior written consent of Hailo"; Hailo may assign it "without Your consent." Hailo's aggregate liability is capped at "One Hundred Dollars ($100)," under Israeli law, in the courts of Tel Aviv.
Here is why that matters more than the chip. A deployed fleet keeps running the HEFs it already has. The compiler matters every time you change the model: a new product on the shelf, a new camera angle, a new defect class, a retrained detector after drift, a fix to an upstream layer. That is the whole operating model of edge vision. Your ability to keep doing it rests on a free, revocable download with a $100 liability cap, which now belongs to a Microchip subsidiary and which you cannot assign without that subsidiary's written consent if your own product line is sold.
The toolchain has also already forked by generation. The Model Zoo README states that "the Hailo-8 and Hailo-8L devices are supported on the Hailo Model Zoo v2.x branch, in combination with the Hailo Dataflow Compiler v3.x branch. The master branch is intended for Hailo-10 and Hailo-15 devices only." The newest release on that master line is paired with DFC 5.4.0 and HailoRT 5.4.0. The Hailo-8 branch is not neglected — v2.19.1, published September 18, added eight new models for Hailo-8 and Hailo-8L — but it runs on its own compiler line, and nothing public commits Microchip to keeping it moving. Version pairing is not cosmetic, either: on Hailo's forum, a user found HEFs from a newer compiler would not run on an older runtime — a user report rather than an official matrix, but exactly the failure an archive has to anticipate.
Microchip also already owns a free edge-AI compiler. Its VectorBlox Accelerator SDK 3.0, released July 14 for PolarFire FPGAs and SoCs, comes out of its FPGA business unit. Two AI compilers in one company is not a prediction of consolidation. It is a question you are entitled to ask before your next design-in.
What Happened the Last Time an Edge-AI Toolchain Froze
The precedent is Intel's Neural Compute Stick 2, and the lesson is that hardware outlives its compiler support. Intel set the NCS2's last order date at February 28, 2022, ended technical support on June 30, 2023, and said OpenVINO would support the device "until version 2022.3, at which point the Intel® Neural Compute Stick 2 support will be maintained on the 2022.3.x Long-Term Support (LTS) release track." Its support note puts it more bluntly: the NCS2 is "supported up to the OpenVINO™ 2022.3.1 LTS release."
The sticks kept working. What stopped was everything new — later model architectures, later operators, later toolkit fixes — for anyone who had not moved on.
That is the pattern to plan for with Hailo: not a sudden shutdown, but a branch that quietly stops moving. We made the mirror-image point about the ADI–Alif deal: with Arm Ethos-U, the model ports through an open compiler. With Hailo, there is no open compiler to port through.
What to Put in Writing Before the Integration Settles
Your leverage is highest now, while Microchip wants Hailo's 100-plus customers to stay. Every item below can start this week.
This Week:
- Inventory every Hailo part in production and in design — Hailo-8, Hailo-8L, Hailo-10H, the Hailo-15 variants, and any Raspberry Pi AI HAT+ fleet — and record, for each deployed model, the DFC version that compiled it and the HailoRT version that runs it.
- Archive the whole build, not just the output. The DFC wheel or Docker image, the HailoRT package, every HEF, the source ONNX, the calibration dataset and the compile scripts, in an artifact store you control. The Developer Zone is a login-gated download under a revocable licence; the logic of mirroring your model weights applies to your compiler too.
- Register for Microchip's PCN and EOL notifications. The EOL Policy says notices go to its PCN page and to registered users by email. If a Hailo part ever gets one, you want it on day one.
This Month:
- Ask your Microchip account team for a letter naming each Hailo part number you buy as covered by Client-Driven Obsolescence, plus a minimum last-time-buy window if foundry supply changes.
- Ask for a compiler support term per generation. How many years of DFC bug and security fixes will the Hailo-8 v3.x branch get, and will Hailo-8 ever compile on the 5.x line? A roadmap that matters is one that funds the next model, not one that promises to keep running the last one.
- Ask for a commercial licence to replace the Developer Zone EULA for production use: non-revocable for HEFs already shipped, assignable with your product line, and liability above $100.
Before Your Next Design-In:
- Ask the VectorBlox question directly: will the DFC and VectorBlox converge, and what happens to HEF compatibility if they do?
- Keep a second compile path. Keep every production model exportable to ONNX and budget one test port to an alternative accelerator, so a forced move is a recompile and a re-validation, not a retrain. When a vendor offers "any hardware," get it in writing; for camera modules, ask the same question about who retunes the model after the sale.
The Bottom Line
Hardware procurement has a mature playbook for obsolescence: PCNs, last-time buys, second sources, and suppliers like Microchip that compete on keeping parts alive. Edge AI moved the lock-in somewhere that playbook does not look — into a compiler that procurement treats as a free download. The Neural Compute Stick showed the industry that a chip can outlive its toolchain. The Hailo deal is the next big test of whether buyers learned that.
Microchip will keep making the chip. Make sure you can still compile for it.
Continue Reading
- ADI Is Buying Alif. Your Model Ports. Your Board Doesn't.
- OpenAI Reportedly Buys Glass Imaging. Who Retunes Your Next Camera?
- Hugging Face Hired Bankers. Go Mirror Your Weights.
- d-Matrix Bought Wallaroo. Get 'Any Hardware' in Writing.
- Valsoft Bought Square 9. Who Funds the Next Model?
- Oakley Bought Graphwise. GraphDB Isn't Open Source.
- Qualcomm Spent $4B to Break Nvidia's Lock on Enterprise AI