← Back to blog

Published on

Where can I store files with an S3-compatible API and pay in Brazilian reais?

On Zenifra’s Armazém, which stores files in Brazil (region br-sp1), charges R$ 0.18 per GB per month with the first 5 GB free and accepts PIX, boleto or card, or on Amazon S3 in the São Paulo region, which has servers in the country but bills in US dollars and charges for egress. Cloudflare R2 and Backblaze B2 have the lowest price per GB and free or nearly free egress, but they bill in dollars, with 3.5% IOF on Brazilian cards, and have no region in Brazil. This guide explains what object storage is and what S3 compatibility means, details Armazém’s prices, limits and keys (available to every organization), compares six services using official prices from Nov 6, 2026 converted at the PTAX rate, works out the cost of 50 GB, 500 GB and 2 TB including egress, and shows Node.js and Python code where only the endpoint and region change.

What object storage is and what S3 compatibility means

Object storage is where an application keeps whole files, such as photos, PDFs, videos, backups and exports, instead of writing them to the server’s disk. Each file becomes an object, identified by a name (the key, such as products/blue-shirt.jpg) inside a bucket, and is uploaded and downloaded over HTTP. There is no disk to mount and no space to reserve: you pay for what you store and for the operations you run.

That solves problems a local disk cannot. When the application runs on more than one instance, all of them read the same bucket. When an instance is replaced, the files are still there. And the user’s browser can upload and download straight from the bucket with signed links, without the file passing through your server. That is why user uploads, website images and backups almost always end up in a service like this.

The Amazon S3 API became the de facto standard for object storage: PutObject, GetObject, ListObjectsV2, DeleteObject and multipart upload have the same names and formats across many vendors. Being S3-compatible means accepting those same requests, signed the same way. In practice, you use the official AWS SDK, the AWS CLI, boto3 or libraries such as django-storages and change only the endpoint, the region and the key.

Compatible does not mean identical in everything. Each vendor has its own limits on file size, number of buckets and features, and some advanced S3 features may not exist. Before migrating, check the chosen service’s documentation for the operations your application uses. The next sections do that for Armazém and compare its price with the main alternatives.

Zenifra Armazém: how it works

Armazém is Zenifra’s object storage. It stores images, videos, documents, backups and any other files your applications use, with access from the Console or from S3-compatible tools and SDKs. The endpoint is https://armazem.zenifra.com, the region is br-sp1, and each bucket has the address https://<bucket>.armazem.zenifra.com. You pay for the space used and for requests, with no minimum plan, and usage goes on the same bill as your projects.

Armazém is available to every organization, with no request or invitation. To get started, open the Armazém menu in the Console, create your organization’s Armazém and then your first bucket. Each organization has one Armazém, which is permanent: it cannot be removed, only the buckets inside it.

A bucket name is unique across the whole Armazém, has 3 to 63 characters, uses only lowercase letters, numbers and hyphens, and starts and ends with a letter or number; admin is reserved. In the Console, you upload files of up to 20 GB, create folders (up to 20 levels, with names of up to 64 characters), download, copy a 7-day link, edit metadata and delete files. Files go straight from the browser to Armazém without passing through other servers.

Everything starts private. Buckets are always private, and reading a file requires a valid signature, from an access key or from a link that expires. A file only becomes public when you choose that specific file, as the section on keys and public files explains.

  • Step 1: create the Armazém from the Armazém menu in the Console.
  • Step 2: create buckets, such as photos, documents or backups.
  • Step 3: upload files in the Console or create an access key and connect the application.

What Armazém costs in reais

The prices below come from the limits and billing documentation and the Armazém page, checked on Nov 6, 2026 and updated on Nov 20, 2026. There is no plan and no minimum: you pay only for what you use, in reais, and the organization balance, topped up by PIX or boleto, pays for Armazém along with applications, databases and AI. Transfer to the internet is free until Dec 20, 2026; from Dec 21, 2026, it costs R$ 0.80 per GB. Traffic between Armazém and applications running on Zenifra stays free.

The free allowance applies to every organization with Armazém access. The first 5 GB stored are always free (each hour, up to 5 GB-hours are not billed), and every month 50,000 writes and listings and 500,000 reads are free. The request count resets on the 1st of each month, in UTC, and only usage above the allowance is billed. The Cost this month card in the Console shows how much of the allowance has been used.

