GITNUXSOFTWARE ADVICE
Digital Products And SoftwareTop 10 Best Electronic Parts Catalogue Software of 2026
Top 10 electronic parts catalogue software ranked by inventory tracking features, with side-by-side comparisons of Octopart, Z2Data, and BOMist.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Choose Octopart as your core electronic parts catalogue when sourcing and engineering teams need API-driven part discovery with accurate cross-references, and go with Z2Data if you’re maintaining governed, living master data for replacements and compliance; if budgetReviewId is needed, DigiKey API suits low-cost line enrichment via distributor catalogs, whereas for curated symbol and footprint records SnapMagic fills the gap.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Octopart
API-based component search and attribute responses that integrate directly into BOM and procurement tooling.
Built for fits when sourcing and engineering teams need API-driven part discovery and cross-reference accuracy..
Z2Data
Editor pickLifecycle-oriented supersession relationships keep alternates and replacements consistent across updates.
Built for fits when engineering and procurement teams maintain living component master data with governed replacements..
BOMist
Editor pickAPI-driven catalog synchronization keeps manufacturer and alternate part references consistent across BOMs.
Built for fits when teams maintain shared component master data and need API-driven catalog synchronization..
Related reading
Comparison Table
Electronic parts catalogue software matters when BOMs, distributor stock, and component compliance must stay synchronized across procurement workflows. This ranked list helps analysts and operators compare tools by data model depth, API and automation options, lifecycle and risk coverage, and control features such as RBAC and audit logs, using Octopart as the key mechanism reference point for integration-first component catalogs.
Octopart
API-firstElectronic component search and supply data platform with distributor inventory and technical specifications.
API-based component search and attribute responses that integrate directly into BOM and procurement tooling.
Octopart’s core value comes from search result richness, because component pages include attributes needed for filtering and compare-ready offer summaries for common sourcing tasks. The API supports automation by returning structured identifiers and attribute fields that can feed internal catalogs, BOM tools, and review screens. This structure reduces manual mapping between manufacturer part numbers and alternates when teams standardize parts across projects.
A key tradeoff is that governance and master data ownership remain external, because Octopart provides catalog data and search access rather than a full internal component master data system. Octopart fits teams that need high-throughput parts discovery and API-based data pulls, then apply internal approvals and supersession rules in their own tools. Teams doing bulk XML or CSV catalog exchanges still need a separate pipeline to normalize units, map attributes, and enforce PLM or ERP rules.
- +API returns structured search and offer fields for automation pipelines
- +Attribute-based parametric search reduces manual component cross-checks
- +Component pages consolidate datasheets and distributor offer context
- +Cross-references connect manufacturer part numbers to alternates
- –Catalog governance and approval workflows require external systems
- –Bulk import and normalization needs an additional ETL layer
- –Advanced lifecycle rules often depend on team-specific logic
- –Deep ERP or PLM synchronization still requires integration work
Procurement analytics teams
Automate offer-aware component matching
Less manual vendor comparison
Engineering change coordinators
Validate alternates during revisions
Faster change validation
Show 2 more scenarios
BOM automation engineers
Enrich BOM rows via API
Higher BOM completeness
Query manufacturer identifiers to populate attributes and documentation links during BOM creation.
Component master data stewards
Sync external identifiers into catalogs
Fewer identifier mismatches
Use API responses as input to internal normalization, mapping, and approval processes.
Best for: Fits when sourcing and engineering teams need API-driven part discovery and cross-reference accuracy.
More related reading
Z2Data
enterpriseElectronic component intelligence platform covering parts data, supply risk, compliance, and lifecycle status.
Lifecycle-oriented supersession relationships keep alternates and replacements consistent across updates.
Z2Data fits organizations that treat component master data as an operational asset, not a static lookup, because part records are managed with lifecycle-oriented fields and relationships. Manufacturer alignment is handled through attribute and identity mapping between manufacturer part numbers and internal part numbers, which reduces duplication during catalog normalization. Technical documentation attachments support datasheets and drawings on the same part record, which improves traceability for engineering review workflows.
A key tradeoff is that deeper governance requires deliberate configuration of workflows and validation rules before catalog scale operations, because consistency depends on how mappings and alternates are maintained. Z2Data works best when a team needs ongoing catalog synchronization across tools like ERP or PLM via API-based integration, rather than only manual browsing.
- +Supersession-aware part relationships reduce BOM ambiguity during transitions
- +Manufacturer part number mapping supports controlled alternate and replacement logic
- +API-based catalog synchronization supports multi-system updates
- +Document attachments keep datasheets and drawings tied to each part
- –Governance setup requires careful workflow and validation configuration
- –Complex alternate graphs need periodic cleanup to avoid drift
- –Advanced search tuning depends on configured attributes and indexes
- –Large imports can require pre-normalization for consistent identities
Procurement operations teams
Manage approved alternates during obsolescence
Fewer wrong-part purchases
Engineering data managers
Normalize manufacturer and internal identities
Clean component master data
Show 2 more scenarios
ERP integration owners
Sync parts to downstream systems
Reduced master data lag
Uses API-based catalog synchronization to push updates into connected tooling workflows.
Mechanical and EE teams
Centralize datasheets and drawings
Fewer document hunting delays
Attaches technical documentation to part records for faster engineering review.
Best for: Fits when engineering and procurement teams maintain living component master data with governed replacements.
BOMist
SMBBOM and inventory software for organizing electronic parts, assemblies, suppliers, and production requirements.
API-driven catalog synchronization keeps manufacturer and alternate part references consistent across BOMs.
BOMist is built around electronic parts catalogue usage where component master data, manufacturer part number references, and alternate part relationships stay synchronized across bills. It supports BOM authoring with structured selection and record linking, so engineering changes can be reflected by updating shared part records instead of editing every bill manually. Datasheet attachments and technical drawing references can be stored with the part record to keep procurement and engineering context together. Integration depth is a key differentiator for teams that need catalog synchronization, because BOMist provides an API surface designed to connect external systems to the same part identifiers.
A practical tradeoff is that governance depends on how strictly the organization defines and enforces approved part references and substitution rules within the catalog. BOMist fits teams that update component content frequently, like organizations responding to obsolescence or sourcing changes where alternates must be tracked at the part level. For one-off BOM creation without shared master data discipline, the workflow overhead of maintaining part relationships can feel heavier than lighter catalog tools.
- +API-based catalog synchronization for shared part records
- +Alternate part relationships support controlled substitutions
- +Manufacturer part number and internal part mapping reduces duplicates
- +Datasheet and drawing attachments stay with each part record
- –Approved part discipline requires ongoing admin work
- –Complex substitutions need clear internal rules to avoid ambiguity
- –Bulk ingestion workflows can require up-front attribute normalization
- –Advanced CAD library alignment needs extra setup effort
Electronics engineering teams
Maintain BOMs with controlled alternates
Fewer BOM edit cycles
Procurement and sourcing teams
Map MPNs to internal identifiers
Reduced parts mismatch
Show 2 more scenarios
Operations data stewards
Standardize component master data
Cleaner master data
Attribute normalization and attachments centralize datasheet and drawing context per part record.
Change management coordinators
Track substitution impacts quickly
Faster change propagation
Part-level updates propagate through shared BOM references, limiting downstream inconsistency during changes.
Best for: Fits when teams maintain shared component master data and need API-driven catalog synchronization.
PartsBox
SMBElectronic parts inventory software with component records, stock tracking, and bill of materials support.
Supersession relationships are modeled per component record to support replacement tracing inside catalogue-driven BOM work.
PartsBox functions as an electronic parts catalogue where component master data is organized around manufacturer part numbers and internal part numbers. The system supports BOM management with an approval-oriented workflow for adding and revising parts records.
Data entry is geared toward parametric search using normalized attributes, and records can carry attachments like datasheets and drawings. Catalog data can be synchronized for downstream use through import workflows and integration surfaces designed for parts data governance.
- +Attribute-driven search that uses normalized fields for faster part discovery
- +BOM-centric workflows for turning vetted parts into build-ready lists
- +Record attachments support datasheet and drawing capture per component
- +Supersession links help trace replacements across part updates
- –Integration depth depends on configured import and mapping workflows
- –Alternate part handling can require manual curation for complex substitution rules
- –Complex lifecycle states need disciplined maintenance to prevent mismatches
- –Parametric search performance depends on field completeness across records
Best for: Fits when engineering teams maintain a shared parts library and need controlled BOM updates.
SiliconExpert
enterpriseEnterprise component intelligence software covering parts data, lifecycle status, compliance, and risk.
Built-in lifecycle and obsolescence intelligence wired directly into the part record and its cross-reference graph.
SiliconExpert aggregates manufacturer and distributor component data into an electronic parts catalogue for use in BOM and procurement workflows. It focuses on structured part records with lifecycle signals and cross-reference behavior across manufacturer part numbers and alternates.
The catalog supports deep filtering for engineering review and supports integration patterns that move component master data between systems. Strong automation and API-based synchronization are key for keeping internal part lists current at scale.
- +High coverage of part cross-references across manufacturer identifiers
- +Lifecycle and obsolescence indicators included inside part records
- +Attribute filtering supports technical review before BOM entry
- +API-based catalog synchronization supports automated master data updates
- –Attribute normalization gaps can require internal mapping rules
- –Modeling alternates and supersession can be complex to govern
- –EDA and library handoff depend on integration design
- –Search performance can drop when filtering on many optional attributes
Best for: Fits when teams need API-driven parts catalog updates tied to engineering change and sourcing workflows.
SnapMagic
vertical specialistElectronic component library platform providing symbols, footprints, models, and part information.
Record-level review states let teams gate changes to parts before they become usable in catalogue exports.
SnapMagic is an electronic parts catalogue tool built for curating component master data and keeping supplier and manufacturer references consistent. It focuses on guided ingestion of parts records, structured attributes, and attachment handling for datasheets and drawings.
Catalog users can search by common fields such as manufacturer part number and alternate identifiers, then export catalogue data for downstream bill of materials workflows. Governance support centers on review states for part records rather than deep engineering-change traceability.
- +Structured part records reduce duplicate manufacturer part number entries
- +Guided import keeps attribute normalization and required fields consistent
- +Datasheet and drawing attachments stay tied to each part
- +Search supports multiple identifiers including internal and alternates
- –API surface is not positioned for bidirectional catalogue synchronization
- –Supersession and obsolescence workflows are limited to record-level status
- –Engineering change notice linkage is not a first-class workflow
- –Role and approval controls lack fine-grained per-field review states
Best for: Fits when engineering teams need curated parts records with attachments and identifier-based search.
Aligni
SMBManufacturing inventory and product data software with parts, bills of materials, and purchasing records.
Governed publish workflows for internal part numbers, alternates, and lifecycle status tied to downstream BOM refresh cycles.
Aligni focuses on managing electronic parts catalogue content with a workflow around internal part numbers, alternates, and lifecycle status rather than treating a catalogue as a static spreadsheet. It supports attribute normalization so manufacturer part numbers and catalog attributes can be kept consistent across sources.
Aligni is also oriented toward controlled publish and update cycles for engineering and sourcing use cases that depend on bill of materials accuracy. The most practical distinction is its focus on catalogue governance for component master data and its integration-oriented approach to keeping downstream lists synchronized.
- +Attribute normalization keeps manufacturer and internal part data consistent
- +Alternate and lifecycle fields support disciplined component master data changes
- +Governed publish and update flows reduce catalogue drift across teams
- +Catalogue synchronization workflow supports repeatable BOM refresh cycles
- –Parametric search depth varies by attribute setup and taxonomy completeness
- –Supercession rules and obsolescence logic require careful configuration
- –EDA and CAD library attachment support depends on how data is mapped
- –Complex import scenarios can need manual cleanup for edge cases
Best for: Fits when engineering and procurement need governed component master data with repeatable updates.
TraceParts
vertical specialistEngineering component catalog platform offering product data and downloadable CAD content from manufacturers.
Library-grade content delivery with tightly linked CAD and technical documents for manufacturer part numbers, designed for engineering selection workflows.
TraceParts is an electronic parts catalogue built around manufacturer content distribution and parameterized product browsing for engineering teams. The catalogue experience centers on multi-format digital data like CAD and technical assets tied to manufacturer part numbers.
It supports search workflows that match real engineering usage, including filtering on attributes and using category navigation to reach the right component quickly. The value comes from integrating supplier catalog data into engineering Bill of Materials and downstream CAD libraries workflows without rebuilding the catalogue from scratch.
- +Strong CAD and document coverage aligned to published manufacturer parts
- +Attribute-driven browsing speeds up component selection and shortlists
- +Consistent manufacturer part number indexing across distributed catalog entries
- +Supports repeatable ingestion into engineering workflows for BOM creation
- –Catalog depth varies by manufacturer, so coverage can be uneven
- –Advanced workflows require catalog governance for internal numbering alignment
- –Limited visible customization of attribute schemas after import
- –Deep ERP or PLM automation depends on external integration components
Best for: Fits when teams need reliable manufacturer part content for engineering selection, CAD libraries, and BOM assembly with manageable governance.
DigiKey API
API-firstDistributor API providing DigiKey product catalog data, pricing, availability, and order integration.
API-first access to current Digikey catalog entities enables automated catalog sync without manual downloads.
DigiKey API delivers manufacturer-part and product data through an API built for catalog synchronization workflows. The core capability is programmatic access to Digikey catalog entities so engineering and procurement systems can pull up-to-date component master data and validate part availability by part number.
Querying and filtering support downstream automation in tools like ERPs and PLM systems that need bill of materials line enrichment. The API surface is documented to support consistent integration patterns for recurring inventory updates and attribute reads.
- +Programmatic manufacturer part lookups for automated BOM enrichment
- +Catalog synchronization support for keeping internal component records current
- +Structured API responses suitable for building repeatable import pipelines
- +Stable integration pattern for recurring availability and attribute pulls
- –Mapping Digikey identifiers to internal part numbers needs custom logic
- –Complex parametric navigation can require more client-side handling
- –Long-running sync jobs need throughput planning to avoid rate constraints
- –Media asset retrieval is not always aligned with CAD and EDA library needs
Best for: Fits when systems need API-based catalog synchronization and line-level enrichment from Digikey parts.
Mouser Electronics API
API-firstDistributor API providing Mouser product search, specifications, pricing, stock, and order data.
Alternate-part and related product data delivered through a queryable API response for automated substitution workflows.
Mouser Electronics API is geared toward automated ingestion of electronic parts catalogue data into internal applications rather than manual catalog browsing.
The API focuses on programmatic product retrieval with structured attributes and related sourcing information that can feed BOM and engineering workflows.
Integration effort is mainly on the receiving side, where internal part identification and alternates must be mapped to internal part records.
- +Supports API-driven catalog synchronization for component lookups
- +Provides structured attributes needed for automated part matching
- +Delivers alternates and related sourcing data
- +Reduces manual mapping work during BOM updates
- –Requires engineering work to map responses into internal part records
- –Rate limits can constrain high-throughput enrichment jobs
- –Limited visibility into supersession chains across internal part numbering
- –Datasheet attachment handling depends on downstream storage design
Best for: Fits when engineering and procurement teams automate component matching and updates from a parts catalog API.
Conclusion
After evaluating 10 digital products and software, Octopart stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right electronic parts catalogue software
This buyer's guide covers electronic parts catalogue software tools across sourcing search, component master data governance, CAD content delivery, and distributor API synchronization. It references Octopart, Z2Data, BOMist, PartsBox, SiliconExpert, SnapMagic, Aligni, TraceParts, DigiKey API, and Mouser Electronics API.
The guide explains how to evaluate integration depth and automation surfaces, how to validate lifecycle and replacement logic, and how to avoid catalog drift during BOM refresh cycles. It also maps specific tool capabilities to procurement, engineering, and governance use cases.
Electronic parts catalogue software for component master data, alternates, and build-ready BOM handoff
Electronic parts catalogue software stores component master data around manufacturer part numbers and internal part numbers, then connects alternates, supersessions, and lifecycle status to bill of materials workflows. It reduces BOM ambiguity by keeping component identifiers and attached documentation consistent across projects and systems.
Octopart illustrates a discovery-first approach that combines attribute-based search, part cross-references, and API responses that integrate into procurement and BOM tooling. Z2Data illustrates a governance-first approach that maintains living component records with supersession-aware relationships and document attachments tied to part records.
These tools are typically used by electronics engineering teams, procurement teams, and data owners who must run engineering change notices into procurement-ready component lists while managing obsolescence and replacement behavior.
Catalogue governance, API-driven synchronization, and BOM-ready replacement traceability
The right evaluation focuses on how the tool represents alternates, supersessions, and lifecycle states inside component records and how it synchronizes those records into other systems. Integration depth matters because many organizations build BOMs, CAD libraries, and procurement catalogs from separate pipelines.
Automation and API surface determine whether the catalog behaves like a managed master data system or a manual export workflow. Admin and governance controls decide whether part record updates can be validated before they impact downstream BOM refresh cycles.
API-based component discovery and structured search responses
Octopart provides an API that returns structured search and offer fields for automation pipelines, which directly supports programmatic BOM enrichment and procurement workflows. DigiKey API and Mouser Electronics API also provide API-first catalog synchronization for distributor entities, which supports line-level matching for automated updates.
Supersession-aware alternate and replacement relationships
Z2Data models lifecycle-oriented supersession relationships so alternates and replacements stay consistent across updates. PartsBox models supersession per component record to support replacement tracing inside catalogue-driven BOM work.
Governed publish and update workflows that reduce catalog drift
Aligni focuses on governed publish workflows for internal part numbers, alternates, and lifecycle status so downstream BOM refresh cycles stay aligned. SnapMagic provides record-level review states that gate changes before parts become usable in catalogue exports.
Attribute normalization that supports parametric search without duplicates
PartsBox uses attribute-driven search with normalized fields to accelerate part discovery and reduce duplicate records. Aligni adds attribute normalization for manufacturer part numbers and catalogue attributes so component master data stays consistent across sources.
Attachment handling tied to component records
SnapMagic and SiliconExpert keep datasheets and technical documents attached to part records so engineering context travels with the component identifier. BOMist and PartsBox also tie datasheet and drawing attachments to stored parts records to keep documentation available during BOM assembly and engineering change work.
Library-grade CAD and technical content delivery for manufacturer parts
TraceParts delivers tightly linked CAD and technical documents for manufacturer part numbers, which supports engineering selection workflows without rebuilding manufacturer content. It also supports repeatable ingestion into engineering workflows for BOM creation when governance for internal numbering alignment is handled.
Which teams should use electronic parts catalogue software
The right tool selection depends on whether the organization needs API-driven discovery, governed component master data, or library-grade manufacturer content. Different teams own different authoritative data, and the tooling reflects that authority.
Engineering and procurement teams typically share responsibility for part identifiers and replacement behavior, while governance owners focus on workflow control and auditability of changes inside component records.
Sourcing and engineering teams that need API-driven part discovery and cross-reference accuracy
Octopart fits when procurement and engineering need attribute-based parametric search and component pages that consolidate datasheets and distributor offer context. Its API returns structured search and offer fields that support automation pipelines for BOM and procurement tooling.
Engineering and procurement teams that maintain living component master data with governed replacements
Z2Data fits when supersession-aware part relationships and controlled alternates must stay consistent across updates. Aligni also fits when governed publish workflows tie internal part number changes and lifecycle status to repeatable downstream BOM refresh cycles.
Teams that share component records across BOMs and need API-driven catalog synchronization
BOMist fits when shared parts libraries require consistent manufacturer and alternate part references across BOMs through API-driven synchronization. BOMist also ties attachments like datasheets and drawings to part records so documentation stays consistent across BOM assembly workflows.
Engineering teams that curate reusable parts records with export gating
SnapMagic fits when record-level review states must gate changes before parts become usable in catalogue exports. It supports search by manufacturer part number and alternates while keeping datasheet and drawing attachments tied to each part record.
Engineering teams that primarily consume manufacturer CAD content for selection and BOM creation
TraceParts fits when the organization needs tightly linked CAD and technical documents for manufacturer part numbers to support engineering selection workflows. It also supports repeatable ingestion into engineering workflows for BOM creation, with coverage that varies by manufacturer.
Pitfalls that cause duplicate parts, broken supersessions, or weak synchronization
Most failure patterns come from mismatched governance ownership and missing normalization work. Another set of issues comes from expecting distributor or search APIs to solve internal replacement logic without integration and mapping.
Catalog drift usually appears when alternates and lifecycle states are edited without governed publish cycles, or when attribute completeness is insufficient for parametric search performance.
Treating alternates as free text instead of governed relationships
Z2Data and PartsBox model alternates with lifecycle or per-component supersession relationships, which supports traceable replacements. Tools like BOMist and Aligni also include alternate handling that needs disciplined internal rules, so free-text substitutions that bypass relationship modeling create ambiguity during BOM updates.
Assuming API enrichment automatically maps to internal part identities
DigiKey API and Mouser Electronics API provide structured responses, but mapping distributor identifiers to internal part numbers requires custom logic. Octopart also integrates into external workflows, so ignoring identifier mapping and normalization pipelines leads to duplicates and mismatched cross-references.
Importing large catalog libraries without pre-normalization and cleanup rules
Z2Data and BOMist can require pre-normalization for consistent identities during large imports, and Z2Data can need periodic cleanup of complex alternate graphs to avoid drift. PartsBox can require attribute normalization upfront to avoid weak parametric search results.
Relying on record edits without gating or publish workflows
SnapMagic uses record-level review states to gate changes before catalogue exports use them. Aligni uses governed publish and update flows tied to downstream BOM refresh cycles, so skipping those controls creates mismatches between component records and engineering build lists.
Overestimating CAD and EDA handoff from a parts catalogue that focuses on records only
TraceParts delivers tightly linked CAD and technical documents for manufacturer part numbers, which suits engineering selection and CAD library ingestion. SnapMagic and BOMist focus on component records and attachments, so expecting deep library-grade CAD delivery without a dedicated ingestion step can break downstream EDA and CAD workflows.
How We Selected and Ranked These Tools
We evaluated Octopart, Z2Data, BOMist, PartsBox, SiliconExpert, SnapMagic, Aligni, TraceParts, DigiKey API, and Mouser Electronics API using criteria drawn from feature coverage, ease of use, and value, with features carrying the most weight. Ease of use and value were each weighted less than features, because orchestration choices like API-driven synchronization and replacement traceability create the largest day-to-day impact.
Each tool received a composite view from named capabilities like API-based structured responses, lifecycle and supersession modeling, guided import and normalization, record review states, and CAD-linked content delivery. We then used the reported overall rating, the features rating, the ease of use rating, and the value rating as the combined numerical basis for the ranking narrative.
Octopart separated from lower-ranked tools through API-based component search with attribute responses that integrate directly into BOM and procurement tooling. That combination lifted its features score and eased adoption for automation-driven sourcing and engineering workflows.
Frequently Asked Questions About electronic parts catalogue software
How do Octopart and SiliconExpert handle attribute-based parts discovery for BOM line enrichment?
Which tools provide API-based catalog synchronization for procurement and engineering systems?
How does BOMist maintain manufacturer-to-internal part mappings while keeping alternates consistent?
What tradeoff appears when SnapMagic uses record-level review states instead of deep engineering-change traceability?
When lifecycle supersession is required, how do Z2Data and PartsBox differ in modeling replacements?
How do Aligni and TraceParts support catalogue governance without turning data entry into a spreadsheet process?
Which tools emphasize technical asset attachments like datasheets and drawings on stored part records?
How does attribute normalization affect interoperability across teams using Aligni and Z2Data?
What breaks if integration relies on browser export instead of API-based synchronization with DigiKey API or Octopart?
Where do security and admin controls typically fall short in this category, and what should teams verify with SnapMagic or PartsBox?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Digital Products And Software alternatives
See side-by-side comparisons of digital products and software tools and pick the right one for your stack.
Compare digital products and software tools→