GITNUXSOFTWARE ADVICE
Communication MediaTop 10 Best Internet Search Engine Software of 2026
Ranked roundup of Internet Search Engine Software, covering Google Custom Search API, Bing Web Search API, and DuckDuckGo Instant Answer API for buyers.
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
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Google Custom Search API
Custom search engines with site and domain restrictions plus JSON search results
Built for teams embedding Google-style site search into apps and internal tools.
Bing Web Search API
Editor pickMarket and safe search parameters for region-specific, content-filtered web results
Built for developer teams adding web search to apps, dashboards, or assistants.
DuckDuckGo Instant Answer API
Editor pickInstant Answer extraction with abstracts and related topics for widget-style responses
Built for apps needing quick question answering UI without crawling result pages.
Related reading
Comparison Table
This comparison table ranks Internet search and instant-answer APIs by integration depth, including how each API maps results into a data model, schema, and query configuration. It also evaluates automation and the API surface for provisioning, extensibility, throughput, and sandbox testing. Governance controls are covered through RBAC, audit log support, and admin configuration options.
Google Custom Search API
API-firstProvides a programmable web search experience through the Custom Search JSON API for embedding search results into applications.
Custom search engines with site and domain restrictions plus JSON search results
Google Custom Search API stands out for delivering Google-ranked results through a programmable search interface. It supports custom search engines that restrict results to selected sites and domains.
The API returns structured JSON with snippets, titles, and links for direct integration into applications. It also enables query-time controls such as language and safe search filtering.
- +Google-powered ranking with consistent, high-quality web results
- +Custom search engine control using domains and site inclusion
- +JSON responses include titles, links, and snippets for easy rendering
- +Query parameters support language selection and safe search filtering
- –Result relevance depends on configured engine scope and sources
- –Advanced vertical ranking features require external enrichment logic
- –Rate limits and quotas can restrict high-volume crawling-style use
- –Pagination and result depth are bounded for many user experiences
Website engineers
Embed Google results in app search
Faster search feature delivery
Content operations teams
Constrain results to brand sources
Reduced off-brand results
Show 2 more scenarios
Customer support teams
Answer with safe, multilingual knowledge search
Improved resolution accuracy
Applies safe search and language settings to find relevant help articles and references.
Developers building internal portals
Route queries to curated knowledge indexes
Consistent portal search coverage
Creates custom search engines for department-specific collections and consumes results via JSON.
Best for: Teams embedding Google-style site search into apps and internal tools
More related reading
Bing Web Search API
API-firstDelivers Bing web search results via REST APIs for building search features with structured response data.
Market and safe search parameters for region-specific, content-filtered web results
Bing Web Search API stands out by delivering Microsoft’s Bing web search results through a programmable HTTP interface. It supports query execution, result pagination, and structured response fields such as titles, URLs, snippets, and relevance metadata.
The API can be constrained with filters like safe search and market selection to target results by region and content sensitivity. It is designed for developers who need to integrate web search behavior into applications without building a crawler and ranking pipeline.
- +Structured JSON results include URLs, titles, and snippets for fast rendering
- +Supports pagination with offset and count for large result sets
- +Market and safe-search controls improve result targeting and filtering
- +Consistent HTTP endpoints simplify integration and automated retries
- –Web search only, so it cannot replace full vertical search engines
- –Limited control over ranking signals compared to running custom retrieval
- –Answer quality depends on Bing indexing coverage for niche pages
- –Requires handling request quota and latency tradeoffs in production
Customer support engineering teams
Find current troubleshooting articles and answers
Faster resolution with cited sources
Developer teams building chatbots
Ground responses with live web pages
More accurate, up-to-date answers
Show 2 more scenarios
Market research analysts
Monitor regional news and product mentions
Better targeting by geography
Uses market selection and filters to collect region-specific results with consistent relevance metadata.
Security and compliance teams
Screen content with safe search
Lower risk of unsuitable results
Applies safe search settings to reduce exposure to sensitive material in internal research interfaces.
Best for: Developer teams adding web search to apps, dashboards, or assistants
DuckDuckGo Instant Answer API
API-accessSupports search result retrieval for developers through DuckDuckGo's Instant Answer interfaces and related endpoints.
Instant Answer extraction with abstracts and related topics for widget-style responses
DuckDuckGo Instant Answer API enriches responses with structured instant-answer payloads rather than only links and snippets, which supports faster UI rendering. The API includes machine-readable fields such as answer text and related metadata, letting apps decide what to show without additional scraping. It is a fit for building query intent previews, knowledge widgets, and lightweight assistant responses that need consistent formatting.
A tradeoff is that the API’s instant-answer content is optimized for brevity and may not cover niche questions that require full result sets. It is most useful when an application can display a compact answer plus supporting links or related topics, and can fall back to another search path when the payload is thin.
- +Returns instant abstracts for direct answer rendering
- +Provides related topics for expanding short-form responses
- +Includes source and answer URLs for traceable display
- +Designed for fast query-to-answer integration
- –Instant answers can be sparse for niche queries
- –Output focuses on summaries, not full result lists
- –Limited control over ranking and snippet selection
- –Requires handling varied response completeness
Customer support tooling teams
Auto-show answers in chat widgets
Shorter time to first reply
E-commerce site search owners
Render concise product or policy snippets
Higher search-to-click conversion
Show 2 more scenarios
Mobile app search engineers
Disambiguate queries with related topics
Fewer rephrasing loops
Uses related topic metadata to steer users toward clearer intents and queries.
Developer platform teams
Embed instant answers in internal tools
Lower custom UI parsing cost
Delivers structured answer fields that UI services can render consistently across screens.
Best for: Apps needing quick question answering UI without crawling result pages
SerpAPI
managed SERP APIFetches search engine results through a single API that returns parsed SERP data suitable for building search aggregations.
Single API normalizing Google-style results into consistent, structured JSON objects
SerpAPI differentiates with a production-focused search results API that returns structured data instead of rendered webpages. It supports many major search sources and provides consistent JSON fields for ranking, snippets, and metadata.
The tool is built for developers who need reliable parsing and enrichment of search outputs across automated workflows. It also includes mechanisms for handling pagination, filters, and query parameters in a repeatable request format.
- +Structured JSON responses for search rank, snippets, and metadata
- +Multiple search engines supported through a single API interface
- +Reliable pagination and query parameter handling for automation
- +Developer-friendly endpoints designed for programmatic data extraction
- –API-centric workflow requires engineering effort for non-developers
- –Limited control over frontend rendering since it returns data only
- –Result fields can vary by source and query type
Best for: Developer teams automating search data collection and enrichment workflows
Algolia Search
hosted searchEnables fast hosted search for website and app content using indexing pipelines and query-time relevance controls.
InstantSearch-style query suggestions with built-in typo tolerance and advanced ranking configuration
Algolia Search stands out for near-instant, typo-tolerant search powered by prebuilt indexing and relevance tuning. It provides fast retrieval via query-time ranking options and attributes-based filtering.
Developers integrate with search APIs to build autocomplete, faceted navigation, and relevance experiments across web and mobile experiences. Operational features include dashboards for index management and performance monitoring.
- +High-speed search using dedicated indexes for rapid query responses
- +Relevance controls with ranking rules and typo tolerance for better matching
- +Facet filters enable structured discovery through attributes
- +Autocomplete and search suggestions support engaging UX patterns
- –Relevance tuning can become complex with many ranking signals
- –Facet and filter modeling requires careful indexing of attributes
- –Large datasets and frequent updates can increase index management overhead
- –Schema changes often require coordinated reindexing across environments
Best for: Teams building fast, highly relevant search and autocomplete experiences
Elastic App Search
managed relevance searchProvides search and relevance tooling for applications with managed indexing, schema, and query APIs on Elasticsearch.
Relevance Tuning with boosting, synonyms, and typo tolerance
Elastic App Search stands out for its guided, application-focused search experience built on top of Elastic’s ecosystem. It provides document-based indexing, relevance tuning, and synonym handling designed for quickly improving end-user results.
Query features include typo tolerance, faceting, filtering, and relevance controls that map directly to common search UI needs. The product emphasizes developer integration through straightforward REST APIs and consistent schema management for content updates.
- +Relevance controls like boosting and value factors improve results without complex tuning
- +Facets support navigation with aggregations over indexed fields
- +Typo tolerance helps recover from misspellings in user queries
- +Curated synonym sets enable controlled query expansion
- –App Search limits deep custom scoring compared with raw Elasticsearch
- –Schema flexibility can require rethinking fields when content changes
- –Advanced ranking features may require direct Elasticsearch for complex needs
- –Large-scale custom analytics often fall outside built-in tooling
Best for: Teams building application search with fast relevance iteration and REST integrations
OpenSearch Dashboards
open source search stackPresents a web UI for search, indexing, and analytics over OpenSearch clusters used to build internal search features.
Discover and dashboard exploration powered by OpenSearch queries and aggregations
OpenSearch Dashboards provides built-in search and analytics interfaces for OpenSearch indexes with tight integration to query, visualize, and explore data. It supports interactive dashboards, ad hoc querying, and Discover-style exploration that returns results from the underlying search engine.
OpenSearch Dashboards also offers alerting, index management, and role-based access control for operating search-based applications. Its visualization stack includes dashboards, visual builders, and common chart types tailored to log, metric, and event datasets.
- +Interactive search and Discover view for fast ad hoc exploration
- +Dashboard builder with multiple visualization types and saved views
- +OpenSearch query integration keeps filtering and aggregations consistent
- +Role-based access control supports secure multi-user environments
- –Dashboards functionality depends on OpenSearch data modeling
- –Complex multi-index workflows can require careful configuration
- –Advanced visualization customization can feel limited versus custom frontends
Best for: Teams building OpenSearch-backed search and analytics interfaces
Meilisearch
self-hosted searchDelivers typo-tolerant, fast search over documents with simple setup and HTTP APIs.
Typo-tolerant search with ranking controls via custom ranking rules
Meilisearch stands out with a fast, developer-first search engine focused on typo-tolerant relevance. It provides near-instant indexing and search over structured data using a simple API.
Ranking controls include custom sortable fields, filterable attributes, and relevance tuning tools. It also supports faceting and secure deployments through hosted or self-managed options.
- +Lightning-fast search results from incremental indexing
- +Simple API for adding, updating, and searching documents
- +Built-in typo tolerance for improved query matching
- +Flexible filtering and faceting for search navigation
- –Smaller ecosystem compared to major enterprise search platforms
- –Advanced analytics require external tooling
- –Large-scale governance features may need custom engineering
- –Schema and ranking configuration demands careful upfront setup
Best for: Teams needing fast, API-driven full-text search with tunable relevance
Typesense
self-hosted searchProvides a developer-friendly, typo-tolerant search engine with real-time indexing and straightforward query endpoints.
Schema and typo-tolerant full-text search with fast faceting through REST query parameters
Typesense stands out for fast, developer-friendly full-text search built for near real-time updates. It offers simple REST APIs and a schema-first approach with typo tolerance, faceting, and sorting to support search UI needs.
Its relevance tuning and powerful filtering let applications narrow results without complex query pipelines. Typesense also integrates cleanly with common indexing workflows through bulk import and continuous synchronization patterns.
- +Schema-driven indexing keeps document fields consistent for predictable search behavior
- +Built-in typo tolerance improves matching for user-entered queries
- +Faceted filtering enables fast drill-down experiences without custom ranking logic
- –Advanced custom ranking requires careful query and schema design
- –Nested complex data can increase indexing and filter complexity
- –Large-scale multi-region deployments can add operational overhead
Best for: Teams building low-latency search with facets, filters, and relevance tuning
Apache Solr
open source search serverSearch platform for indexing and querying text and structured content using Lucene-based indexing and query syntax.
SolrCloud provides distributed search with sharding, replication, and automatic leader election
Apache Solr stands out with its search-first architecture built on Apache Lucene, enabling high-performance indexing and querying. It provides REST-based admin and indexing endpoints plus a flexible schema that supports text search, faceting, and relevance tuning.
Solr integrates with SolrCloud for distributed indexing, replication, and shard-based scaling. It is commonly used to deliver application search features like autocompletion, filtering, and analytics over structured and unstructured content.
- +Lucene-backed full-text search with strong relevance and scoring controls
- +Faceting and filtering for fast analytics-style search experiences
- +SolrCloud supports sharding, replication, and distributed indexing
- +Flexible schema and analyzers for tailored language processing
- –Schema and analyzer management requires careful operational discipline
- –Complex deployments need tuning for performance and stability
- –Custom ranking and query features often require deeper expertise
- –Distributed setups add operational overhead for SolrCloud administration
Best for: Teams building fast app search with Lucene relevance and scalable indexing
Conclusion
After evaluating 10 communication media, Google Custom Search API 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 Internet Search Engine Software
This buyer’s guide compares Google Custom Search API, Bing Web Search API, DuckDuckGo Instant Answer API, SerpAPI, Algolia Search, Elastic App Search, OpenSearch Dashboards, Meilisearch, Typesense, and Apache Solr using integration depth, data model, automation and API surface, and admin and governance controls.
It also includes a ranked roundup and a practical decision framework for teams embedding Internet search behavior into applications, building application search over their own data, or operating search and analytics on OpenSearch or Elasticsearch.
Programmatic Internet search and app search systems with query APIs and governed data access
Internet Search Engine Software includes APIs and search platforms that return search results, snippets, and metadata for embedding into apps. It solves problems like consistent search UI rendering, query-time filtering such as safe search and region selection, and structured automation outputs for pipelines.
Some tools target web search result retrieval for applications, such as Google Custom Search API and Bing Web Search API. Other tools target application search over indexed content with document schemas and relevance controls, such as Elastic App Search and Apache Solr.
Evaluation criteria mapped to integration, data modeling, automation, and governance
Teams choosing Internet search engines need more than relevance quality. They need predictable API payloads, query controls that match product requirements, and a data model that stays stable across environments.
Governance controls matter because search behavior affects user visibility, search safety, and admin operations like role-based access and auditing of access patterns. Tools that expose configuration clearly through APIs and schemas tend to reduce operational drift across deployments.
Query-time controls for safety and targeting
Google Custom Search API applies safe search filtering and language selection through query parameters, while Bing Web Search API adds safe search and market selection for region-specific results. These controls reduce custom filtering code and keep app behavior consistent across requests.
Structured response payloads for direct UI rendering
Google Custom Search API returns JSON with titles, links, and snippets for easy rendering. Bing Web Search API and SerpAPI also provide structured JSON fields such as URLs, snippets, and relevance metadata that automation and UI layers can consume without scraping.
Instant-answer payloads for widget-style experiences
DuckDuckGo Instant Answer API returns instant-answer text and related topics so apps can render concise answers without crawling result pages. This design supports fast query-to-answer widgets that still include source and answer URLs for traceable display.
Unified SERP normalization for automation workflows
SerpAPI provides a single API interface that normalizes structured search result data across multiple major search sources. It supports repeatable pagination and query parameter handling, which helps reduce brittle parsing logic in enrichment and monitoring pipelines.
Schema-first application search with faceting and typo tolerance
Algolia Search uses attributes-based filtering and relevance tuning for faceted UX, while Meilisearch provides typo tolerance with ranking rules and sortable fields. Typesense adds a schema-first approach with built-in typo tolerance plus faceting and sorting through REST query parameters.
Relevance tuning primitives for controlled search behavior
Elastic App Search exposes relevance tuning using boosting, synonyms, and typo tolerance that map directly to application search needs. Apache Solr offers Lucene-based scoring controls plus schema and analyzer flexibility for tailoring relevance at query time.
Admin and access governance for search operations
OpenSearch Dashboards includes role-based access control and operational features like alerting and index management over OpenSearch. Apache Solr’s SolrCloud adds sharding and replication with automatic leader election, which supports governed distributed operations when scaling indexing and querying.
Choose the tool by mapping your use case to API surface and governance requirements
The selection starts by deciding whether the product needs Internet web search results, instant answers, or search over indexed documents. That choice determines whether tools like Google Custom Search API and Bing Web Search API fit, or whether schema-driven platforms like Elastic App Search, Meilisearch, Typesense, Algolia Search, or Apache Solr are a better match.
Next, teams should map automation needs to the API payload and normalization strategy. Finally, admin and governance requirements such as RBAC and distributed operational controls should be checked against what OpenSearch Dashboards and SolrCloud provide.
Classify the target data source: web results, instant answers, or indexed documents
If the app needs web search behavior and configurable result scoping, Google Custom Search API and Bing Web Search API are designed for web result retrieval. If the requirement is concise answers with traceable sources for widgets, DuckDuckGo Instant Answer API fits that payload style. If the requirement is fast search over documents with facets and typo tolerance, use Algolia Search, Elastic App Search, Meilisearch, Typesense, or Apache Solr.
Confirm the API payload matches the UI and automation contract
For direct rendering, Google Custom Search API returns JSON with titles, links, and snippets, and Bing Web Search API returns structured fields like URLs, titles, and snippets. For automation that normalizes results across sources, SerpAPI provides consistent structured SERP data and pagination handling. For instant-answer UI, DuckDuckGo Instant Answer API returns answer text and related topics so the app can render without downstream scraping.
Match query-time controls to the product’s filtering requirements
When safe search, language selection, and site or domain scoping are required, Google Custom Search API supports these query-time controls through its Custom search engine configuration and parameters. For region targeting and safe search on web results, Bing Web Search API provides market and safe-search parameters. For app search experience controls, Algolia Search and Elastic App Search offer faceting and relevance tuning primitives, while Meilisearch and Typesense expose typo tolerance plus filtering and sorting through their REST query endpoints.
Evaluate your data model and schema stability requirements
Schema-first application search is a better fit when document fields must stay consistent, which aligns with Typesense’s schema-driven indexing and predictable query behavior. Meilisearch also centers on structured documents with ranking rules and filterable attributes. Apache Solr and Elastic App Search provide flexible schema and analyzers, but Solr’s schema and analyzer management requires operational discipline when fields and language processing change.
Check governance and operational controls for multi-user and scaled deployments
For RBAC and search administration visibility over dashboards and indexes, OpenSearch Dashboards provides role-based access control and ties operational features to OpenSearch queries and aggregations. For distributed search scaling with replication and shard management, Apache Solr’s SolrCloud supports sharding, replication, and automatic leader election. For distributed application search, governance often depends on how the platform exposes schema management and index update operations through its APIs and dashboards, which Elastic App Search and Algolia Search emphasize through their application-focused REST integrations and index management interfaces.
Validate throughput assumptions against the product’s access pattern
If request volume resembles crawling or high-throughput batch retrieval, Google Custom Search API has rate limits and quotas that can restrict crawling-style use. Bing Web Search API works as HTTP endpoints but still requires handling request quota and latency tradeoffs in production. For fast low-latency app search with frequent updates, Typesense supports near real-time indexing patterns, while Meilisearch emphasizes incremental indexing for near-instant results.
Audience fit by integration style and operational responsibility
Internet search engine tools segment clearly by whether they serve web result retrieval, instant-answer widgets, or application search over indexed content. Operational governance needs also vary between teams building a front-end integration and teams operating search infrastructure.
The following segments map to the stated best-for profiles across Google Custom Search API, Bing Web Search API, DuckDuckGo Instant Answer API, SerpAPI, Algolia Search, Elastic App Search, OpenSearch Dashboards, Meilisearch, Typesense, and Apache Solr.
Teams embedding Google-style site search into applications and internal tools
Google Custom Search API matches this requirement because it uses custom search engines with site and domain restrictions plus JSON responses containing titles, links, and snippets. That payload structure reduces rendering work and keeps search scoping centralized in the configured engine.
Developer teams adding web search and region-safe filtering to apps, dashboards, or assistants
Bing Web Search API fits this segment because it offers REST endpoints with pagination plus structured JSON fields. It also exposes market selection and safe search parameters that support region-specific and content-sensitive product behavior.
Apps needing compact question answering UI without crawling result pages
DuckDuckGo Instant Answer API is built for widget-style responses because it returns instant abstracts and related topics. It also includes answer and source URLs so UIs can display traceable references without building a result list renderer.
Developer teams automating search data collection and enrichment workflows
SerpAPI fits when the workflow needs normalized structured SERP data across sources rather than rendered pages. Its single API interface and repeatable pagination support automation that enriches results in pipelines.
Teams building governed application search with facets, typo tolerance, and relevance controls
Algolia Search, Elastic App Search, Meilisearch, Typesense, and Apache Solr align with this segment because each provides schema-aware or document-based search with relevance controls and filtering. OpenSearch Dashboards is a strong fit for teams operating OpenSearch-backed search and analytics with RBAC and discover-style exploration.
Pitfalls that cause integration breakage or operational drift
Common issues appear when teams mismatch payload shape to UI needs, assume full vertical search capabilities from web-only APIs, or underestimate schema and governance effort. These mistakes show up across both web result retrieval tools and document indexing search platforms.
The corrections below reference specific tools that either solve the problem directly or expose the limitation when the requirement is mis-scoped.
Assuming a web search API can replace vertical or full vertical search engines
Bing Web Search API is designed for web search only, so it cannot replace vertical search engines built for specific content types. For vertical-like behavior in application contexts, switch to document indexing tools like Elastic App Search or Apache Solr with your own schema and relevance controls.
Building heavy UI rendering or scraping logic when the API already returns structured fields
SerpAPI and Google Custom Search API return structured JSON fields such as titles, URLs, and snippets, which supports direct rendering. Avoid writing brittle parsers meant for rendered pages when JSON field contracts exist in these APIs.
Overlooking how instant-answer coverage can be sparse for niche queries
DuckDuckGo Instant Answer API focuses on brevity and instant abstracts, so some niche questions can produce sparse payloads. For cases where full result lists are required, design a fallback path that uses a structured SERP tool like SerpAPI or a web result API like Bing Web Search API.
Letting schema changes disrupt ranking and filtering behavior across environments
Meilisearch and Typesense rely on filterable attributes and schema-based indexing behavior, so changing document fields can break query filters and sorting. In Solr, schema and analyzer management also requires operational discipline when fields or language processing evolve, which can destabilize relevance and facets.
Underestimating distributed operations complexity and RBAC needs
Apache Solr’s SolrCloud supports sharding and replication with automatic leader election, but distributed setups add operational overhead for administration. OpenSearch Dashboards provides RBAC and index management features, which reduces governance risk compared with relying on a custom frontend-only approach.
How We Selected and Ranked These Tools
We evaluated Google Custom Search API, Bing Web Search API, DuckDuckGo Instant Answer API, SerpAPI, Algolia Search, Elastic App Search, OpenSearch Dashboards, Meilisearch, Typesense, and Apache Solr across features, ease of use, and value. The overall rating is a weighted average in which features carries the most weight, while ease of use and value contribute equally. This ranking reflects criteria-based scoring from the provided feature and usability details rather than hands-on lab testing or private benchmark experiments.
Google Custom Search API separated from lower-ranked web and aggregation options because it combines Google-ranked results with query-time controls and a structured JSON response that includes titles, links, and snippets. That combination lifted the features and ease-of-use factors because teams can both scope results using site and domain restrictions and integrate the payload directly into application rendering without extra normalization steps.
Frequently Asked Questions About Internet Search Engine Software
How do Google Custom Search API and Bing Web Search API differ in result control for apps?
Which API is best for embedding instant answers rather than full result lists?
What’s the most integration-friendly option for normalizing search results into consistent JSON objects?
Which tool provides the strongest schema and indexing model for application search over your own content?
How do admin controls and role-based access control work in OpenSearch Dashboards compared with API-only search services?
Which products support extensibility through query-time tuning versus offline indexing pipelines?
What data migration approach fits teams moving from one search index schema to another?
How do these tools handle automation for ingestion, reindexing, and search queries at high throughput?
Which options are most suitable for enterprise security requirements like auditability and controlled access paths?
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
Communication Media alternatives
See side-by-side comparisons of communication media tools and pick the right one for your stack.
Compare communication media tools→