Markets · bedrock market · provisional
Object Storage
Shape market (the aws s3 api re-served; convergence by imitation, graded by declared degree). The Kin Score Market layer reads each provider in its market:
who it integrates with, how deep those integrations go, and where the market publishes its own structure.
Methodology.
32providers measured
24 (75.0%)declare their own
2 (6.2%)covered by others only
1 (3.1%)distribution only (sell through, not integrations)
5 (15.6%)undeclared
26declare compatibility (report only, not weighted)
0in-market workflows shown
Provisional. Provisional and unweighted: the Market layer is not part of the composite or agent readiness. Leader lists are read within a position, never as one ranking. A provider that declares nothing we can
read is shown as undeclared, with no number: we never infer integrations.
Where this market publishes its structure
- Providers' own S3 compatibility pages and operation matrices (fetched, saved under evidence/compatibility/) machine-readable
- Providers' own contracts naming the S3 API (info/tags/path descriptions) machine-readable
- Structural detection: S3 operation names and paths in providers' contracts (ours, marked) machine-readable
- Zapier, n8n, Make, Composio, Monid connector catalogs machine-readable
- AWS, Azure and Google Cloud marketplace listings (distribution, reported beside) machine-readable
- JS-rendered compatibility pages (IBM Cloud Docs, Hetzner supported-actions) not machine-readable: client-rendered; no text without a browser
- Conformance test running the AWS SDK against each endpoint not machine-readable: not built; would be the highest evidence tier
Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.
Taxonomy how this market maps onto apis.io
Derived 2026-10-23 from the 32 providers in this market we could resolve in the
catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.
| Tags | Storage 69%, Object Storage 59%, Infrastructure 31%, Kubernetes 31%, Cloud Storage 31%, Cloud 25%, S3 Compatible 22% |
|---|
| Tag groups | Storage 81%, Infrastructure 41%, LLM 34%, Kubernetes 31% |
|---|
| Industries | Developer Tools & DevOps 44%, Artificial Intelligence 28% |
|---|
| Areas | Machine Learning 12% |
|---|
| Capabilities | Information Technology Management 59%, Cybersecurity Management 38% |
|---|
share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py
Leaders by position (provisional)
Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside
position, never inside it. Unknown-builder listings are left out of position shares and counted here.
gravity 1 · other companies invest to build on it
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| Digital Ocean |
53.3 |
58 |
42 / 16 |
0 |
0 |
3 |
partner-built 72%, ipaas-bridge 5%, standard 12%, covered 2%, builds-on-platform 9% |
builds-on 4 · publishes apps on other platforms' stores
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| Supabase |
51.8 |
17 |
0 / 17 |
1 |
3 |
2 |
ipaas-bridge 12%, standard 12%, covered 6%, builds-on-platform 47%, distribution 18%, unknown 6% |
| Tigris |
51.7 |
6 |
0 / 6 |
0 |
0 |
0 |
standard 33%, builds-on-platform 67% |
| Linode |
50.1 |
13 |
0 / 13 |
0 |
4 |
0 |
standard 31%, builds-on-platform 38%, distribution 31% |
| Wasabi |
44.4 |
6 |
0 / 6 |
0 |
0 |
1 |
ipaas-bridge 17%, builds-on-platform 83% |
covered 3 · reached mainly through aggregators
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| Oracle Cloud Infrastructure |
44.6 |
10 |
0 / 10 |
0 |
1 |
1 |
ipaas-bridge 10%, standard 40%, covered 40%, distribution 10% |
| Amazon S3 |
30.5 |
10 |
0 / 10 |
0 |
0 |
5 |
ipaas-bridge 50%, covered 50% |
| Azure Blob Storage |
26.2 |
5 |
0 / 5 |
0 |
0 |
3 |
ipaas-bridge 60%, covered 40% |
standard 10 · listed by a voluntary standard's own directory
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| Rook |
58.1 |
3 |
0 / 3 |
0 |
0 |
0 |
standard 67%, builds-on-platform 33% |
| NetApp |
56.8 |
22 |
0 / 22 |
0 |
3 |
0 |
contract 9%, standard 45%, builds-on-platform 32%, distribution 14% |
| Ceph |
54.9 |
6 |
0 / 6 |
0 |
0 |
0 |
standard 50%, builds-on-platform 50% |
| CoreWeave |
53.3 |
9 |
0 / 9 |
0 |
0 |
0 |
standard 67%, covered 11%, builds-on-platform 22% |
| Pure Storage |
53.1 |
11 |
0 / 11 |
0 |
2 |
0 |
standard 55%, builds-on-platform 27%, distribution 18% |
| Gcore |
52.8 |
6 |
0 / 6 |
0 |
0 |
0 |
standard 50%, builds-on-platform 50% |
| Nebius |
52.7 |
15 |
0 / 15 |
0 |
0 |
1 |
ipaas-bridge 7%, standard 47%, covered 33%, builds-on-platform 13% |
| Exoscale |
48.4 |
5 |
0 / 5 |
0 |
1 |
0 |
standard 40%, builds-on-platform 40%, distribution 20% |
| Filebase |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
| Storj |
17.2 thin |
1 |
0 / 1 |
0 |
0 |
0 |
standard 100% |
mixed 7 · no single mode dominates
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| Hetzner |
53.7 |
3 |
0 / 3 |
0 |
0 |
0 |
contract 33%, standard 33%, builds-on-platform 33% |
| Scaleway |
52.4 |
12 |
0 / 12 |
0 |
0 |
1 |
ipaas-bridge 8%, standard 42%, covered 17%, builds-on-platform 33% |
| Fastly |
51.8 |
16 |
0 / 16 |
0 |
3 |
2 |
ipaas-bridge 12%, standard 31%, covered 6%, builds-on-platform 31%, distribution 19% |
| SAKURA internet |
51.3 |
8 |
0 / 8 |
0 |
2 |
0 |
contract 25%, standard 25%, builds-on-platform 25%, distribution 25% |
| Crusoe |
49.8 |
10 |
0 / 10 |
0 |
1 |
0 |
standard 40%, covered 20%, builds-on-platform 30%, distribution 10% |
| Backblaze |
42.4 |
6 |
0 / 6 |
0 |
3 |
0 |
contract 17%, standard 17%, builds-on-platform 17%, distribution 50% |
| MinIO |
38.0 |
9 |
0 / 9 |
1 |
4 |
0 |
standard 22%, covered 11%, builds-on-platform 11%, distribution 44%, unknown 11% |
distribution 1 · only sells through cloud marketplaces
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| NexGen Cloud |
19.2 thin |
2 |
0 / 2 |
0 |
2 |
0 |
distribution 100% |
unknown 1 · every listing has an unknown builder
| Provider | Depth | Integrations | In / out | Unknown builder | Distribution | iPaaS bridge | Mix |
|---|
| Cloudflare R2 |
2.5 thin |
1 |
0 / 1 |
1 |
0 |
0 |
unknown 100% |
undeclared 5 · declares nothing we can read: no number
Shape adoption report only — not weighted
Report only, not weighted (Kin, 2026-10-13): `compatible` edges are shape votes (the provider re-serves the anchor's contract). They are shown here and as 'declares compatibility' on a provider, and are excluded from depth, position and the own/covered declaration until they hold across four weekly snapshots.
Pattern: imitation. Shape gravity (counted by company, one edge per provider, the best
evidence kept): 37. Convergence in the cohort: 25 of
30 (83.3%) — cohort members (minus the anchor's family, mediators and rival shapes) with at least one compatible edge to the shape, read from evidence.
aws-s3 anchor Amazon Web Services · 37 adopters, 39 declared by the provider
By degree: full 3, declared-subset 12, declared-unqualified 23, interoperable-subset 1.
By evidence: own-docs 22, own-contract 16, own-blog 1.
Snapshot timeline 2 weekly snapshot(s); nothing is weighted until it holds across four
| Date | Providers | Declared by the provider | Per shape (gravity / declared) |
|---|
| 2026-10-15 | 37 | 37 |
aws-s3 37 / 37 |
| 2026-10-17 | 38 | 38 |
aws-s3 38 / 38 |