OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Elasticsearch returns selected-index documents and search metadata. Default search limits do not establish complete index extraction.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Use a point-in-time context with search_after and a stable sort for deep traversal; keep the PIT alive and close it after extraction.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
The search API supports Query DSL filters, projections and sorting. The default from/size route is limited to 10,000 hits.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Elasticsearch search operation ↗
Search Query DSL and _source selection · Checked 2026-10-22
Access cost barrier -
-
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Elasticsearch API keys carry role descriptors and expiration. The key creator’s effective permissions bound delegated access.
Elasticsearch API keys ↗
Role descriptors, expiration and delegated privileges · Checked 2026-10-22
Downstream permission -
-
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Elasticsearch API keys ↗
Role descriptors, expiration and delegated privileges · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Index a document by ID using the documented index operation and the required index privilege.
Elasticsearch index document operation ↗
Index API and required privileges · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Elasticsearch API keys ↗
Role descriptors, expiration and delegated privileges · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Repeat a scoped index extraction using PIT and search_after. This review does not establish a customer-visible deletion feed or durable replay.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Limit visibility -
-
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Elasticsearch API keys ↗
Role descriptors, expiration and delegated privileges · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Search results retain selected _source documents and IDs. Mappings, analyzers, security configuration and pipelines require separate extraction.
Elasticsearch deep pagination ↗
search_after, point in time and 10,000-hit boundary · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Elasticsearch API keys ↗
Role descriptors, expiration and delegated privileges · Checked 2026-10-22
Rights to custom logic -
-
Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Elasticsearch API keys ↗
Role descriptors, expiration and delegated privileges · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Elasticsearch API keys carry role descriptors and expiration. The key creator’s effective permissions bound delegated access.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Use a point-in-time context with search_after and a stable sort for deep traversal; keep the PIT alive and close it after extraction. The search API supports Query DSL filters, projections and sorting. The default from/size route is limited to 10,000 hits.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| selected-index search, PIT/search_after traversal and document indexing | API key | Customer | No | Customer-supplied credentials | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Index a document by ID using the documented index operation and the required index privilege.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat a scoped index extraction using PIT and search_after. This review does not establish a customer-visible deletion feed or durable replay.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Search results retain selected _source documents and IDs. Mappings, analyzers, security configuration and pipelines require separate extraction.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Elasticsearch returns selected-index documents and search metadata. Default search limits do not establish complete index extraction. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Use a point-in-time context with search_after and a stable sort for deep traversal; keep the PIT alive and close it after extraction. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. The search API supports Query DSL filters, projections and sorting. The default from/size route is limited to 10,000 hits. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 Elasticsearch search operation ↗Search Query DSL and _source selectionChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Elasticsearch API keys carry role descriptors and expiration. The key creator’s effective permissions bound delegated access. | Elasticsearch API keys ↗Role descriptors, expiration and delegated privilegesChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Index a document by ID using the documented index operation and the required index privilege. | Elasticsearch index document operation ↗Index API and required privilegesChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Elasticsearch API keys ↗Role descriptors, expiration and delegated privilegesChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Repeat a scoped index extraction using PIT and search_after. This review does not establish a customer-visible deletion feed or durable replay. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| How are integration limits disclosed? | -Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Elasticsearch API keys ↗Role descriptors, expiration and delegated privilegesChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Elasticsearch API keys ↗Role descriptors, expiration and delegated privilegesChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Elasticsearch API keys ↗Role descriptors, expiration and delegated privilegesChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedElasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Search results retain selected _source documents and IDs. Mappings, analyzers, security configuration and pipelines require separate extraction. | Elasticsearch deep pagination ↗search_after, point in time and 10,000-hit boundaryChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Elasticsearch / selected-index search, PIT/search_after traversal and document indexing; snapshots, ingest pipelines and whole-deployment restore are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Elasticsearch API keys ↗Role descriptors, expiration and delegated privilegesChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.