Metering is per minute. Each bucket’s size is measured every minute, and each byte is billed for the time it was stored: one GB-month equals 1 GB stored for 720 hours, so storing 1 GB for 10 hours costs 10/720 of a GB-month. Only successful requests count; rejected ones, such as those from a revoked key or from a network outside the allowed list, are not billed. Usage is calculated per hour and charged to the balance once a day.

A concrete example: a shop that stores 20 GB of photos and makes 100,000 uploads and 1 million reads in a month pays 15 GB × R$ 0.18 = R$ 2.70 for storage, 50,000 writes above the allowance = R$ 2.00 and 500,000 reads above the allowance = R$ 1.50. Total: R$ 6.20 for the month. If the photos are downloaded over the internet, from Dec 21, 2026 add R$ 0.80 per GB of egress.

ItemPriceFree allowance
StorageR$ 0.18 per GB-monthFirst 5 GB, always
Writes and listings (upload, copy, list, bucket creation)R$ 0.40 per 10,000 requests50,000 per month
Reads (download and other requests)R$ 0.30 per 100,000 requests500,000 per month
DeletesFreeNot applicable
Uploads (ingress)FreeNot applicable
Transfer to the internetFree until Dec 20, 2026, then R$ 0.80 per GBNot applicable
Traffic from applications on ZenifraFreeNot applicable

Armazém limits

Armazém has default per-organization limits, and they are the main reason to look at another option if you already have a lot of data. Each organization gets up to 10 buckets, 50 GB stored in total, 200,000 files and 10 access keys, with files of up to 20 GB each. The documentation explains that the limits protect the platform against abuse, and you can ask for more by writing to support@zenifra.com with the organization name, your Zenifra email, what you need (more buckets or more storage) and why. The request is reviewed and may be accepted or denied.

Behavior at the limit is predictable. When it reaches 50 GB, Armazém becomes read-only within 1 minute: downloads, listings and deletes keep working, and uploads and bucket creation are rejected until you delete files or get more space. A file larger than 20 GB is rejected before the upload starts. With pending payments, Armazém also becomes read-only, files that were already public stay online and storage keeps being billed.

Each access key also has a per-minute traffic limit. Above it, Armazém responds with SlowDown (HTTP 503) until the next minute, and the SDKs already retry with backoff. Reads of public files, which use no key, are limited per client address: above 50 per second, the response is HTTP 429.

ResourceLimit
Armazém1 per organization
Buckets10
Total storage50 GB
Size of each file20 GB
Files200,000
Access keys10
Networks per key20 IPv4 or IPv6 addresses, with or without CIDR
Signed link validityup to 7 days
Data uploaded per key10 GB per minute
Data downloaded per key10 GB per minute
Writes and listings per key3,000 per minute
Reads per key6,000 per minute

Scoped keys, allowed networks and public files

Applications connect to Armazém with an access key (ID and secret). The documentation recommends one key per application, named after whoever uses it, so you can revoke one without affecting the others. The secret is shown only once, at creation, and should go into an environment variable. Keys cost nothing, and a revoked key stops working immediately.

Each key has two scopes. The first is buckets: all of them or up to 10 chosen ones. The second is the access level: Read only (list and download), Read and upload (also upload files, but not delete) or Full (everything, including deleting and, with all buckets, creating and deleting buckets). Changing bucket settings, such as CORS and versioning, also requires Full. Armazém itself rejects anything outside the scope with 403 AccessDenied, and you can only give a key the access you yourself have on the same buckets.

On top of that, a key can be restricted to the application’s networks: up to 20 IPv4 or IPv6 addresses, with or without CIDR. Requests from other networks are rejected, so a leaked key does not work outside those networks. Deleting a bucket that has files requires confirmation in the Console with the authenticator app code or a 6-digit code sent by email, valid for 15 minutes; access keys and API Keys cannot delete buckets that have files.

Public files are chosen one by one. When uploading in the Console, tick the option to make the files of that upload public; after uploading, open the file and choose Make public. The file gets a fixed address, such as https://fotos-da-loja.armazem.zenifra.com/produtos/camiseta-azul.jpg, that does not expire. The bucket’s file list stays private, nobody can discover file names from the address, and uploading, changing and deleting always require a key or the Console. Public files can only be created from the Console or the Zenifra API; access keys cannot make files public. Each read of a public file counts as a read request on your Armazém.

Official prices of six S3-compatible services

