OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Overall B / 7.6*/10, with 12 of 16 applicable scoring inputs verified. Missing evidence discounts the supported score (unknown answers remain unknown).
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Data access and planned exit carry the most weight. Known commercial barriers cap access; an unpublished price applies a bounded discount. Post-cancellation retrieval is a separate disclosure. Open each dimension to inspect its inputs and sources.
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 10.0/10
Queryable database or replicated schema
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Warehouse-backed sources expose SQL reads; live remote sources use their own dialect and must be queried separately. Permission grants bound accessible records.
Permute Structured query contract ↗
Read-only SQL and source selection · Checked 2026-10-12
Bulk delivery 8.8/10
Batched or iterable API requests
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Managed table records can be retrieved in pages. Pagination observes current data, not a consistent historical snapshot; tables without primary keys lack guaranteed row order.
Permute Managed database record reads ↗
Current-table pagination · Checked 2026-10-12
Query expressiveness 8.8/10
SQL against a customer-controlled database copy; freshness depends on delivery
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Warehouse-backed sources use DuckDB SQL. Live BigQuery or Postgres routes run independently; cross-source native joins and complete workspace export are not implied.
Permute Structured query contract ↗
Warehouse DuckDB and single-source remote SQL · Checked 2026-10-12
Access cost barrier -
-
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Public plans list users, connectors and AI credits, but do not establish every API, app and managed-database entitlement or mandatory additional access fee. Lowest-plan access remains unresolved.
Permute Public plan comparison ↗
Individual, Team and Enterprise plan comparison · Checked 2026-10-12
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
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Customers issue resource-scoped keys to chosen clients. Authentication does not bypass the workspace or resource grants assigned to the key.
Permute API authentication ↗
Create an API key; Permissions · Checked 2026-10-12
Downstream permission 7.5/10
Published purpose and confidentiality boundaries
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
End-customer services and third-party integrations are permitted under stated rights and use limits. Competing-product use is restricted, and upstream provider restrictions still apply.
Permute Public clickthrough Terms of Service ↗
Cover Page Use Limitations; Third-Party Integrations and End Customer Use · Checked 2026-10-12
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
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Customers author bounded actions with declared database and connector capabilities. Publication, permission and supported provider operations qualify execution; this is not arbitrary write access to every connected vendor.
Permute Business action authoring and invocation ↗
Declared action capabilities and invocation · Checked 2026-10-12
Custom application path 10.0/10
Customer-configurable interfaces for custom applications
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Customers build source locally and publish compiled static apps. Visitors use Permute authentication and resource grants; a frontend deployment does not supply independent backend execution.
Permute Customer-built app deployment ↗
Build locally; app creation and grants · Checked 2026-10-12
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Published operations and parent Data Flows can run on schedules. This establishes repeatable processing, not customer-visible CDC for the entire workspace.
Permute Operation scheduling ↗
Published operation schedules · Checked 2026-10-12
Limit visibility -
-
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
The reviewed contract describes query result limits and truncation, but does not establish a general numeric API throughput quota with recovery instructions.
Permute Structured query contract ↗
Request examples and truncation response · Checked 2026-10-12
CDC and deletion capture -
-
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Current records and version tokens do not establish an outbound log of inserts, updates and deletions or a tombstone stream. Customer-visible CDC remains unresolved.
Permute Managed database record reads ↗
Current rows and opaque version tokens · Checked 2026-10-12
Replay and gap recovery -
-
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
A recurring schedule does not establish consumer checkpoints, a retained outbound change log or recovery after missed deletion events. Those contracts remain unresolved.
Permute Operation scheduling ↗
Schedule versus retained extraction history · Checked 2026-10-12
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
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Authorized customers can download original file bytes through a short-lived signed URL. That path does not export every processed table or workspace resource.
Permute Original file download ↗
Original uploaded-file download · Checked 2026-10-12
Post-cancellation access Disclosure
Retrieval expressly prohibited at cancellation
Disclosure only; does not reduce planned-exit credit.
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
The public agreement ends the right to use the product at termination and promises deletion on request within 60 days. It does not guarantee a post-cancellation download window; signed agreements can differ.
Permute Public clickthrough Terms of Service ↗
Standard Terms 5.5 Effect of Termination · Checked 2026-10-12
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Structured table records and original uploaded files can leave while authorized. A complete restorable package for permissions, revisions, lineage, apps, connectors and all workspace artifacts is not established.
Permute Managed database record reads ↗
Managed record response and pagination limits · Checked 2026-10-12
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 7.5/10
Customer-authored native scripts or custom APIs
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.
Operation handler source and configured inputs are readable through the API. Customer-authored code still depends on Permute runtime helpers and resource bindings.
Permute Operation code and inputs ↗
Handler source and configured inputs · Checked 2026-10-12
Rights to custom logic 7.5/10
Customer-owned definitions export in a reusable format
Permute / customer-submitted operation handler source and configured input references. Platform helpers and provider-generated implementation rights are separate; independent runtime execution is not established.
Source and configuration can be retrieved in reusable text/JSON. Customer Content ownership is retained under Terms section 11; equivalent independent execution of every helper and binding is not established.
Permute Operation code and inputs ↗
Handler source, instructions and input references · Checked 2026-10-12
Permute Public clickthrough Terms of Service ↗
11 Reservation of Rights; Customer Content definition · Checked 2026-10-12
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
Customers create API keys for chosen SDK and REST clients. End-user MCP uses separate OAuth sign-in and consent, limited to selected sources and current user permissions (it accepts no API key and exposes read-only tools). Upstream vendors retain their own access rules.
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
SQL queries, paginated managed records, original-file downloads and operation-source reads are distinct paths. Warehouse-backed SQL uses DuckDB; live remote queries use the provider dialect one source at a time.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Scoped customer REST / TypeScript SDK | API key | Customer | No | Customer-supplied credentials | 2026-10-12 |
| Permissioned end-user MCP | OAuth 2.0 | Customer | No | Customer-supplied credentials | 2026-10-12 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Individual and Team have published subscription prices and connector/AI-credit allowances. The plan table does not establish all API, app or managed-database entitlements; a free or included access grade is not inferred from missing fees.
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
Customer-authored Business Actions declare the resources and connector operations they can use. Managed record transactions and provider writes have separate grants; permitted reads do not establish arbitrary writes.
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
Published operations and Data Flows can run on schedules. Current-row pagination and resource versioning are not an outbound CDC or deletion-replay contract. General API throughput and gap recovery remain unresolved.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Current records and version tokens do not establish an outbound log of inserts, updates and deletions or a tombstone stream. Customer-visible CDC remains unresolved. | Permute Managed database record reads ↗Current rows and opaque version tokensChecked 2026-10-12 |
| How can extraction recover after missed events or an interrupted consumer? | -Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. A recurring schedule does not establish consumer checkpoints, a retained outbound change log or recovery after missed deletion events. Those contracts remain unresolved. | Permute Operation scheduling ↗Schedule versus retained extraction historyChecked 2026-10-12 |
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
Original uploaded files and structured records can be retrieved while access is active. Complete workspace restore, source permissions, revision history and connector migration still need a documented recovery package. Public terms do not promise post-cancellation retrieval.
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 read native operation code and keep app source in their own repositories. Handler code references Permute helpers and resource IDs; copying it does not establish equivalent execution outside the platform.
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 schemaPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Warehouse-backed sources expose SQL reads; live remote sources use their own dialect and must be queried separately. Permission grants bound accessible records. | Permute Structured query contract ↗Read-only SQL and source selectionChecked 2026-10-12 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Managed table records can be retrieved in pages. Pagination observes current data, not a consistent historical snapshot; tables without primary keys lack guaranteed row order. | Permute Managed database record reads ↗Current-table paginationChecked 2026-10-12 |
| What queries can a customer issue outside the provider UI? | SQL against a customer-controlled database copy; freshness depends on deliveryPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Warehouse-backed sources use DuckDB SQL. Live BigQuery or Postgres routes run independently; cross-source native joins and complete workspace export are not implied. | Permute Structured query contract ↗Warehouse DuckDB and single-source remote SQLChecked 2026-10-12 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Customers issue resource-scoped keys to chosen clients. Authentication does not bypass the workspace or resource grants assigned to the key. | Permute API authentication ↗Create an API key; PermissionsChecked 2026-10-12 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Public plans list users, connectors and AI credits, but do not establish every API, app and managed-database entitlement or mandatory additional access fee. Lowest-plan access remains unresolved. | Permute Public plan comparison ↗Individual, Team and Enterprise plan comparisonChecked 2026-10-12 |
| What permission is needed for the documented downstream use? | Published purpose and confidentiality boundariesPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. End-customer services and third-party integrations are permitted under stated rights and use limits. Competing-product use is restricted, and upstream provider restrictions still apply. | Permute Public clickthrough Terms of Service ↗Cover Page Use Limitations; Third-Party Integrations and End Customer UseChecked 2026-10-12 |
| Which external write operations are documented? | Customer-configurable write interfaces with validationPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Customers author bounded actions with declared database and connector capabilities. Publication, permission and supported provider operations qualify execution; this is not arbitrary write access to every connected vendor. | Permute Business action authoring and invocation ↗Declared action capabilities and invocationChecked 2026-10-12 |
| How can customers connect an application they build or choose? | Customer-configurable interfaces for custom applicationsPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Customers build source locally and publish compiled static apps. Visitors use Permute authentication and resource grants; a frontend deployment does not supply independent backend execution. | Permute Customer-built app deployment ↗Build locally; app creation and grantsChecked 2026-10-12 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Published operations and parent Data Flows can run on schedules. This establishes repeatable processing, not customer-visible CDC for the entire workspace. | Permute Operation scheduling ↗Published operation schedulesChecked 2026-10-12 |
| How are integration limits disclosed? | -Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. The reviewed contract describes query result limits and truncation, but does not establish a general numeric API throughput quota with recovery instructions. | Permute Structured query contract ↗Request examples and truncation responseChecked 2026-10-12 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Authorized customers can download original file bytes through a short-lived signed URL. That path does not export every processed table or workspace resource. | Permute Original file download ↗Original uploaded-file downloadChecked 2026-10-12 |
| What retrieval rights are documented at cancellation? | Retrieval expressly prohibited at cancellationPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. The public agreement ends the right to use the product at termination and promises deletion on request within 60 days. It does not guarantee a post-cancellation download window; signed agreements can differ. | Permute Public clickthrough Terms of Service ↗Standard Terms 5.5 Effect of TerminationChecked 2026-10-12 |
| How can customers define their own business logic? | Customer-authored native scripts or custom APIsPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Operation handler source and configured inputs are readable through the API. Customer-authored code still depends on Permute runtime helpers and resource bindings. | Permute Operation code and inputs ↗Handler source and configured inputsChecked 2026-10-12 |
| What rights or portability are documented for custom workflow artifacts? | Customer-owned definitions export in a reusable formatPermute / customer-submitted operation handler source and configured input references. Platform helpers and provider-generated implementation rights are separate; independent runtime execution is not established. Source and configuration can be retrieved in reusable text/JSON. Customer Content ownership is retained under Terms section 11; equivalent independent execution of every helper and binding is not established. | Permute Operation code and inputs ↗Handler source, instructions and input referencesChecked 2026-10-12 Permute Public clickthrough Terms of Service ↗11 Reservation of Rights; Customer Content definitionChecked 2026-10-12 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedPermute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. Structured table records and original uploaded files can leave while authorized. A complete restorable package for permissions, revisions, lineage, apps, connectors and all workspace artifacts is not established. | Permute Managed database record reads ↗Managed record response and pagination limitsChecked 2026-10-12 |
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
- Lowest-plan entitlement and incremental charges for API, app and database access
- Outbound CDC, deletion events and durable consumer replay
- Whole-workspace recovery of history, permissions, lineage and app/database artifacts
- Independent execution of exported native code and resource bindings
- General API throughput limits and observed migration reliability
Documentation
Assessment checked 2026-10-12. Each answer retains its source and applicable route; the check date does not establish live account behavior.