Your apps have always been able to handle text. Now they can handle everything else.

We've added native Cloud Storage and File Handling to both the Mayson Agent and the Manual Builder. Here's what that means, why it matters, and how to start using it today.

What We Built

Upload File Block

A one-click integration for user file uploads, available directly in the Manual Builder as a pre-built block.

Drop it into your app flow and your users can upload images, PDFs, audio files, documents — any file type you need. The block handles the entire upload pipeline: multipart form parsing, file validation, and storage routing. No wiring required.

Secure Asset Management

Files your users upload are stored in production-ready cloud storage, built into Mayson's infrastructure.

• Images, PDFs, audio, and documents are handled natively

• Storage is provisioned automatically — no S3 buckets to configure, no IAM policies to manage

• Assets are served securely, with access scoped to the right users

Why This Matters

Until now, if you wanted to build a media-rich application on Mayson — a transcription tool, a document manager, a photo gallery, a portfolio platform — you had two options: mock the uploads, or wire up an external storage provider manually.

Both options were friction. External storage meant leaving the Mayson ecosystem, configuring credentials, managing buckets, and handling file URLs yourself. Mocked uploads meant your app wasn't production-ready.

With native Cloud Storage, neither is necessary. File handling is now a first-class citizen inside the Mayson stack.

What You Can Build Now

Some of the application types this directly unlocks:

Document Management Apps — let users upload, store, and retrieve PDFs, spreadsheets, or contracts.

Media Platforms — image galleries, portfolio tools, or asset libraries with user-facing upload flows.

AI Processing Pipelines — upload an audio file, send it to a transcription service, return the result. The file handling layer is already there.

SaaS with Attachments — any product where users need to attach files to records: support tickets, project management tools, CRMs.

Forms with File Inputs — contact forms, job applications, onboarding flows. Any form that needs a file alongside the text.

How to Use It

In the Agent: Describe file upload behaviour in your prompt. The Agent now natively understands storage requirements and will provision the correct infrastructure.

"Build a document manager where users can upload PDFs, tag them by category, and search through their library."

The Agent handles storage, access control, and UI — in one build.

In the Manual Builder: Find the Upload File Block in your block library under Storage. Configure the accepted file types, max file size, and storage path. Wire it to your API or Logic layer as needed.

What's Coming Next

File handling is the foundation. The next layer is file processing — OCR, AI summarisation, format conversion, and automated workflows triggered by file events. We're building that now.

Start building media-rich applications today at app.mayson.dev. Native storage. No configuration. Just ship.