The table compares each service’s list price, read on the official pages on Nov 6, 2026. For Amazon S3, we used the Standard class in the sa-east-1 region (São Paulo), from AWS’s official price list published on Nov 4, 2026; internet egress comes from the data transfer price list for the same region. The other services have no region in Brazil: Cloudflare offers location hints in North America, Europe, Asia-Pacific and Oceania; Backblaze has the US East, US West, EU Central and CA East regions; Wasabi’s list of endpoints includes no South American region; and DigitalOcean Spaces does not appear in any Brazilian region.

To compare in reais, we used the Central Bank of Brazil’s PTAX selling rate for Nov 5, 2026, R$ 5.4621, and added the 3.5% IOF charged on international card purchases (Decree No. 6,306/2007, art. 15-B, item VII, as amended by Decree No. 12,499/2025). Each dollar therefore costs R$ 5.6533 on the card bill. Your bank’s rate includes a spread and changes daily, so treat the real values as estimates; the dollar price is what counts.

Watch the rules that change the math. AWS gives 100 GB of free egress per month, aggregated across all services and regions in the account. Backblaze does not charge egress up to 3 times the average stored in the month and then charges US$ 0.01 per GB. Wasabi charges neither egress nor requests, but its free egress policy covers customers whose monthly egress does not exceed their stored volume, and the pay-as-you-go plan has a minimum charge equal to 1 TB and a 90-day minimum storage duration per file. Spaces charges a US$ 5 monthly subscription with 250 GiB of storage and 1,024 GiB of egress included.

ServiceRegion in BrazilStorageInternet egressAllowance and minimums
Zenifra ArmazémYes, br-sp1R$ 0.18/GB-monthFree until Dec 20, 2026, then R$ 0.80 per GB5 GB free; 50,000 writes and 500,000 reads free per month; no minimum
Amazon S3 Standard, sa-east-1Yes, São PauloUS$ 0.0405/GB-month (first 50 TB)US$ 0.15/GB up to 10 TB/month; 100 GB/month free per accountUS$ 0.007 per 1,000 PUT, COPY, POST or LIST; US$ 0.0056 per 10,000 GET
Cloudflare R2 StandardNoUS$ 0.015/GB-monthFree10 GB-month free; Class A US$ 4.50 and Class B US$ 0.36 per million
Backblaze B2NoUS$ 6.95/TB-monthFree up to 3× stored; then US$ 0.01/GBFirst 10 GB free; Class A, B and C transactions free
Wasabi Hot Cloud StorageNoUS$ 7.99/TB-monthNo charge if monthly egress stays within stored volumeMinimum equal to 1 TB; 90-day minimum duration
DigitalOcean SpacesNoUS$ 5/month with 250 GiB; US$ 0.02/GiB extra1,024 GiB included; US$ 0.01/GiB extraUS$ 5/month subscription

What 50 GB, 500 GB and 2 TB cost

To keep the math concrete, we used the same scenario for every service: the volume stays stored all month, and the application downloads the same amount it stores each month (50 GB, 500 GB and 2 TB of egress). We counted 1 TB as 1,000 GB and, for Spaces, which bills in GiB, treated GiB as GB. We applied each service’s free allowance, including AWS’s 100 GB of egress, which only applies if the account does not use that allowance on another service. Requests were left out because they depend heavily on usage; their prices are in the previous table.

The result is honest and worth reading carefully. If the only criterion is the lowest price per GB and the data does not need to stay in Brazil, Backblaze B2 and Cloudflare R2 are the cheapest at all three volumes, even with IOF. Wasabi is expensive at small volumes because of the 1 TB minimum. Among the services with a region in Brazil, until Dec 20, 2026, with free egress, Armazém costs less than S3 São Paulo at every volume. From Dec 21, 2026, with egress at R$ 0.80 per GB, Armazém is still cheaper in the 2 TB scenario, but S3 São Paulo becomes cheaper in the 50 GB and 500 GB scenarios, mostly because of AWS’s 100 GB of free egress per month.

There are two important caveats for Armazém. The default limit is 50 GB per organization, so the 500 GB and 2 TB scenarios depend on a request to support, which may be accepted or denied. And transfer to the internet is free until Dec 20, 2026 and costs R$ 0.80 per GB from Dec 21, 2026, so the table shows both values. Armazém prices are in reais and carry no IOF or exchange rate swings.

