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 10.0/10
Queryable database or replicated schema
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Turso Cloud exposes SQL-over-HTTP operations and a database dump endpoint. Local embedded Turso and Cloud authorization are different routes.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
Bulk delivery 10.0/10
Customer-initiated native snapshot or full scoped table export
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
GET /dump returns database SQL. Repeated SELECT statements can also traverse selected tables with stable key ranges.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
Query expressiveness 10.0/10
SQL or equivalent joins and aggregations against the operational system
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
The pipeline endpoint supports bound SQL parameters and connection batons; close connections when no longer needed.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
Access cost barrier -
-
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · 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
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Create a database bearer token with the Turso CLI and send it in Authorization. Use the database’s HTTPS host rather than a platform-management endpoint.
Turso Cloud SQL-over-HTTP reference ↗
Base URL and Authentication · Checked 2026-10-22
Downstream permission -
-
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Turso Cloud SQL-over-HTTP reference ↗
Base URL and Authentication · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 10.0/10
Customer-configurable write interfaces with validation
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Execute SQL statements through /v2/pipeline; the reference demonstrates table creation and parameter binding.
Turso Cloud SQL-over-HTTP reference ↗
Simple query and Parameter binding · Checked 2026-10-22
Custom application path 10.0/10
Customer-configurable interfaces for custom applications
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Turso Cloud SQL-over-HTTP reference ↗
Base URL and Authentication · 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
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
Limit visibility -
-
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration 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.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · 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
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Turso Cloud SQL-over-HTTP reference ↗
POST /v2/pipeline, Parameter binding and GET /dump · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Turso Cloud SQL-over-HTTP reference ↗
Base URL and Authentication · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
The SQL dump includes schema and data, but managed multi-database and vector tables can contain service-specific definitions. Independent restoration of those features remains unverified.
Turso Cloud SQL-over-HTTP reference ↗
GET /dump: multi-db schemas and vector tables · 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
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Turso Cloud SQL-over-HTTP reference ↗
Base URL and Authentication · Checked 2026-10-22
Rights to custom logic -
-
Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Turso Cloud SQL-over-HTTP reference ↗
Base URL and Authentication · 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
Create a database bearer token with the Turso CLI and send it in Authorization. Use the database’s HTTPS host rather than a platform-management endpoint.
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
GET /dump returns database SQL. Repeated SELECT statements can also traverse selected tables with stable key ranges. The pipeline endpoint supports bound SQL parameters and connection batons; close connections when no longer needed.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump | bearer token | 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
Execute SQL statements through /v2/pipeline; the reference demonstrates table creation and parameter binding.
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 the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
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 unverifiedTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration 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. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 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
The SQL dump includes schema and data, but managed multi-database and vector tables can contain service-specific definitions. Independent restoration of those features remains unverified.
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? | Queryable database or replicated schemaTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Turso Cloud exposes SQL-over-HTTP operations and a database dump endpoint. Local embedded Turso and Cloud authorization are different routes. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Customer-initiated native snapshot or full scoped table exportTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. GET /dump returns database SQL. Repeated SELECT statements can also traverse selected tables with stable key ranges. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | SQL or equivalent joins and aggregations against the operational systemTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. The pipeline endpoint supports bound SQL parameters and connection batons; close connections when no longer needed. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Create a database bearer token with the Turso CLI and send it in Authorization. Use the database’s HTTPS host rather than a platform-management endpoint. | Turso Cloud SQL-over-HTTP reference ↗Base URL and AuthenticationChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| Which external write operations are documented? | Customer-configurable write interfaces with validationTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Execute SQL statements through /v2/pipeline; the reference demonstrates table creation and parameter binding. | Turso Cloud SQL-over-HTTP reference ↗Simple query and Parameter bindingChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer-configurable interfaces for custom applicationsTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Turso Cloud SQL-over-HTTP reference ↗Base URL and AuthenticationChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| How are integration limits disclosed? | -Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Turso Cloud SQL-over-HTTP reference ↗POST /v2/pipeline, Parameter binding and GET /dumpChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Turso Cloud SQL-over-HTTP reference ↗Base URL and AuthenticationChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Turso Cloud SQL-over-HTTP reference ↗Base URL and AuthenticationChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Turso Cloud SQL-over-HTTP reference ↗Base URL and AuthenticationChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedTurso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. The SQL dump includes schema and data, but managed multi-database and vector tables can contain service-specific definitions. Independent restoration of those features remains unverified. | Turso Cloud SQL-over-HTTP reference ↗GET /dump: multi-db schemas and vector tablesChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Turso / Turso Cloud SQL-over-HTTP selected database queries, mutations and SQL dump; local embedded runtime, beta change listeners and full organization migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Turso Cloud SQL-over-HTTP reference ↗Base URL and AuthenticationChecked 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.