- Workplace Search Guide: other versions:
- Installation
- Getting started
- Administration & management
- Content sources
- Custom connector packages
- Custom API sources
- Box
- Confluence Cloud
- Confluence Cloud connector package
- Confluence Server
- Dropbox
- GitHub
- Gmail
- Google Drive
- Jira Cloud
- Jira Server
- Network drives connector package
- OneDrive
- Outlook connector package
- Salesforce
- ServiceNow
- SharePoint Online
- SharePoint Online connector package
- SharePoint Server connector package
- Slack
- Teams connector package
- Zendesk
- Zoom connector package
- Customizing filters
- Customizing indexing
- Content extraction
- Permissions & access control
- Search experiences
- Encryption keys
- Known issues
- Troubleshooting
- Workplace Search API reference
- API Authentication Reference
- Content sources API reference
- Custom sources indexing API reference
- Custom sources Permissions API reference
- External Identities API reference
- Search API reference
- OAuth Service API reference
- Analytics event API reference
- Synonyms API reference
- Automatic query refinement settings
ℹ️ The future of internal knowledge search with Elasticedit
The internal knowledge search use case (AKA workplace search) continues to be a top priority for Elastic. We are actively developing new features and capabilities in Elasticsearch to serve this use case. For new users, we strongly recommend using our native Elasticsearch tools for your workplace search needs, rather than the standalone Workplace Search product.
We have provided a comparison table below to help you understand the differences between the standalone product and our native Elasticsearch tools. Refer to this overview to learn more about our native Elasticsearch tools for the workplace search use case.
Read our companion blog post to learn more about the past, present and future of internal knowledge search with Elastic. Check out this example app to see how you can build your own internal knowledge search experience using our native Elasticsearch tools.
Table: Workplace Search (standalone) vs. Elasticsearchedit
Use the following table to compare the standalone Workplace Search product with the native Elasticsearch tools our team are actively developing.
| Workplace Search (standalone product) | Elasticsearch tools | ||
|---|---|---|---|
Overview |
Out-of-the-box product. An opinionated solution developed as a user-friendly abstraction on top of Elasticsearch. |
Flexible toolkit that works directly with Elasticsearch. Native connectors hosted on Elastic Cloud. Self-managed connector clients are run on your infrastructure and can be customized. |
|
Product status |
Supported |
Active development |
|
Connector portfolio |
17 data sources |
20 data sources and growing |
|
Customizing connectors |
Customize one of the 7 connector packages available |
Customize any of our 20 (and growing) connectors in our public |
|
Connecting custom sources |
Write your custom connector via Custom API sources |
Build a customized connector in Python using our open code connector framework |
|
Indexing strategy |
Content saved to hidden Workplace search indexes (managed, opinionated storage) |
Content saved to Elasticsearch indexes (flexible, familiar Elastic APIs) |
|
User interface and search experience |
Built-in opinionated search interface; cannot be customized |
Build your own customizable search experience |
|
Admin tooling |
Workplace Search built-in tools |
Elasticsearch native |
|
Release cycles |
Security fixes tied with official Elastic release cycles |
Updates immediately available in |
|
Source code |
Closed source connector code |
Open code connectors available in our public |
|
Binary content extraction |
Limited content extraction |
Content extraction via Elasticsearch, with ingest pipeline integration. Extraction of large binary files supported on edge for most connector clients. |
|
Machine Learning |
Not supported |
Leverage all Elasticsearch ML capabilities |