Blimp
Configure a decentralized S3 server with Blimp
Key Features
Open-source and Trustful cloud.
Blimp offers a true multi-cloud alternative to traditional cloud S3 and file storage for all industries. Easily configure a high redundancy architecture of 11-14 nines with always ON storage and with zero RPO and RTO for disaster recovery.
Blimp also offers absolute privacy using Züs encrypted data sharing protocol, and immutability of data where no one can change or delete your uploaded data or view it other than in its original content.
Configure your best business uptime.
Blimp is a new way to store enterprise data with better performance and security than traditional cloud at a lower cost.The protocol inherently provides data ownership and privacy, and the ability for Enterprises to encrypt data and easily share with partners and vendors
Scalable and reliable business solutions
Blimp uses cases range from healthcare, and financials to storing logs etc, so it has use-cases in every industry that needs fast, secure and bespoke storage.
Lower TCO. Higher availability, security.
Blimp offers the flexibility to seamlessly switch providers at any time, allowing for enhanced performance and potential cost savings. It also enables on-the-fly provider additions to boost availability and redundancy, all without any data egress fees or hidden costs. With a straightforward pricing structure, you only pay one fixed storage fee, and Blimp ensures a Zero Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for Disaster Recovery.
Getting Started with Blimp
Sign up to Blimp for cloud storage and migration.
You can utilize Blimp as a direct storage solution. This means you can store and access your data directly through Blimp's platform.
Blimp can function as an S3 (Simple Storage Service) server, allowing you to store and retrieve data using S3 commands, which is commonly used for object storage on cloud platforms like AWS.
Blimp can also be used for cloud migration, suggesting that you can use it to transfer your data and applications from one cloud environment to another.
Purchase ZCN token to use as payment for storage services within the Blimp platform.
This section encompass various actions for managing Blimp allocations, ranging from adjusting size and duration to modifying blobbers and controlling the type of interactions allowed, as well as the ability to freeze or cancel allocations as needed.
This task involves increasing the size of a Blimp allocation, allowing it to handle more data or resources.
In this task, the duration of a Blimp allocation is prolonged, enabling it to remain active for a longer period.
This action involves incorporating a new blobber, which is a storage component, into the Blimp allocation, potentially expanding storage capacity or redundancy.
This task focuses on substituting an existing blobber with a new one within the Blimp allocation, possibly for performance improvement or maintenance reasons.
This setting restricts the Blimp allocation to only allow reads and file uploads
Freezing an allocation involves suspending any changes or modifications to it, effectively locking it in its current state.
Cancelling an allocation entails terminating it prematurely, ending any associated resources or activities.
Last updated