LightSource vs. Arkestro
Arkestro is a predictive procurement platform: it compresses multi-round sourcing events by generating AI-suggested prices before suppliers bid, and runs alongside suites like Coupa and SAP Ariba. LightSource is the Direct Materials Operating System: the system of record for parts, BOMs, RFQs, and awards, from spec through scale, PLM through ERP.
| Attribute | ![]() | ![]() |
|---|---|---|
| The short version | LightSourceLightSource is the AI-native Direct Materials Operating System, spec through scale, PLM through ERP: revision-managed parts and BOMs, part-level RFQs with flexible cost breakdowns, AI quote analysis, and awards that become tracked price history. Teams are live in days, and suppliers use it free. | ArkestroArkestro is a predictive procurement platform: it compresses multi-round sourcing events by generating AI-suggested prices before suppliers bid, and runs alongside suites like Coupa and SAP Ariba. |
| Built for | LightSourceDirect materials, spec through scale: parts, BOMs, NPI programs | ArkestroPredictive sourcing events across category spend |
| Core question | LightSourceWho should make this part, and at what price? | ArkestroWhat price should this event open at before suppliers bid? |
| Architecture | LightSourceAI-native direct materials operating system, built around the part record | ArkestroPredictive pricing layer; offers and awards sync to SAP, Oracle, Coupa, or SAP Ariba |
| Implementation | LightSourceLive in days on flat files; sourcing in about 30 days; implementation included | ArkestroEnterprise rollout; Arkestro cites results in as little as two months |
| Pricing model | LightSourcePlatform plus seats; implementation included; always free for suppliers | ArkestroNot published; Capterra's third-party listing shows a $500 per month starting point |
| Supplier network | LightSource100,000+ suppliers live; free supplier workspace; AI discovery | ArkestroYour incumbent supplier list; suppliers respond to suggested prices inside events |
| Target customer | LightSourceManufacturers from growth stage to enterprise divisions | ArkestroEnterprise procurement teams; most G2 reviewers are mid-market |
| Public evidence | LightSourceNamed customers on record; G2 4.9/5 on about 11 reviews; Gartner Cool Vendor 2025; Hackett 50 to Watch 2025-26, evaluated in SolutionMap Sourcing and Direct Sourcing | ArkestroFounded 2017; about 11 G2 and 4 Capterra reviews; Hackett 50 to Watch 2025-26 and in its 2026 sourcing and spend analytics guides; named enterprise customers and public case studies. |
Where each system actually works
The procurement landscape reduced to what matters for this comparison: three rows across the nine lifecycle stages, one lane per product. Orange bars are where LightSource operates, outlined bars are where this vendor does; solid means native in practice, dashed partial, dotted claimed but not evidenced.
Capability comparison, in detail
Fifty-two capabilities in twelve groups, aligned to the areas on our interactive procurement technology map. The LightSource column is identical on every comparison page, including the ones we don’t win.
| Capability | ![]() | ![]() |
|---|---|---|
| 1 · Define and intake | ||
| Parts, drawings and metadata | LightSourceStrong Item master with drawings, custom properties and frozen revisions; AI extracts items from PDFs and sheets | ArkestroNot documented Not publicly documented; parts enter events as line items, with no drawing, spec or item record |
| BOMs | LightSourceStrong Multi-level BOMs with cost rollup from quotes or contracts, revision diffs and cost history charts | ArkestroNot documented Not publicly documented; BOMs, revisions and cost roll-ups appear nowhere in its public materials |
| Should-cost, VAVE and design-to-cost | LightSourceModerate Should-costs and target costs on each item serve as bid baselines; no built-in cleansheet modeling tool | ArkestroLimited Native: predicted baseline prices for new items from quote data; no bottom-up cost models or VAVE |
| PLM (system of record) | LightSourceIntegrates PLM stays the engineering record; items, BOMs and files sync in by external ID via the API or spreadsheets | ArkestroNot documented Not publicly documented; the integrations page names ERP, S2P and CLM systems but no PLM |
| Category management and strategy | LightSourceModerate Item categories with their own properties, category charts and Programs inform category plans | ArkestroLimited Marketed: Opportunities co-pilot (beta, Oct 2025) suggests line-item sourcing actions; no category plans |
| Intake and orchestration | LightSourceNot offered No requester intake front door; work starts at the item, BOM or Sourcing project | ArkestroIntegrates Configured: Zip and ServiceNow listed as API and webhook connectors; no native requester front door |
| 2 · Discover suppliers | ||
| Supplier engagement and early involvement | LightSourceStrong Early supplier involvement and design collaboration: data rooms, RFIs, threads, drawings shared by revision | ArkestroNot documented Not publicly documented; suppliers enter at the event with suggested prices, no DFM or design input |
| Supplier capability mapping | LightSourceStrong Supplier Discovery searches by process or material; profiles hold specialties, sites, tags and properties | ArkestroNot documented Not publicly documented; supplier recommendations are marketed, with no equipment or process record |
| Spec-to-Scale system of record | LightSourceStrong One record from item and BOM through RFQ, quote, award and Awarded contract, between PLM and ERP | ArkestroNot offered Outside scope; a predictive pricing layer over events, with no part, BOM or cost-breakdown record |
| Supplier discovery | LightSourceStrong Supplier Discovery across 100,000+ suppliers by process or material; LightSource contacts the ones you pick | ArkestroLimited Marketed: recommends suppliers from procurement history; events run on the buyer's own suppliers |
| GPOs and buying consortia | LightSourceNot offered No GPO or consortium buying; LightSource runs your own Sourcing projects | ArkestroNot offered Outside scope; Arkestro is a sourcing tool with no GPO or buying-consortium contract features |
| 3 · Source | ||
| Spec-aware sourcing (RFQs with drawings) | LightSourceStrong Sourcing projects built from items with drawings; per-item quote formats drafted by the RFX Setup Agent | ArkestroLimited Native: line-item events cover A and B parts; no BOM-driven events, revision-tied drawings or bid templates |
| Quote breakdowns and normalization | LightSourceStrong Quote formats with flexible cost breakdowns; AI normalizes any quote; bids compared in one currency | ArkestroModerate Native: bids ranked against predicted prices with supplier error detection; no cost-breakdown structure |
| Iterative pricing and re-quotes | LightSourceStrong RFQ versions and rounds, per-supplier updates and quote history compared across rounds; Item Cost Walk | ArkestroModerate Native: targeted round-two counteroffers with live rank feedback; no revision re-quotes or cost walks |
| Marketplaces | LightSourceNot offered Not a marketplace; suppliers are invited to Sourcing projects and RFIs | ArkestroNot offered Outside scope; Arkestro runs buyer-led events and is not a parts or business marketplace |
| Indirect RFx and e-auctions | LightSourceModerate RFQs and RFIs for strategic indirect categories such as freight lanes and capex; no reverse auctions | ArkestroStrong Native: multi-round RFQ events where buyers open with predicted offers and suppliers accept or counter |
| 4 · Contract and award | ||
| Award and nomination | LightSourceStrong Award scenarios with splits, suggested and AI-optimized plans, sequenced approvals; awards create contracts | ArkestroModerate Native: award scenarios and event-level awards in case studies; no nominations or long-term agreements |
| Pricing formulas | LightSourceStrong Formula fields in quote formats price from item properties; per-period volumes and terms set at award | ArkestroNot documented Not publicly documented; events price line items against predicted offers, with no index-linked formulas |
| Third-party and internal benchmarking | LightSourceModerate Baselines from contracts, should-costs or past quotes; quote comparison across projects; bid distribution | ArkestroStrong Native: every event opens on a price predicted from quote and market data; index feeds not named |
| Contract management | LightSourceStrong Awarded contracts with price, volume, terms, expiry tracking and pricing history; authoring stays in your CLM | ArkestroIntegrates Configured: Icertis and Agiloft listed as API and webhook connectors; no native contract lifecycle tools |
| Tail-spend management | LightSourceNot offered No tail-spend desk or spot-buy channel; built for planned direct and strategic buys | ArkestroStrong Native: tail and spot buys run as predictive multi-line events at volume; no catalogs, cards or spot desk |
| 5 · Industrialize | ||
| APQP, PPAP and supplier quality | LightSourceModerate Certifications and quality documents via RFIs and data room file requests; no PPAP approval workflow | ArkestroNot offered Outside scope; sourcing ends at award, with no APQP, PPAP or corrective-action workflow |
| Tooling, prototypes and pilot builds | LightSourceModerate Tooling and ED&T costs in quotes and bid totals; tooling items record cavity count, tool life, ownership | ArkestroNot offered Outside scope; no tooling, prototype or pilot-build tracking in public materials |
| Supplier onboarding and information | LightSourceStrong Suppliers join free by invitation; RFI qualification, certificates in data rooms, ERP vendor sync | ArkestroNot documented Not publicly documented; suppliers are invited to events, with no registration, certificate or banking flow |
| 6 · Ramp and launch | ||
| Production ramp and timelines | LightSourceModerate Programs track awarded projects, open items and milestones per project; suppliers see the milestones | ArkestroNot offered Outside scope; no launch timeline, ramp curve or supplier milestone tracking |
| Alternate sourcing and tier-N visibility | LightSourceModerate Dual-source awards with supplier caps and Supplier Discovery for alternates; no tier-N supplier mapping | ArkestroNot documented Not publicly documented; award modeling is marketed as weighing risk, with no tier-N map or alternates |
| Supplier collaboration portals | LightSourceStrong Free for suppliers, onboarding in under 30 minutes: RFQs, Excel round-trip quotes, messages, data rooms | ArkestroModerate Native: suppliers accept or counter predicted offers with live rank feedback; quotes only, no POs |
| 7 · Scale and sustain | ||
| Price compliance and index adjustments | LightSourceStrong Awarded contract prices, Pricing History and Item Cost Walk set the reference price for each item | ArkestroLimited Marketed: Continuous Procurement promises always-on benchmarking; no invoice, PO or index checks |
| Engineering changes and cost-downs | LightSourceStrong Item and BOM revision diffs reach live RFQs as pending changes; Re-source, Programs and Savings projects | ArkestroNot documented Not publicly documented; no ECO intake or revision-driven re-quote workflow in public materials |
| SRM and supplier performance | LightSourceStrong Weighted Scorecards, Book Of Business per supplier, data rooms with AI document analysis, contacts | ArkestroNot documented Not publicly documented; no scorecards or performance reviews, supplier activity centers on events |
| Renewals and vendor consolidation | LightSourceNot offered Indirect renewal calendars are out of scope; direct contract expiry is tracked under Contracts | ArkestroNot documented Not publicly documented; no renewal calendar, auto-renew controls or vendor consolidation tools |
| 8 · Order and pay LightSource stops at the award on purpose. Purchase orders, receipts and invoices run in your ERP or procure-to-pay system, and LightSource writes awarded pricing and supplier records into it. | ||
| PO, release and order collaboration | LightSourceIntegrates POs and releases run in your ERP; awarded prices and terms flow there via the GraphQL API or files | ArkestroIntegrates Configured: awards sync back to SAP, Oracle or Coupa by API and webhook; no releases or ASNs |
| ERP and MRP (system of record) | LightSourceIntegrates ERP stays the transactional record; supplier master syncs both ways and awarded pricing flows into it | ArkestroIntegrates Configured: REST API and webhooks for SAP, Oracle and Coupa; offers and awards sync to the record |
| Invoice, AP automation and payments | LightSourceIntegrates Invoicing and payment stay in your ERP or AP; Awarded contracts send agreed prices and payment terms | ArkestroNot offered Outside scope; no invoicing, AP or payment touchpoint, Arkestro sits upstream of the P2P suite |
| Requisition to PO, catalogs and punchouts | LightSourceIntegrates No requisitions, catalogs or punchouts; awarded prices export to your ERP or P2P, where POs are issued | ArkestroIntegrates Configured: awards sync to Coupa, SAP Ariba or ServiceNow for the PO; no requisitions or catalogs |
| 9 · Plan and fulfill Downstream planning and logistics stay in the supply chain systems that own them; LightSource is upstream of the forecast. | ||
| Planning and logistics systems | LightSourceNot offered Planning, S&OP, TMS and WMS sit downstream of LightSource and are out of scope | ArkestroNot offered Outside scope; no demand planning, TMS or WMS features or connectors |
| Cross-cutting: analytics, risk and governance | ||
| Spend analytics and savings tracking | LightSourceModerate BOM-level spend and cost analytics, Savings projects, My Supply Chain dashboards; not a company-wide cube | ArkestroLimited Native: savings and cycle-time reporting on events; Sievo connector listed; no spend cube |
| Risk monitoring and third-party risk | LightSourceModerate AI Document Analysis flags expired certificates; supplier status and Scorecards; no external risk feeds | ArkestroIntegrates Configured: Exiger listed as an API and webhook connector; no native risk monitoring or TPRM |
| ESG, sustainability and supplier diversity | LightSourceNot offered No ESG ratings, Scope 3 or diversity data; RFIs and data rooms can collect supplier certificates | ArkestroIntegrates Configured: EcoVadis listed as an API and webhook connector; no native ESG or diversity tools |
| Master data management | LightSourceIntegrates Items and suppliers mastered against PLM and ERP by external ID; AI duplicate detection and merge | ArkestroIntegrates Configured: supplier data syncs by REST API with the ERP or suite as the record; no MDM tools |
| Tariff and HTS support | LightSourceModerate Built-in HTS code property with AI suggestions; duty and freight as cost modifiers for landed-cost bids | ArkestroNot documented Not publicly documented; tariffs appear as webinar topics, not as an HTS or landed-cost feature |
| Indirect category systems Category-specific indirect systems. LightSource runs strategic indirect categories that behave like direct, such as packaging, logistics lanes and facilities. | ||
| Services and contingent workforce | LightSourceNot offered Contingent labor, VMS and statement-of-work management are out of scope | ArkestroNot offered Outside scope; services can run as sourcing events, with no VMS or SOW management |
| SaaS and software spend | LightSourceNot offered SaaS discovery and license management are out of scope | ArkestroNot offered Outside scope; no software discovery, license or renewal management |
| T&E, cards and expense | LightSourceNot offered Travel, corporate cards and expense reporting are out of scope | ArkestroNot offered Outside scope; no travel, card or expense features |
| MRO | LightSourceNot offered MRO storeroom and CMMS-linked buying are out of scope | ArkestroLimited Native: MRO is a lead case-study category for events; no storeroom, catalog or CMMS buying |
| Strategic indirect | LightSourceStrong Freight lanes, rate cards and capex run as Sourcing projects; Ocean Freight and Capex quote templates | ArkestroModerate Native: predictive multi-round events for packaging and other indirect categories; no lane books |
| Platform and fit | ||
| AI-native architecture | LightSourceStrong AI through the cycle: item extraction, RFX Setup Agent, custom views, award optimization, thread answers | ArkestroStrong Native: ML-first since 2017 as Bid Ops; predicted offers drive every event, extended by Arkestro Labs |
| Agentic and autonomous operation | LightSourceStrong Agents draft quote formats, bid views and award plans; autonomous sourcing; BYO agents (Claude, OpenAI) by API | ArkestroModerate Native: automated counteroffers and a read/write REST API; MCP listed as coming soon on its site |
| Direct-materials focus | LightSourceStrong Built around parts: drawings, revisions, multi-level BOMs, tooling and ED&T costs, cost breakdowns | ArkestroModerate Direct spend in scope (Nissan, A and B parts cases), but parts are event line items, not managed records |
| NPI support | LightSourceStrong Revision-aware RFQs, target costs and should-costs for new parts, Engineering role, Programs for launches | ArkestroNot documented Not publicly documented; no engineering collaboration or revision workflow; new items get predicted prices |
| Implementation and time-to-value | LightSourceStrong Live in days on spreadsheet syncs, sourcing in about 30 days, implementation included; API connectors later | ArkestroModerate Results in as little as two months per Arkestro; Capgemini and BDO support enterprise rollouts |
| Mid-market accessibility | LightSourceStrong Self-serve quick start, free for suppliers; SSO, SCIM, approval chains and access groups when needed | ArkestroModerate Most G2 reviewers are mid-market and find it straightforward after training; sales motion is enterprise |
Where Arkestro is strong
Arkestro, founded in 2017 as Bid Ops and rebranded in 2022, runs multi-round competitive sourcing events in which the buyer's side moves first: the platform generates a predicted price from historical quote and market data, and suppliers accept or counter it with live ranking feedback. That mechanic is differentiated, and it is well evidenced on high-volume, history-rich categories such as MRO, packaging, and commodity parts. Arkestro's own case studies document an automotive company capturing $1.4M in recognized savings across MRO and A and B parts, and a three-round, four-supplier tape event covering 15 line items.
The commercial base is real enterprise scale. Chevron, Nissan Americas, Valvoline, Koch Industries, JLL, and GAF appear as named customers, and Nissan uses the platform across both direct and indirect spend in North America. Arkestro raised a $36M strategic investment in May 2025 led by Altira Group and Aramco Ventures, reports that customer spend through the platform tripled year over year in 2026, and says it has quoted more than 400,000 items and processed $410B in spend. Its homepage claims 18.8% average savings on all spend and a 13-day average cycle time at one materials company; treat those as vendor figures rather than audited results, though the customer list itself is public.
Arkestro also positions itself carefully, as a layer that connects to the existing suite rather than replacing it, and it has Capgemini and BDO partnerships for enterprise rollout. If the goal is compressing negotiation cycles across a broad category estate without changing systems of record, this is Arkestro's home ground.
The Hackett Group's 2026 sourcing guide describes Arkestro as a predictive procurement orchestration platform built on data, behavioral science, game theory and machine learning, and placed it on its 2025-2026 '50 to Watch' list.
Where LightSource wins for direct materials
LightSource's object model is the part itself. AI ingestion builds a revision-managed item master from Excel files, PDFs, and drawings; BOMs nest with snapshots, diffs, and cost roll-ups; RFQs go out at the part level with drawings attached. Quotes come back as structured cost breakdowns rather than totals: as of September 2026, LightSource is the only sourcing solution with true flexible cost breakdowns, meaning category-specific bid sheets per event, and AI normalizes quotes in any format into comparable data. Awards become tracked contracts with per-part, per-supplier price history that survives buyer turnover. The two pricing philosophies diverge exactly where history is thin. Arkestro's anchors are statistical, built from bid and market history, and they are strongest where that history is rich. An engineered component at new-product introduction has little or no history; its price forms from drawings, tolerances, tooling, and cost structure. LightSource treats should-cost as first-class item data, and engineering works inside the same system: item edits in active projects create revisions, and buyers re-issue the RFQ against the new revision with a full record of who quoted what on which revision. The supplier side is a network rather than a list. 100,000+ suppliers are live on LightSource, the platform is free for suppliers, onboarding takes under 30 minutes, and AI discovery searches by capability. The adoption math is also different: live in days on flat files, sourcing in about 30 days, implementation included. Customers include BRP, Canada Goose, HelloFresh, Shure, Serta Simmons Bedding, Yum! Brands, Infinite Machine, and Arxada. LightSource was named a Gartner Cool Vendor 2025 and carries venture backing co-led by Lightspeed and Bain Capital Ventures ($33M). The Hackett Group placed LightSource on its 2025-2026 '50 to Watch' list and lists it in its September 2026 Sourcing (for direct) solutions guide as AI-native and purpose-built for direct materials procurement.
The structural difference: pricing events versus managing parts
Arkestro's own materials position it as a layer over the existing suite rather than a replacement. Its integrations page lists connectors for SAP, Oracle, Coupa, SAP Ariba, Icertis, Agiloft, Zip, and ServiceNow, and every offer, counter, and award syncs back to the buyer's system of record. Record-keeping, contracts, and requester intake stay in those connected systems, and Arkestro adds a predictive pricing layer over the events that run through them. LightSource sits differently in the stack. It is the Direct Materials Operating System, the record itself: parts in from PLM or spreadsheets, awarded pricing out to the ERP, and everything about the part in between.
The claimed-versus-practice reading matters here. As of November 2026, Arkestro's Predictive Sourcing page describes AI-suggested prices on every line item, automatic counteroffers, supplier recommendations, and line-item award scenarios that weigh value, risk, and supplier diversification, and its Continuous Procurement page adds scheduled price-update events with every price versioned across SKUs and suppliers. We could not find an item master, BOM structures, revisions, drawings, spec packs, cost-breakdown quoting, or engineering collaboration anywhere in its public materials: the site, the product pages, the case-study PDFs, or the press releases. Arkestro can still run events on parts, and Nissan uses it across direct and indirect spend today. In the public record, though, parts live inside Arkestro as line items and SKUs with price history, so the durable record of what the part is, which revision was quoted, and what it should cost has to live somewhere else. For engineered direct materials, maintaining that record is most of the work.
Running both: Arkestro on category events, LightSource on engineered parts
Arkestro is a sourcing-stage neighbor, so the coexistence story is narrower here than with intake or P2P tools, but it exists and it splits cleanly by spend type. A large manufacturer can run Arkestro as the negotiation-compression layer over indirect, MRO, and commodity categories inside its Coupa or SAP Ariba estate, exactly where Arkestro's predictive anchors and case-study evidence are strongest. LightSource is where the engineered parts live: items, BOMs, revisions, drawings, cost-breakdown quotes, awards, and per-part price history from NPI through production resourcing.
Both can feed the same downstream systems. LightSource exports awarded pricing to the ERP through its GraphQL API or flat files, and Arkestro syncs offers and awards back by API and webhook, so awards made in either tool end up in the same purchasing backbone. As of November 2026, Arkestro lists native MCP connectivity for agents as coming soon, with its REST API and webhooks available today; LightSource's GraphQL API mirrors the whole app, which lets Claude, OpenAI, and other agents operate LightSource directly. Where an Arkestro event would touch engineered direct materials, the evaluation question is depth: a line-item price event or a part-lifecycle record. Place your actual spend mix against that question and the split usually follows from it.
What public reviewers say
On G2, Arkestro holds 5.0 out of 5 across 11 reviews and LightSource holds 4.9 out of 5 across roughly 11 reviews. Both review bases are small and the same order of magnitude, so read individual reviews as anecdotes rather than statistics.
The positive Arkestro theme is consistent: the product is approachable once teams are trained. A G2 reviewer (Mid-Market, 2023) wrote: "The product is straightforward to use by our internal teams. Once trained, they can use the tool without support from Procurement." The thoughtful caveats concern category fit and the supplier side. The same reviewer noted: "Arkestro works very well for a lot of spend categories; however, in some areas, such as Marketing services, we haven't yet been able to demonstrate the value of the tool." And a G2 reviewer (Mid-Market, Electrical/Electronic Manufacturing, 2021) from the platform's Bid Ops era wrote: "Bid Ops was not a perfect fit at first with the way we do things, and it took some getting used to from our suppliers." That reviewer went on to credit the Bid Ops team for responsiveness in adjusting the tool to their needs. Worth knowing: Arkestro's G2 reviews date from 2021 to 2023, so they describe earlier versions of the product. Among verified reviewers on enterprise review platforms beyond G2, sentiment on Arkestro is more mixed than its perfect G2 score, with a wider spread of middling ratings in a small pool.
On the LightSource side, a G2 reviewer (Mid-Market, VP of Supply Chain, 2024) wrote: "Having the cost and quoting information in a single location helps with rapid product launches and better visibility for our leadership group." Another G2 reviewer (Mid-Market, 2024) was candid about the supplier-side start: "The biggest challenge of LightSource is just getting the suppliers to try it. Once they try it --- they're also hooked."
When to choose what
Choose Arkestro if
You need to compress high volumes of repetitive sourcing events across indirect, MRO, and commodity categories.
Your categories have rich bid history, which is where predictive price anchoring works best.
You have an installed Coupa or SAP Ariba estate and want a pricing layer that coexists with it rather than replacing it.
You are converting single-source and spot buys into competitive multi-round events at enterprise scale.
You are in energy or heavy process industries, where Arkestro has flagship references (Chevron, Koch Industries) and strategic investors (Aramco Ventures, Altira Group).
Choose LightSource if
Your spend is engineered direct materials: parts with drawings, revisions, and tooling, organized in BOMs.
You need quotes as structured cost breakdowns you can compare line by line, not predicted totals.
You launch products, so NPI resourcing, revision-aware RFQs, and per-part price history matter more than event throughput.
You want supplier discovery beyond your incumbent list; 100,000+ suppliers are live and the platform is free for them.
You want to be live in days without a systems-integrator project, with implementation included.
RUNNING BOTH
Arkestro is a sourcing-stage neighbor, so the coexistence case is narrower than with intake or P2P tools, but it exists and it splits by spend type. Run Arkestro as the negotiation-compression layer over indirect, MRO, and commodity categories inside your Coupa or SAP Ariba estate, and run LightSource as the system where engineered parts live: items, BOMs, revisions, drawings, cost-breakdown quotes, awards, and per-part price history from NPI through production resourcing. Both can feed the same ERP: LightSource exports awarded pricing through its GraphQL API or flat files, and Arkestro syncs offers and awards back by API and webhook. Where an Arkestro event would touch engineered parts, ask the depth question: a line-item price event or a part-lifecycle record.
Frequently asked questions
What is the difference between LightSource and Arkestro?
Arkestro is a predictive procurement platform that compresses multi-round sourcing events by suggesting prices from bid history, and it runs alongside suites like Coupa and SAP Ariba. LightSource is the Direct Materials Operating System: the system of record for engineered parts, with revision-managed items, BOMs, drawings, cost-breakdown quotes, award scenarios, and per-part price history from PLM through ERP. The practical difference is the unit of work: Arkestro works on events, LightSource works on parts.
Does Arkestro handle direct materials and BOMs?
Arkestro does run events on direct spend; Nissan Americas uses it across direct and indirect categories, and its case studies include A and B parts. However, its public materials show no item master, BOM, revision, or drawing constructs; parts appear as line items inside sourcing events. Buyers who need a revision-managed record of engineered parts keep that record elsewhere.
Does LightSource offer predictive pricing like Arkestro?
No, LightSource approaches price differently. It treats should-cost and target price as first-class item data, normalizes any supplier quote into structured cost breakdowns with AI, and tracks per-part price history across revisions and suppliers. Arkestro's mechanic is a statistically predicted anchor price generated from bid and market history before suppliers bid.
Can you use LightSource and Arkestro together?
Yes, and the split is by spend type. Arkestro can compress negotiation events across indirect, MRO, and commodity categories inside an existing Coupa or SAP Ariba estate, while LightSource serves as the system of record for engineered parts: items, BOMs, revisions, drawings, cost-breakdown quotes, and awards. Awarded pricing exports from LightSource to your ERP through its GraphQL API or flat files.
How much do LightSource and Arkestro cost?
LightSource prices as a platform fee plus seats, with implementation included; exact pricing depends on scope. Arkestro does not publish pricing; Capterra's third-party listing shows a starting point of $500 per month on a per-feature model. Ask each vendor directly how pricing scales with users, events, and spend.
Which is better for NPI sourcing, LightSource or Arkestro?
New-product introduction is where the two models differ most. Predictive anchors depend on bid history, which is thin for new engineered parts, while LightSource builds price from the part itself: drawings, revisions, should-cost data, and structured cost-breakdown quotes, with engineering collaborating in the same workflow. Arkestro's public materials do not document an NPI or engineering workflow.
Sources
Arkestro: Continuous Procurement (scheduled price update events, versioned price history)
Arkestro homepage (savings and cycle-time claims, named customers, as of November 2026)
Arkestro press release: $36M strategic investment (May 2025)
TechCrunch: Arkestro Series A and Bid Ops rebrand (June 2022)
Arkestro press release: Nissan Americas collaboration (February 2026)
PR Newswire: Arkestro 2026 momentum release (400,000+ items, $410B spend)
Arkestro press release: leadership appointments and platform spend growth (August 2026)
Arkestro Use Case Booklet Vol. 2 (A and B parts, tape sourcing event)
CNBC: LightSource raises $33M co-led by Lightspeed and Bain Capital Ventures
The Hackett Group: Sourcing Solutions guide, vendor landscape (Sep 2026)
The Hackett Group: Spend Analytics Solutions guide (Sep 2026)
This comparison is based on publicly available information as of November 2026 and our understanding of both products. Products evolve; if you spot something out of date, tell us and we will fix it.
All product names and trademarks are the property of their respective owners and are used for identification only.
See your cost model in LightSource
Bring a representative bid sheet. See how an event-specific breakdown is structured, then walk through the PLM-to-ERP handoff.