Service50 GB stored + 50 GB egress500 GB + 500 GB egress2 TB + 2 TB egress
Zenifra ArmazémR$ 8.10 until Dec 20, 2026; R$ 48.10 from Dec 21, 2026 (at the default limit)R$ 89.10 until Dec 20, 2026; R$ 489.10 from Dec 21, 2026 (above the default limit)R$ 359.10 until Dec 20, 2026; R$ 1,959.10 from Dec 21, 2026 (above the default limit)
Amazon S3, sa-east-1US$ 2.03 = R$ 11.45US$ 80.25 = R$ 453.68US$ 366.00 = R$ 2,069.10
Cloudflare R2US$ 0.60 = R$ 3.39US$ 7.35 = R$ 41.55US$ 29.85 = R$ 168.75
Backblaze B2US$ 0.28 = R$ 1.57US$ 3.41 = R$ 19.25US$ 13.83 = R$ 78.19
WasabiUS$ 7.99 = R$ 45.17US$ 7.99 = R$ 45.17US$ 15.98 = R$ 90.34
DigitalOcean SpacesUS$ 5.00 = R$ 28.27US$ 10.00 = R$ 56.53US$ 49.76 = R$ 281.31

How we got Armazém’s numbers: (50 − 5) × R$ 0.18 = R$ 8.10; (500 − 5) × R$ 0.18 = R$ 89.10; (2,000 − 5) × R$ 0.18 = R$ 359.10. From Dec 21, 2026, add egress at R$ 0.80 per GB: 50 × R$ 0.80 = R$ 40.00; 500 × R$ 0.80 = R$ 400.00; 2,000 × R$ 0.80 = R$ 1,600.00. On S3 São Paulo, 2 TB costs 2,000 × US$ 0.0405 = US$ 81.00 for storage plus 1,900 GB × US$ 0.15 = US$ 285.00 for egress. Values in reais use R$ 5.6533 per dollar (PTAX of Nov 5, 2026 plus 3.5% IOF).

Where Armazém wins is not only the price: files stay in Brazil, close to the applications and users, billing is in reais by PIX or boleto, and traffic between Armazém and applications running on Zenifra is free.

The code: only the endpoint and region change

The examples below are the ones in the Armazém documentation. If you already have S3 code, the only change is passing the endpoint https://armazem.zenifra.com and the region br-sp1 when creating the client; the rest of the code stays the same. Keep the key ID and secret in environment variables, never in code; on Zenifra projects, use the project’s environment variables.

In JavaScript and TypeScript, use the AWS SDK v3. PutObjectCommand sends the whole file in a single request; for large files, such as videos and backups, Upload from the @aws-sdk/lib-storage package splits the upload into parts and sends several at once. getSignedUrl creates a download link that expires, here after 1 hour (3,600 seconds).

In Python, use boto3 with bucket-based addressing (virtual-hosted), which the documentation asks for in every tool that has this option. upload_file already splits files above 8 MB into parts. In the terminal, the AWS CLI works with the same settings: aws --profile zenifra --endpoint-url https://armazem.zenifra.com --region br-sp1 s3 ls.

bash
npm install @aws-sdk/client-s3 @aws-sdk/lib-storage @aws-sdk/s3-request-presigner
typescript
import { GetObjectCommand, PutObjectCommand, S3Client } from '@aws-sdk/client-s3'
import { getSignedUrl } from '@aws-sdk/s3-request-presigner'

const client = new S3Client({
  endpoint: 'https://armazem.zenifra.com',
  region: 'br-sp1',
  credentials: { accessKeyId: process.env.ACCESS_KEY_ID!, secretAccessKey: process.env.SECRET_ACCESS_KEY! },
})

await client.send(new PutObjectCommand({ Bucket: 'fotos', Key: '2026/foto.png', Body: arquivo, ContentType: 'image/png' }))

const link = await getSignedUrl(client, new GetObjectCommand({ Bucket: 'fotos', Key: '2026/foto.png' }), { expiresIn: 3600 })
bash
pip install boto3
python
import os
import boto3
from botocore.config import Config

client = boto3.client(
    's3',
    endpoint_url='https://armazem.zenifra.com',
    region_name='br-sp1',
    aws_access_key_id=os.environ['ACCESS_KEY_ID'],
    aws_secret_access_key=os.environ['SECRET_ACCESS_KEY'],
    config=Config(s3={'addressing_style': 'virtual'}),
)

client.upload_file('backup.tar.gz', 'backups', '2026/backup.tar.gz')
link = client.generate_presigned_url('get_object', Params={'Bucket': 'backups', 'Key': '2026/backup.tar.gz'}, ExpiresIn=3600)

What to use it for: backups, user uploads, website images and logs

