Build on time.
Kepler is the AI-native material planner for aerospace, defense and dual-use hardware. It finds the shortages that threaten a build and drafts the fix before production slips.
Starts on four exports from your ERP. Nothing to replace.
Projected on hand, by part and week
| Part |
|---|
Example build with synthetic parts and suppliers.
The plan looks fine in ERP. The build still slips.
A shortage rarely lives in one place. It hides across the MRP run, a quality-hold spreadsheet and a supplier's email. Planners reconcile them by hand, and the one that matters surfaces days too late.
IOB-3 short 12 from Nov 9
6 DRV-A on quality hold, not in ERP
BAT-260 now ships three weeks late
Found days later, by hand.
Four exports in. A ranked action list out.
Kepler nets every part against every build date, ranks what will actually stop the build, and prepares the next move for your planner.
- Bill of materialsParts and quantities
- Build scheduleQuantities and dates
- InventoryOn hand and on hold
- Open purchase ordersSupplier dates
- 1Ranked shortagesOrdered by build impact, with the math behind each one.
- 2Next action draftedExpedite, verify stock, send an RFQ or ask engineering for an alternate.
- 3Tracked to closureEvery approval and supplier reply logged against the build.
Netting runs by part, quantity and date. Every shortage traces to rows in your own files.
Root cause, part-number matching and supplier messages, written for your planner to review.
Substitutions, sources and purchase orders stay with your team.
Tell us what you build.
Same engine, different parts. Pick your world to see a typical shortage and what Kepler prepares.
Example scenarios with synthetic parts.
Start with the planner. Add the rest of the material team.
Every account starts with a Kepler forward-deployed engineer who answers your questions, builds the reports and dashboards your team needs, and recommends fixes. What repeats becomes a module.
Illustrative examples with synthetic parts and suppliers. Roadmap modules and timing are plans.
On your build, with your planners.
A pilot is one real build, scored on numbers you choose before it starts.
- Week 1Send four exports
BOM, build schedule, inventory and open POs, as files. No integration project to start.
- Week 2See your shortages
Every shortage ranked with the math behind it, reviewed line by line with your planners.
- Weeks 3–10Run one live build
A paid pilot on real data. Success criteria agreed up front; the fee is credited to your first year.
- After the pilotExpand across programs
More programs and sites, then the next module when your team asks for it.
Starts on the files you already export.
- SAP
- Oracle NetSuite
- Epicor
- Plex
- Infor
- Microsoft Dynamics 365
- Sage
- Odoo
- Arena
- PTC Windchill
- Siemens Teamcenter
- Excel
- Google Sheets
- Outlook
- Gmail
Kepler reads exports, so a pilot needs no write access. Direct connectors come once a pilot proves the workflow.
Built for controlled programs.
Every shortage links back to the rows that produced it.
Nothing goes to a supplier or into ERP without a named approver.
Pilots run on exported files, with no access to your live systems.
SOC 2 and CMMC Level 2 readiness, ahead of handling controlled data at scale.
“Tell me which programs are at risk before the VP asks me.”
Send four exports. See your shortages in days.
We are taking a small number of design partners building aerospace, defense and dual-use hardware.
Book a call