Object Storage

Estimated reading: 2 minutes

Robility Flow utilizes S3-compatible object storage for managing uploaded files, exported workflow definitions, execution artifacts, temporary processing data, and large execution payloads. Object storage provides scalable and durable storage for unstructured data that is generated or consumed by the platform during workflow execution.

Asset	Initial Size	Comments
Flow Definitions & Exports	500 MB Initial	Storage requirement increases over time based on the number of published flows, exported packages, and version history retained.
Uploaded Files / Documents	Variable	Storage consumption depends on business use cases, document volumes, file sizes, and retention policies.
Execution Logs (Cold Tier)	~1 GB / 100k Runs	Historical execution logs should be archived to low-cost storage tiers to optimize operational storage costs.
Platform Images (OCI)	~4 – 7 GB	Includes RobilityFlow Designer and Runtime container images, associated layers, and versioned image repositories.
PostgreSQL Data Volume	100 GB (Pilot) / 500 GB (Production)	Includes database tables, indexes, transaction logs (WAL segments), temporary objects, and growth capacity.
Redis AOF / RDB Snapshots	10 – 50 GB	Storage allocation depends on the required persistence, replay window, backup frequency, and retention requirements.

Supported object storage backends:

1. Amazon S3 (recommended for AWS deployments)
2. Google Cloud Storage (with HMAC keys for S3-compat. API)
3. NFS, Azure Files, AWS EFS, SMB/CIF (recommended for VM deployments without cloud object storage access)

Object Storage

Object Storage

CONTENTS