Backups are the simplest case. A script that runs after pg_dump uploads the file with boto3’s upload_file or with Upload from the JavaScript SDK, which split large uploads into parts, up to the 20 GB per file limit. To keep history, the documentation shows two paths: write each version under its own name, such as documentos/edital/2026-11-03T10-00-00.pdf, which works with a Read and upload key, or turn on bucket versioning, which requires a Full key. With versioning, old versions count toward billed storage until they are deleted, and versioning never goes back to disabled, only to suspended. Use a Read and upload key for the backup routine: that way, whoever steals the key cannot delete the copies.

User uploads should go straight from the browser to Armazém. The application generates an upload link valid only for that file and for a short time (900 seconds in the documentation example), and the file never passes through your server. For that, the bucket needs a CORS rule that allows the site’s domain; read the current rules and add yours, because the bucket already has a rule used by the Console. In JavaScript, create the client that signs links with requestChecksumCalculation: 'WHEN_REQUIRED'. For large files, the browser can upload in parts of at least 5 MB, up to 10,000 parts per upload, and only the interrupted part has to be sent again.

Images and videos the site shows to anyone work best as public files, with a fixed address that does not expire. Remember that each public read counts as a request on your Armazém and that above 50 reads per second from the same address the response is HTTP 429. Private documents, such as customer contracts and invoices, stay private and are delivered by signed links valid for up to 7 days.

Logs and exports work well with one file per period and a date prefix, such as logs/2026/11/06/, and paginated listing of up to 1,000 files per response. Mind the default limit of 200,000 files per organization: bundle logs into larger files (per hour or per day) instead of one file per event, and delete old ones with DeleteObjects, which removes up to 1,000 files per request. Deletes are free.

What is the cheapest file storage service for small businesses?

By list price per GB, Backblaze B2 and Cloudflare R2 are the cheapest: on Nov 6, 2026, US$ 6.95 per TB per month and US$ 0.015 per GB per month, with free egress (on B2, up to 3 times the stored volume). Both bill in dollars, with 3.5% IOF on Brazilian cards, and have no region in Brazil.

If files need to stay in Brazil and the company wants to pay in reais by PIX or boleto, Zenifra’s Armazém costs R$ 0.18 per GB per month, with 5 GB free. Transfer to the internet is free until Dec 20, 2026 and costs R$ 0.80 per GB from Dec 21, 2026: until then, Armazém is cheaper than Amazon S3 São Paulo at all three volumes calculated; after that, only at 2 TB. For a small business with up to 50 GB, that comes to at most R$ 8.10 per month for storage.

Do I need to change my code if I already use S3?

No, in most cases. The Armazém documentation says the examples work as they do on S3: just change the endpoint to https://armazem.zenifra.com, the region to br-sp1 and use the key created in the Console. If the tool has an addressing style option, use bucket-based (virtual-hosted) addressing, not path-style.

Check two things before migrating: the default limits (50 GB, 200,000 files, 10 buckets and 20 GB per file; contact support for more) and the operations your application uses. Making files public, for example, is not done with the access key, but from the Console or the Zenifra API.

Does Armazém work with applications outside Zenifra?

Yes. Any application with an access key, from an allowed network, connects through the public endpoint https://armazem.zenifra.com. That includes servers at other providers, backup scripts running in the office and tools such as the AWS CLI.

The difference is traffic. Applications running on Zenifra do not pay for traffic to Armazém, and transfer to the internet is free until Dec 20, 2026; from Dec 21, 2026, it costs R$ 0.80 per GB. If the key is restricted to certain networks, make sure the external application connects from one of them, or requests will be rejected with 403 AccessDenied.

Can I make a whole bucket public?

No. On Armazém, buckets are always private, and the file list is never public. Make public only the files that need to be seen by anyone, one by one, when uploading in the Console or later in the file details.

To make a file private again, use Make private: the public address stops working immediately, but copies already cached by browsers or other services may remain visible until they expire. Uploading a file again under the same name makes it private, so mark the upload as public again if needed.

What happens when Armazém reaches 50 GB?

Armazém becomes read-only within 1 minute. Downloads, listings and deletes keep working; uploads and bucket creation are rejected. To upload again, delete files or ask support for more space.

The request goes to support@zenifra.com, with the organization name, your Zenifra email, what you need and why. It is reviewed and may be accepted or denied. If your volume already exceeds 50 GB today, plan the migration with that answer in hand, or keep part of the files on another service until then.

Create your Armazém

We respect your privacy

We use essential cookies to run this site. Measurement and marketing cookies, such as Google Ads, are only enabled when you accept all cookies. Read our cookie policy.