CATEGORIES / DEVELOPER TOOLS

Developer tools software: how much control do you have?

Compare development records, application permissions and change delivery.

2 category vendor reviewsPermute reference includedProvider documentation, not live tenant tests

Where the reviewed products stand

Compare documented control across the named products and routes. Open a review for its plan, region and agreement (this is a selected sample).

Developer tools: customer control map

0–10 on both axes · Higher and further right means more documented control

Data access and portability on the horizontal axis; build and act on the vertical axis. Exact scores and review links follow in the table. Dashed lines mark 5, not a grade threshold.BUILD WITH LIMITSMORE CUSTOMER CONTROLMORE DEPENDENCEPORTABLE, LESS EXTENSIBLE00551010Data access & portability →Build & act →GitHub*: 7.6 / 5.6GIGitLab*: 7.6 / 5.6GTPermute*: 8.0 / 7.1P
Exact scores & review links (3)
Vendor positions
VendorData access & portabilityBuild & act
GitHub ↗7.6*5.6*
GitLab ↗7.6*5.6*
Permute ↗Publisher self-assessment8.0*7.1*

Axes average three dimensions each: access, third-party access and exit horizontally; action, continuity and business logic vertically. Fixed 0–10 scale, midlines at 5 (overall grades use separate weights). * Some evidence is unresolved. Marker colors identify companies, not score bands. How to read the map ↗

Permute is included as a reference (it owns this site and is a publisher self-assessment). Its score is excluded from sample averages. Read the Permute review ↗

Repository files and hosted issue metadata require separate extraction paths. A code mirror alone does not establish recovery of every hosted record.

Compare the six dimensions

Comparing 2 of 3 vendors
Overall control
Data access
Third-party accessibility
External action
Continuity
Data exit
Business logic and customization
Product scopes, dates & reviews

GitHub

Developer tools · Checked 2026-10-16

GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.

Read findings and sources ↗

GitLab

Developer tools · Checked 2026-10-16

GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.

Read findings and sources ↗
Customer controlGitHub ↗GitLab ↗Permute ↗
CategoryDeveloper toolsDeveloper toolsDatabases and data platforms
Overall control
Data access
Third-party accessibility
External action
Continuity
Data exit
Business logic and customization
Assessment scopeGitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.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.
Assessment checked2026-10-162026-10-162026-10-12
Read the findingsDetailed review ↗Detailed review ↗Detailed review ↗

Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗

Who can connect?

Credentials and approval by connection method

Yes No- Unknown

A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.

What each review covers

GitHub ↗

GitHub supports repository-scoped apps and structured issue APIs. Webhook redelivery helps repair recent failures, but repository mirroring does not preserve the complete hosted collaboration state.

GitHub.com / customer-installed GitHub App, repository issues and issue webhooks; Git repository backups are disclosed separately and do not establish issue-archive completeness.

Read the findings and sources ↗

GitLab ↗

GitLab supports issue APIs and project exports with explicit omissions. GitLab.com limits differ from self-managed controls, and issue/work-item event coverage must match the current API version.

GitLab.com / user-authorized OAuth, project issue REST operations, work-item webhooks and project file exports; self-managed instance policies and complete repository/platform migration are separate.

Read the findings and sources ↗

Permute ↗

Scoped APIs expose SQL reads, managed records and customer-authored operation code. Customer-built apps are supported, while complete workspace recovery, outbound CDC and minimum-plan access terms remain unresolved.

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.

Read the findings and sources ↗

Browse all categories ↗