Core capability — storage

Every file, already connected.

Codata IO stores every asset your app needs and connects it to the same data, access rules and email already running your backend — no bucket to wire up, no separate permissions to configure.

01 · your agent

02 · Codata IO connects it

03 · live files

files v1

action

Files · Assets · Access · Connected actions

The shift

What storage work becomes.

File permissions living apart from the rest of your data

Permissions run on the same access rules as everything else

One wrong setting away from making private files public

Private by default, using the same access rules as your data

Manual wiring just to give your backend access to its own files

Every file is available to the rest of your backend automatically

No simple way to tie a stored file to the workflow that uses it

Storage, email and the app act as one motion, not three separate steps

What it is

One place for every asset.

Where your app’s files and assets live — images, documents and uploads — kept in one place and connected to the rest of your data. You don’t stand up a separate bucket or wire up its own access layer.

FILE UPLOADED STORED & CONNECTED ACCESS ENFORCED USED BY THE APP

What you get

What a storage team owns.

cover.jpg image invoice.pdf document export.csv upload brand-kit.zip any file type
added by your agent
edited without a console
kept in one place

Files and assets, in one place.

Add and edit assets easily, whatever the file type. Images, documents and uploads are kept together and connected to the rest of your data, instead of scattered across a bucket you maintain yourself.

> send my photos directory to these recipients

← 1 action · storage + email

stepruns onstate read folderstoragedone attach filesstoragedone send mailemail serverdone one native action, not three separate steps

Connected actions.

“Send my photos directory to these recipients” is one native action — storage and email in the same motion.

Safe by default.

Files are private by default and permissions run on the same rules as everything else — not a separate setting to get wrong.

Your database One access layer Your files

One access layer, not two.

Your files are available to the rest of your backend the same way your database is, with no separate access layer to configure and nothing to keep in sync by hand.

Specs

Scales with your plan.

Hitting the cap pauses metered usage — nothing is deleted, and upgrading unpauses it immediately.

Compare plans
PlanStorageFile types
Free1 GBAny
Builder100 GBAny
Pro1 TBAny

How it works

From upload to any workflow.

01

Your agent uploads or references a file

In whatever coding agent you already use — Claude Code, Cursor, Copilot.

02

Codata IO stores it, connected to your data and access rules

No separate bucket, no separate permissions to configure.

03

The file becomes available to any other capability

Email it, filter by metadata or serve it back to the app.

04

Access follows the same permissions as your data

Protected by the same rules, not a separate default to check.

Why Codata IO

Not a bucket you wire up.

Most tools hand you an object storage bucket to configure and secure yourself. Codata IO runs storage as part of the same backend already serving your database and email — your agent can add a feature that stores, filters or emails a file, and Codata IO handles it as one connected system, not three.

If you’d rather run your own storage bucket and wire up the permissions yourself, a dedicated object storage service is a fine choice — it’s just not what this is built for.

Part of one backend

Not a standalone tool.

Product

Co-Live

Build and go live as one motion.

Product

Auto-Runtime

Stays live and adapts as your agent changes the app.

FAQ

Common questions about storage.

What kind of files can I store in Codata IO?

Any file type — images, documents, uploads and more, all stored in Codata IO and connected to the rest of your backend.

Do I need to configure access permissions for Codata IO storage separately?

No. Codata IO storage uses the same access rules as the rest of your backend, so it’s not a separate setting to get wrong.

Can a file stored in Codata IO trigger other parts of my app?

Yes. Storage, email and the rest of the app connect natively inside Codata IO — emailing a file the moment it’s uploaded is one action, not three.

What happens if I hit my Codata IO plan’s storage cap?

Usage pauses at the cap on your Codata IO plan — nothing is deleted, and upgrading your Codata IO plan unpauses it immediately.

One bill. No surprise bills.