Connect storage

DataPrism never stores your file contents. Files are encrypted in your application, split into shards, and written to buckets that belong to you. The platform only keeps the encrypted index that says where everything is.

Supported providers

The signer URL belongs to a small service in your infrastructure. It authenticates your application and returns a short-lived URL for one storage operation and one hash-named object. Your permanent cloud credentials never leave that service.

Recommended bucket setup

• Create a dedicated bucket per project. Shards are content-addressed, so the bucket contains opaque objects named by hash; keeping it dedicated makes cleanup and migration simple.
• Give the signing service an identity scoped to that bucket only, with the minimum read, write, head, and delete permissions it needs.
• No public access is ever needed. Keep the bucket private.
• Authenticate every signer request, validate the object key and operation, and keep signed URLs short-lived.

Enter only the bucket metadata and HTTPS signer URL in the project form, or later from the project's Providers tab. Supply the signer's short-lived authentication token to the SDK at runtime; do not save it in the project.

One provider or several?

One bucket is enough to start. With two or more providers, uploads spread shards across them with erasure coding, so your files remain fully recoverable even if one provider is down. You can add a provider later; new uploads take it into account.

Where files show up

The project's Storage tab lists your files with their metadata: name, size, and upload date. Content never transits through the dashboard; uploads and downloads happen in your own application through the SDK, as shown in the examples.

Next step: invite your team.