⬡
Provisioned with the application
Storage and services belong to the thing that uses them, so there is no separate account to create and no credential to copy between two dashboards.
Storage, queues and caches are rarely the hard part. Assembling five vendors into something that works, stays secure and can be explained to an auditor is the hard part. These arrive already belonging to the same system.
10 GB of object storage included, with no card required to begin.
What teams run on it
Each individual service is straightforward. The cost is in the seams: the credentials, the network rules, the billing, and the person who knows how it all fits.
Storage and services belong to the thing that uses them, so there is no separate account to create and no credential to copy between two dashboards.
Access is granted once, in one place, and removed the same way. Not five vendors with five rotation schedules and one forgotten.
Every piece on the same invoice as your compute and databases. No reconciliation exercise across providers at the end of the quarter.
What you store is reachable by your account and nothing else, enforced where the data lives rather than by a rule somebody configured.
Services, capacity and the included allowance in one view, so the question 'what have we actually got running' does not require three logins to answer.
Nobody budgets for it, everybody pays it. It is the weeks between having chosen your services and having them working together safely.
What an account can reach is decided where the data lives, not by application code remembering to filter a prefix. The common failure — one customer reading another customer's files because a path was built wrong — is not available as a mistake.
Services belong to what uses them, so deleting the application takes its storage with it.
Usage is the byte count actually stored, not an estimate that drifts from reality.
What you pay is on the pricing page, in the same units you will be billed in.
A deployment that would take you past what is included is refused with the reason in its own log — before the bytes are stored, not after.
We cancelled four vendors in a month. The saving was real, but the thing that mattered was having one place to answer a security questionnaire from.
Object storage, queues and caches, provisioned alongside the applications that use them. The free allowance covers 10 GB of object storage, with usage measured from the bytes actually written.
No. One account covers all of it, with one set of credentials and one invoice. That is the point of it being a single product rather than a bundle.
Access is scoped where the data is stored rather than by application code filtering a path. A request for something outside your account is refused at the store.
Its storage goes with it. Nothing is left behind holding data you believed you had removed.
From the byte count actually written when a deployment publishes. It is a measurement taken once, not a running total that something has to remember to adjust.
The write is refused, with the reason, before anything is stored. You are told you are at the limit rather than finding out from a bill.
Storage, queues and caches that already belong to the same system as everything else you run.
10 GB of object storage included. No card to begin.