Object storage

Every account is born with one.

It exists the moment you sign up, and it is the account's default: a file saved without naming a destination lands somewhere real. It answers the same calls as S3, so what you write against it runs unchanged against your own bucket.

1 per accountCreated at sign-up
S3-shapedlist · head · upload · delete
200 creditsPer GB, per month, beyond the plan
What you get

A bucket that is already
there, and already the default.

Not a service to switch on. It is created with the account, it is where a destination-less save goes, and everything else on the platform writes into it rather than into a quota of its own.

There before you ask

Every account is created with its own object storage, on every plan including the free one. That is also why a second is refused: the one your plan carries is the one you already have.

The same calls as S3

List, head, upload, read, download and delete, with deeper keys grouped into prefixes exactly as ListObjectsV2 does with a slash. Code written against this storage runs unchanged against a connected R2 or S3 bucket.

Bytes go straight in

The browser uploads to a signed address that expires after fifteen minutes, rather than through a second hop. A write is made beside the file and renamed into place, so a reader never sees a half-written object.

The agent reads it, and asks before writing

Listing and reading are free and never ask. A write is asked even in Auto mode. Documents you upload can be searched by meaning, and that search refuses rather than answering on a fallback vector.

One number

Mail, hosting and files
share the same space.

What your mailboxes receive, what a host keeps online, the photos on your contacts and the files you save are all counted here. One number for everything IaGenify keeps of your account, instead of four quotas that run out separately and at different times. When it fills, a write is refused rather than silently dropped, and an arriving message is deferred for the sender to retry rather than lost.

Storage usageLIVE
01
Your filesSaved by you, the agent or a workflow
02
Mail attachmentsEverything your mailboxes receive
03
What a host servesThe files currently online
Included

One storage,
and room that grows.

Every plan carries exactly one, already created. Beyond the space it includes, room is bought by the gigabyte and paid monthly in credits; a purchase made mid-period is prorated over the days left.

FreeGoStarter
Object storages111
Included space100 MB1 GB2 GB
Default destinationYesYesYes
Mail attachmentsCounted hereCounted hereCounted here
What a host servesNo hostingCounted hereCounted here
Extra space200 Cr / GB / month200 Cr / GB / month200 Cr / GB / month
Extra space is bought by the gigabyte, up to 100 GB, on a 30-day period.See full pricing
Questions

Object storage, in detail.

Do I have to create it?

No. It exists from the moment the account does, and it is already the default destination. That is also why a second one is refused rather than created: every plan carries one, and yours is it.

What counts against the space?

Everything we keep for you as objects: the files you save, what your mailboxes receive, what a host serves, the photos on your contacts. One number rather than four that run out separately.

Can I use my own bucket instead?

Yes. Connect an R2 or S3 bucket and the agent, the workflows and the SDK reach it through the same actions. The credentials are encrypted at rest and never leave the server - the agent sees prefixes and objects, not your keys.

What happens when it is full?

A write is refused rather than silently dropped, and an incoming message is deferred so the sender retries instead of losing it. Buy space by the gigabyte, or delete what you no longer need.