# DigitalOcean Spaces > DigitalOcean Spaces is S3-compatible object storage with a built-in CDN, sold as a $5 monthly subscription. Agents use it through AWS S3 SDKs with a Spaces access key, and manage keys through the DigitalOcean API or MCP server. - Canonical: https://www.anchorterminal.com/tools/digitalocean-spaces - Markdown: https://www.anchorterminal.com/tools/digitalocean-spaces.md (~9,300 tokens) - Slim: https://www.anchorterminal.com/tools/digitalocean-spaces.min.md (~2,130 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/digitalocean-spaces.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade B · 63.2/100 · rank #402 of 950 · #9 in File storage & sharing · not agent-ready · confidence medium** More from DigitalOcean, LLC, listed separately because each is its own product: [DigitalOcean MCP Server](https://www.anchorterminal.com/tools/digitalocean-mcp.md) (Cloud & infrastructure). ## Assessment Per-bucket access keys with read or read-write-delete grants, an 800 operations a second limit per bucket and a 99.9 per cent SLA are all published. The MCP server manages keys and CDN endpoints only, not objects, and the S3 reference documents no error codes. A payment method is required before any bucket is created. ## Facts | Field | Value | | --- | --- | | Vendor | DigitalOcean, LLC (https://www.digitalocean.com) | | Kind | HTTP API | | Category | File storage & sharing (https://www.anchorterminal.com/categories/file-storage) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://nyc3.digitaloceanspaces.com` | | Auth | API key · Self-serve Spaces access key and secret, signed as for AWS S3 (SigV4, or SigV2 for older clients). A person signs up in a browser and adds a payment method first. Keys are full access or limited to named buckets with Read or Read/Write/Delete, and are made in the control panel or through `/v2/spaces/keys` with a scoped DigitalOcean API token. The remote MCP server takes OAuth with a browser sign-in, or a bearer API token. | | Pricing | Pay per use ($5 / mo) · $5 a month for 250 GiB of storage and 1,024 GiB of outbound transfer across all buckets, then $0.02 a GiB-month and $0.01 a GiB. No request charges are listed. The CDN is included. Cold Storage is $0.007 a GiB-month plus $0.01 a GiB retrieved. A $5 sign-up credit lasts 90 days and needs a payment method, so there is no start without a card (https://docs.digitalocean.com/products/spaces/details/pricing/; https://docs.digitalocean.com/platform/billing/signup-credit/). | | x402 | No · No x402, MPP or L402 in the Spaces docs, the API reference index or the pricing pages. A Stablecoin Payment Addendum of 25 November 2025 covers account payments through Stripe, not per-request payment (checked 2026-10-09). | | Licence | Proprietary service under the DigitalOcean Terms of Service Agreement. The MCP server is MIT | | Packages | npm: `@digitalocean/mcp` | | Docs | https://docs.digitalocean.com/products/spaces/ | | llms.txt | https://docs.digitalocean.com/llms.txt | | Last release | 2026-04-08 | | APIs | S3-compatible XML API on `.digitaloceanspaces.com` (a subset of AWS S3, SigV4 recommended, SigV2 accepted). The DigitalOcean API v2 at `api.digitalocean.com` for access keys and CDN endpoints | | Endpoints | `https://.digitaloceanspaces.com` path-style or `https://..digitaloceanspaces.com`. CDN at `..cdn.digitaloceanspaces.com`. Static sites at `.-static.digitaloceanspaces.com` | | Regions | 13 for Standard Storage (NYC3, AMS3, SFO2, SFO3, SGP1, LON1, FRA1, TOR1, BLR1, SYD1, ATL1, RIC1, MKC1). Cold Storage in all of them except BLR1 | | Credentials | Access key and secret, up to 200 an account. Full access, or limited to named buckets with Read or Read/Write/Delete. The secret is shown once and can be regenerated. Limited keys cannot be combined with bucket policies | | MCP server | Remote at `https://spaces.mcp.digitalocean.com/mcp`, OAuth or `Authorization: Bearer` with an API token. Ten tools at v1.2.0, `spaces-key-*` and `spaces-cdn-*`, none for objects. Also runs locally as `npx @digitalocean/mcp --services spaces`. MIT licence | | Rate limits | 800 operations a second per new bucket, with `LIST` limited further under load. Cold Storage 450 write, 250 read and 25 list requests a second per bucket. The DigitalOcean API allows 5,000 requests an hour and 250 a minute per token, with `retry-after` on 429 | | Object limits | `PUT` up to 5 GB, multipart to 5 TB in 10,000 parts of at least 5 MiB. 100 buckets an account. 100 million unversioned or 50 million versioned objects a bucket. Incomplete multipart uploads are deleted after 30 days | | Presigned URLs | SigV2 and SigV4. The control panel makes links valid for 1 hour, 6 hours, 1 day, 3 days or 7 days. Uploads through the CDN with a presigned URL are capped at 8,100 KiB | | Minimums | $5 a month while any bucket exists, prorated hourly. 4 KiB per object on Standard. On Cold Storage 128 KiB per object and per read, and 30 days of storage | | Sign-up credit | $5, expiring 90 days after sign-up. A valid payment method must be added before any resource is created | | Deletion controls | Bucket versioning (API only), lifecycle expiry by time, and a one-week pending period in which a destroyed bucket can be recovered. No Object Lock found in the reviewed documentation | | Logging | Bucket access logs in Amazon S3 server access log format and CDN logs in CloudFront format, off by default, set through `PutBucketLogging` or Terraform, usually written within one hour | | SLA | 99.9 per cent monthly uptime per bucket. Credit of 10 per cent from 99.0 to 99.9, 25 per cent from 95.0 to 99.0 and 100 per cent below 95.0. Claims need written notice within 24 hours of the start of downtime | | Certifications | SOC 2 and SOC 3 reports and Global PRP named on the trust page. DigitalOcean states eligibility for HIPAA and DORA workloads. ISO 27001 was not named on the page read | | Sub-processors | More than 30 with activity and location in the list of 10 June 2026, Cloudflare (CDN), Wasabi (Cold Storage), Amazon Web Services and Stripe among them. The DPA of 6 February 2026 allows 30 days to object to a new one | | Capabilities | storage.object, storage.s3, storage.presigned, storage.share | | Tags | hosted, closed-source, s3-compatible, cdn, mcp, oauth, llms-txt, openapi, usage-priced, status-page, sla, soc-2 | | JSON | https://www.anchorterminal.com/api/v1/tools/digitalocean-spaces.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 77 | 15.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 63 | 10.2 | | Agent ergonomics | 13% | 16.2 | 73 | 11.9 | | Security & auth | 14% | 17.5 | 77 | 13.5 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 37 | 3.2 | | Transparency & trust (editorial 63, provenance 85) | 7% | 8.8 | 74 | 6.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63.2 → B** | ### Why each score - Reliability 77: Graded as a hosted API on the S3 surface. Status page at status.digitalocean.com with a readable history feed (20). The feed reaches back to 24 July 2026, 77 days. It shows failed write operations across services, Spaces among them, for 2 hours 26 minutes on 6 August, a 63-minute network disruption in BLR1 on 3 October that included Spaces, control panel access to Spaces failing for about two hours on 21 August and a Cold Storage billing display fault on 4 August. We read the 6 August event as one major incident (10). Limits published with numbers, 800 operations a second per new bucket and 5,000 requests an hour on the DigitalOcean API (15). Exponential backoff advised on `503 Slow Down`, and `retry-after` on the DigitalOcean API's 429. No retry or idempotency guidance for S3 writes (12). The Spaces SLA commits to 99.9 per cent monthly uptime per bucket (10). The S3 API and remote MCP servers are generally available (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 63: The DigitalOcean API has a public OpenAPI file, which covers access keys and CDN endpoints. The S3 surface has no description file. Its reference lists each supported operation with headers and the minimum permission level, and defers to AWS for the rest (15). `llms.txt` and a Markdown twin of every page (10). The S3 reference gives one line per operation with a link to AWS, and the MCP tool descriptions are a few words each, such as 'Delete a CDN' (10). Header tables per operation, enumerated grants on the keys API, and MCP tools with required fields, a maximum and output schemas (10). A request and response example for most operations, but no error codes in the S3 reference beyond `NotImplemented` for unsupported calls (8). Dated Spaces release notes and a versioned DigitalOcean API. The limits page and the compatibility page disagree on `ListObjectsV2` (10). - Agent ergonomics 73: Graded as an API, with the MCP server noted. Responses are sized by S3's own controls, `Range` and `HEAD` among the listed headers, and the Spaces MCP endpoint carries only ten compact tools (20). S3 listing with prefix and marker, and `per_page` up to 200 on the DigitalOcean API. The limits page lists `list-objects-v2` pagination as a known issue (14). `503 Slow Down` and `NotImplemented` are the only S3 errors described. The DigitalOcean API documents its error bodies (10). A `PUT` by key can be repeated, conditional copy headers are listed, and all ten MCP tools set read-only, idempotent or destructive hints with a risk class (16). AWS SDK examples in several languages and official DigitalOcean SDKs for TypeScript, Go and Python. Most AWS SDKs need `us-east-1` as a placeholder region to create a bucket (13). - Security & auth 77: Access keys are revocable, can be regenerated and can be limited to named buckets with Read or Read/Write/Delete. DigitalOcean API tokens take custom scopes, and the MCP server issues short-lived OAuth tokens. Three off because SigV2 is still accepted and a limited key cannot coexist with a bucket policy (27). Read-only keys, versioning and a one-week recovery period for destroyed buckets. No Object Lock or confirmation step in the API was found (14). Returns stored bytes, with no guidance on treating them as untrusted. The key creation tool's description warns about handling the secret (8). Bucket and CDN access logs in S3 format, off by default, and an account security history that the docs say can show the wrong IP address for deletes (11). security.txt valid to 2028 with an Intigriti programme as contact, and SOC 2 and SOC 3 reports named on the trust page. ISO 27001 was not named on the page read (17). - Payments & pricing 20: No x402, MPP or L402. Stablecoin payment through Stripe is an account payment method (0). Prices per GiB are public without a login (20). The $5 sign-up credit needs a valid payment method before any resource is created (0). A person signs up in a browser. The keys API needs a token from that account (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 37: Closed service. Its own release notes stop at 8 April 2026, 184 days before the check, which scores 0. The MCP server that carries the Spaces tools was tagged v1.2.0 on 7 October 2026 and its Spaces tools changed on 22 September, but that server cannot read or write objects, so it does not count as a release of the service graded here. No Spaces release notes in the last 90 days. The MCP server had seven tags in that time (10). Public release notes with an RSS feed, support tickets and a public repository with 193 commits in 90 days. Issue response times were not checked (10). Current official SDKs in three languages. The only MCP registry entry found for DigitalOcean is a third party's (10). The MCP repository has CI and release workflows and tests that guard tool annotations (7). - Transparency & trust 74: Closed service under a Terms of Service Agreement updated on 22 August 2026 that leaves ownership of content with the customer. The MCP server is MIT (15). The DPA of 6 February 2026 gives deletion within 30 days of account deactivation and breach notice without undue delay. The privacy policy excludes customer content, and the terms give no retention period in days (22). No general deprecation policy. The terms promise notice of changes as far as reasonably practicable, and old rate limits are dated per data centre (8). A sub-processor list of 10 June 2026 with activity and location, Cloudflare for the CDN and Wasabi for Cold Storage among them, and 13 named storage regions (18). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/digitalocean-spaces.md (JSON https://www.anchorterminal.com/fixes/digitalocean-spaces.json) ### What we couldn't check - unchecked: the DigitalOcean OpenAPI file itself. Its address is listed in `llms.txt`, and we read the rendered Spaces Keys reference instead - unchecked: the certification reports page and the Intigriti programme page, so whether a paid bounty exists and which SOC 2 type applies were not confirmed - unchecked: status history before 24 July 2026. The feed holds 25 entries, which covers 77 of the 90 days - unchecked: issue response times on the MCP repository, which a clone does not show, and npm download figures - Legal, trust and SLA pages on www.digitalocean.com were read through a summarising reader, so clause wording should be confirmed before quoting - Whether Cold Storage has a separate 99.5 per cent SLA, as the product details page says. The Spaces SLA page gives 99.9 per cent without naming tiers - Whether `ListObjectsV2` pagination works. The limits page and the compatibility page disagree - `lastRelease` is the MCP server tag of 7 October 2026. The Spaces release notes last changed on 8 April 2026 - The lead said Spaces is usable through remote MCP servers and the CLI. The MCP tools cover keys and CDN endpoints only, and the docs say `doctl` cannot manage files - The Acceptable Use Policy bars scraping of service content and testing without written consent. Read as a fact with no deduction. It matters before any probe is run - One typed address, https://www.digitalocean.com/legal/service-level-agreement, returned 404. The SLA was then found through the Service Terms ### Sources - docs index (llms.txt): (seen 2026-10-09) - Spaces overview and latest updates: (seen 2026-10-09) - Spaces pricing: (seen 2026-10-09) - Spaces limits and known issues: (seen 2026-10-09) - Spaces feature list: (seen 2026-10-09) - Spaces availability: (seen 2026-10-09) - Spaces S3 API reference: (seen 2026-10-09) - S3 compatibility: (seen 2026-10-09) - AWS SDK guide: (seen 2026-10-09) - access keys guide: (seen 2026-10-09) - file permissions and presigned URLs: (seen 2026-10-09) - access logs: (seen 2026-10-09) - Spaces release notes: (seen 2026-10-09) - Spaces Keys API reference: (seen 2026-10-09) - DigitalOcean API introduction (rate limits, pagination): (seen 2026-10-09) - remote MCP configuration: (seen 2026-10-09) - Spaces MCP tools: (seen 2026-10-09) - SDK and client libraries: (seen 2026-10-09) - sign-up credit: (seen 2026-10-09) - MCP server source at v1.2.0 (shallow clone, read not run): (seen 2026-10-09) - pricing page: (seen 2026-10-09) - Spaces SLA: (seen 2026-10-09) - Terms of Service Agreement: (seen 2026-10-09) - Service Terms: (seen 2026-10-09) - Acceptable Use Policy: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - Data Processing Agreement: (seen 2026-10-09) - Stablecoin Payment Addendum: (seen 2026-10-09) - sub-processor list: (seen 2026-10-09) - trust page: (seen 2026-10-09) - security.txt: (seen 2026-10-09) - status history feed: (seen 2026-10-09) - MCP registry search: (seen 2026-10-09) - RDAP for digitalocean.com: (seen 2026-10-09) ## Who's behind it (provenance 85/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | DigitalOcean, LLC | 20/20 | | Domain age | digitalocean.com, registered 2000-04-12 (26 years) | 15/15 | | Endpoint on the vendor's domain | nyc3.digitaloceanspaces.com is not on digitalocean.com | 0/15 | | Terms of service | read, states 7 of the 7 things a reader expects | 10/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.digitalocean.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The Terms of Service Agreement, last updated 22 August 2026, names DigitalOcean, LLC, 105 Edgeview Drive, Ste. 425, Broomfield, CO 80021. The privacy policy, last updated 1 January 2025, says it does not apply to content customers process in the services. The Data Processing Agreement of 6 February 2026 at https://www.digitalocean.com/legal/data-processing-agreement covers that content. Storage endpoints are on digitaloceanspaces.com. The DigitalOcean API and the MCP server are on digitalocean.com. security.txt at https://www.digitalocean.com/.well-known/security.txt gives an Intigriti programme and security@digitalocean.com as contacts and Expires 2028-04-05. RDAP for digitalocean.com gives a registration date of 2000-04-12. status.digitalocean.com disallows /api/ and /embed/ in robots.txt. We read /history.rss, which holds 25 entries from 24 July to 5 October 2026. The Acceptable Use Policy of 20 March 2026 forbids harvesting or scraping content of the services and probing or testing DigitalOcean systems without written consent. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.digitalocean.com/legal/terms-of-service-agreement), read 2026-10-09, dated 2026-08-22, states 7 of the 7 things a reader expects. - To know. Says access can be ended without notice or for any reason. "While we prefer to give advance notice of termination, we reserve the right, in our sole discretion, to terminate your access to all or any part of the Websites and/or Services at any time, with or without notice, effective immediately." - To know. Requires arbitration or waives class actions. "One requirement of our TOS is that you must agree to resolve disputes arising under this TOS through binding arbitration directly between you and DigitalOcean." - Gives the date it was last updated. Last updated 2026-08-22. - Names the governing law or courts. The law of the State of Delaware. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Says it gives notice of a change. - Also in the text (2026-10-08). Liability is capped at the amount paid for the services at issue in the month before the event behind the claim. "our aggregate liability to you for all claims arising out of or relating to this TOS or the Websites and Services, whether in contract, tort, or otherwise, is limited to the amount you have paid to us for the Services at issue in the month prior to the event or circumstance giving rise to the claim." - Also in the text (2026-10-08). The customer grants DigitalOcean permission to use its name, logos and trademarks in promotional and marketing materials. "2.3 You grant us permission to include your name, logos, and trademarks in our promotional and marketing materials and communications." - Also in the text (2026-10-08). Termination may lead to the immediate forfeiture and destruction of the data associated with the account. "Any such termination may result in the immediate forfeiture and destruction of data associated with your Account." **Privacy policy** (https://www.digitalocean.com/legal/privacy-policy), read 2026-10-09, dated 2025-01-01, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "These advertising partners may set and access their own cookies, pixel tags, and similar technologies on our Services, and they may otherwise collect or have access to information about you which they may collect over time and across different online services." - Gives the date it was last updated. Last updated 2025-01-01. - Says how long data is kept. Names a period of 90 days. - Gives a privacy contact. privacy@digitalocean.com. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). The policy does not cover information or content that customers process when using the services. "This Privacy Policy (the “Privacy Policy”) does not apply to information or content our customers may process when using our Services." - Also in the text (2026-10-08). Public activity on an account may stay stored and publicly accessible after the account is terminated. "If you terminate your Account, any public activity on your Account prior to deletion may remain stored on our servers and may remain accessible to the public." ## Live (updated 2026-10-10 01:37 UTC) - Right now: up, HTTP 200, 257 ms, checked 2026-10-10 01:37 UTC (get on `https://nyc3.digitaloceanspaces.com`) - Uptime 24h 100.0% (102 probes) · 30 days 100.0% (102 probes) · p50 252 ms · p95 318 ms - Vendor status page: none, All Systems Operational - npm `@digitalocean/mcp` 1.3.0 - Watching changelog - Watching pricing - Always current: https://www.anchorterminal.com/api/v1/live/digitalocean-spaces.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Spaces subscription | $5 | per month (plan) | Includes 250 GiB of storage and 1,024 GiB of outbound transfer across all buckets | | Standard storage beyond 250 GiB | $0.02 | per GB per month | Per GiB | | Cold Storage | $0.007 | per GB per month | Per GiB, 30-day minimum, plus $0.01 a GiB retrieved | | Outbound transfer beyond 1,024 GiB | $0.01 | per GB of traffic | Per GiB. Inbound transfer is free | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Spaces access keys can be limited to named buckets with read or read-write-delete grants, and are created through `/v2/spaces/keys` or the control panel - Limits are published with numbers, 800 operations a second per new bucket, with exponential backoff advised on `503 Slow Down` - The Spaces SLA of 2 December 2025 gives 99.9 per cent monthly uptime per bucket, with credits of 10, 25 and 100 per cent - Every docs page has a Markdown twin, indexed in `llms.txt`, and the S3 reference lists each supported operation with its minimum permission level - All ten Spaces tools in the MCP server (MIT licence) carry read-only, idempotent or destructive hints and a risk class, checked by tests ## Weaknesses - The Spaces MCP server has ten tools for access keys and CDN endpoints. None reads, writes, lists or shares an object - The access guide and the limits page say keys cannot be created through the API, while the API reference documents `POST /v2/spaces/keys` - The limits page lists `list-objects-v2` pagination as unsupported, and the compatibility page says to use `ListObjectsV2` for new applications - No error codes are documented in the S3 reference. Unsupported calls return `NotImplemented`, and no Object Lock was found - The $5 sign-up credit needs a payment method first, and a subscription costs $5 a month once the first bucket exists - The Acceptable Use Policy of 20 March 2026 bars scraping of service content and any probing or testing without written consent, which matters before any probe is run ## Before you call it (notes for agents) 1. Set the endpoint to `https://.digitaloceanspaces.com` and, in AWS SDKs other than Python's, set `region` to `us-east-1` when creating a bucket 2. Ask for a limited access key with a Read or Read/Write/Delete grant on one bucket. A full access key can create, configure and delete every bucket 3. Do the object work through the S3 API. The MCP server and `doctl` cannot upload, list, move or delete files 4. Retry with exponential backoff on `503 Slow Down`, and keep below 800 operations a second per bucket 5. Fetch presigned links from the origin host, not the CDN. The docs say presigned requests through the CDN are not cached and can double the bandwidth charge 6. Avoid many tiny objects. Each bills as at least 4 KiB on Standard and 128 KiB on Cold Storage, which also has a 30-day minimum ## Connect First request: ```bash import boto3 session = boto3.session.Session() client = session.client('s3', region_name='nyc3', endpoint_url='https://nyc3.digitaloceanspaces.com', aws_access_key_id='YOUR_SPACES_KEY', aws_secret_access_key='YOUR_SPACES_SECRET') client.upload_file('localfile.txt', 'my-bucket', 'uploaded.txt') ``` MCP client configuration: ```json { "mcpServers": { "spaces": { "url": "https://spaces.mcp.digitalocean.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/digitalocean-spaces. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Amazon S3 | BB | 77.9 | 16 | storage.object, storage.s3, storage.presigned, storage.share | no | https://www.anchorterminal.com/tools/amazon-s3.md | | Cloudflare R2 | BB | 77.1 | 23 | storage.object, storage.s3, storage.presigned, storage.share | no | https://www.anchorterminal.com/tools/cloudflare-r2.md | | Backblaze B2 | BB | 75.3 | 49 | storage.object, storage.s3, storage.presigned, storage.share | no | https://www.anchorterminal.com/tools/backblaze-b2.md | | Tigris | E | 44.4 | 876 | storage.object, storage.s3, storage.presigned, storage.share | no | https://www.anchorterminal.com/tools/tigris.md | | Azure Blob Storage | BB | 75.7 | 41 | storage.object, storage.presigned, storage.share | no | https://www.anchorterminal.com/tools/azure-blob-storage.md | | Wasabi Hot Cloud Storage | C | 61.2 | 478 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/wasabi-hot-cloud-storage.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - A Spaces subscription is $5.00 a month with 250 GiB of storage and 1,024 GiB of outbound transfer across all buckets, then $0.02 a GiB-month and $0.01 a GiB (source: ) - Cold Storage is $0.007 a GiB-month and $0.01 a GiB retrieved, with a 30-day minimum and objects under 128 KiB billed as 128 KiB. It has been generally available since 2 December 2025 (source: , ) - New buckets allow 800 operations a second in total. Buckets made before regional upgrades of 2020 to 2022 keep lower limits. Cold Storage buckets allow 450 write, 250 read and 25 list requests a second (source: ) - Spaces runs on Ceph and implements a subset of the S3 API, with SigV4 and SigV2 signing, multipart uploads to 5 TB, versioning, lifecycle expiry, bucket policies, SSE-C and presigned URLs (source: ) - Only the `private` and `public-read` canned ACLs exist, bucket and object tags used for lifecycle are not supported, and cross-region `CopyObject` fails (source: , ) - The DigitalOcean API manages access keys at `/v2/spaces/keys` with the token scope `spaces_key:read` and its siblings, and grants of `read`, `readwrite` or `fullaccess` per bucket (source: ) - A remote MCP server for Spaces answers at `https://spaces.mcp.digitalocean.com/mcp` with OAuth or a bearer token. Its source at v1.2.0 defines five key tools and five CDN tools (source: , ) - The access guide and limits page state that keys cannot be created, edited or deleted through the API or CLI, which the Spaces Keys API reference and the MCP tools contradict (source: ) - The status feed records failed write operations across services, Spaces among them, from 06:42 to 09:08 UTC on 6 August 2026, and a network disruption in BLR1 from 11:59 to 13:02 UTC on 3 October 2026 (source: ) - The Spaces SLA, last updated 2 December 2025, commits to 99.9 per cent monthly uptime per bucket, measured in 5-minute intervals, with credits of 10, 25 and 100 per cent (source: ) - The docs `llms.txt` carries a block of instructions addressed to AI assistants on which DigitalOcean tools to recommend. We recorded it and did not act on it (source: ) - The sub-processor list of 10 June 2026 names Cloudflare for CDN services and Wasabi for Cold Storage, each with a location (source: ) - #10 of 14 in Best file storage and sharing APIs for AI agents: https://www.anchorterminal.com/best/file-storage/index.md - All 75 storage comparisons: https://www.anchorterminal.com/compare/file-storage/index.md ## Compare - [Box API + MCP vs DigitalOcean Spaces](https://www.anchorterminal.com/compare/box-api-vs-digitalocean-spaces.md): B 69.4 vs B 63.2 - [DigitalOcean Spaces vs Dropbox API + MCP](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-dropbox-api.md): B 63.2 vs B 68.2 - [DigitalOcean Spaces vs Fastio](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-fast-io.md): B 63.2 vs C 55.2 - [DigitalOcean Spaces vs Google Drive API + MCP](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-google-drive-api.md): B 63.2 vs A 79.6 - [DigitalOcean Spaces vs OneDrive and SharePoint files (Microsoft Graph)](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-onedrive-sharepoint.md): B 63.2 vs B 65.3 - [Amazon S3 vs DigitalOcean Spaces](https://www.anchorterminal.com/compare/amazon-s3-vs-digitalocean-spaces.md): BB 77.9 vs B 63.2 - [Azure Blob Storage vs DigitalOcean Spaces](https://www.anchorterminal.com/compare/azure-blob-storage-vs-digitalocean-spaces.md): BB 75.7 vs B 63.2 - [Backblaze B2 vs DigitalOcean Spaces](https://www.anchorterminal.com/compare/backblaze-b2-vs-digitalocean-spaces.md): BB 75.3 vs B 63.2 - [Bunny Storage vs DigitalOcean Spaces](https://www.anchorterminal.com/compare/bunny-storage-vs-digitalocean-spaces.md): C 58.3 vs B 63.2 - [Cloudflare R2 vs DigitalOcean Spaces](https://www.anchorterminal.com/compare/cloudflare-r2-vs-digitalocean-spaces.md): BB 77.1 vs B 63.2 - [DigitalOcean Spaces vs Tigris](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-tigris.md): B 63.2 vs E 44.4 - [DigitalOcean Spaces vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-wasabi-hot-cloud-storage.md): B 63.2 vs C 61.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on digitalocean.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "digitalocean-spaces", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html DigitalOcean Spaces on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![DigitalOcean Spaces on Anchor Terminal](https://www.anchorterminal.com/badges/digitalocean-spaces.svg)](https://www.anchorterminal.com/tools/digitalocean-spaces) ``` Plain link: ```html DigitalOcean Spaces on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say DigitalOcean Spaces is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/digitalocean-spaces-dark.png - Light: https://www.anchorterminal.com/assets/share/digitalocean-spaces-light.png