Beeblos
BEEBLOS STORAGE

Keep your documents
on the infrastructure
you choose.

The choice of storage follows how your organisation operates: where the information resides, who manages the systems and which applications use it.

INFRASTRUCTURE

Storage adapts
to your organisation.

The document repository and the infrastructure that holds the files play different roles. Storage connects them within a single solution.

01

Beeblos FileStore

NATIVE ENGINE

Beeblos storage on file systems, for infrastructure managed by your organisation.

02

MinIO

OBJECT STORAGE

An object storage option for deploying repositories on your own infrastructure.

03

Amazon S3

AWS INTEGRATION

For projects with infrastructure on AWS, the storage integration is defined according to the repositories, operations and policies of the environment.

What connecting a storage system means

The backend holds the physical content. Beeblos manages its references, metadata and document access. The configuration of a specific integration sets the destination of the files, the versioning operations and the connection credentials.

Using an Amazon S3 destination and offering an S3-compatible API to other tools are different capabilities. The scope of each connection is defined in the project architecture.

Define the repository around
how the documentation is used.

LOCATION

Decide where the information should reside.

The architecture considers the systems available and the requirements for locating and managing content.

OPERATION

Relate storage to the applications that use it.

The design sets the document operations, the references and the credentials of each connection.

GOVERNANCE

Maintain access and retention criteria.

Repositories sit within company scopes and within the organisation's document policies.

Security and records governance