Enterprise-class Storage made simple

Odilon is a simple, secure, and fully Open Source object storage server that runs on standard hardware.

Designed for small and medium-scale deployments (up to roughly 100 TB), it provides reliable storage for documents, images, audio, video, and other large files—without the complexity of distributed storage systems.

Odilon includes encryption, software RAID, erasure coding, object versioning, and Internet-based master–standby replication, all under a clear standard license with no hidden commercial restrictions.

Main features

■ Scalable Object Storage on commodity disks
■ It has a simple single-level folder structure similar to the Bucket/Object model of Amazon S3
■ Single binary, does not need database or other external software
■ Runs on Linux, Windows, and macOS
■ License Open Source Apache 2. It can be used for Open Source and commercial projects
■ HTTP/S for client server communication
■ Encryption at rest using modern algorithms (AES GCM-SIV)
■ Redundancy using Erasure Coding and software RAID. Tolerates full disk failures
■ Data immutability. Odilon supports two storage modes that protect data from deletion, whether accidental or intentional: Read Only and WORM (Write Once Read Many)
■ Master - Standby architecture with async replication over the web, for disaster recovery, high availability, archival, ransomware protection
■ Version Control
■ Simple operation. Adding new disks requires one line in the config file, and an asynchronous process sets up disks and replicate data in background
■ Disk monitoring for silent and slow data degradation detection (bit rot detection)
■ Integration with Key Management Server Hashicorp Vault
■ SDK Java for client applications
■ Developed in Java (uses Spring Boot, OkHttp, Jackson, Caffeine, Dropwizard Metrics, among others)

Security

Odilon keeps objects encrypted (Encryption at Rest) using AES GCM-SIV with keys size of 256 bits.

Encryption has the following benefits:

■ It simplifies data protection, applications dont need to worry about protecting the data or encryption keys.
■ If data falls into the hands of an attacker, they cannot read it without also having access to the encryption keys. If attackers obtain the storage devices containing the data, they will not be able to understand or decrypt it.
■ It helps reduce the attack surface by removing lower layers of the hardware and software stack.
■ Simplify security management, centrally managed encryption keys create a single place where data access is enforced and can be audited.
■ It provides a privacy mechanism by limiting the access that systems and engineers have to data.

Each object stored by Odilon has a unique encryption key. Odilon uses envelope encryption (i.e. encrypting a key with another key), every object is encrypted with its unique key and the key is encrypted by Odilon key management layer or by a Key Management Server (KMS)

A KMS is software for generating, distributing, and managing cryptographic keys. It includes back-end functionality for key generation, distribution, and replacement. Moving key management to KMS prevents application reverse engineering attacks, simplifies operational maintenance, and compliance with security policies and regulations.

Odilon integrates with the KMS Open Source Hashicorp Vault.

Data Replication

Odilon can be configured to use software RAID for data replication. The supported configurations are

RAID 0. Two or more disks are combined to form a volume, which appears as a single virtual drive. It is not a configuration with data replication, its function is to provide greater storage and performance by allowing access to the disks in parallel.
RAID 1.For each object, 1 or more exact copies (or mirrors) are created on two or more disks. This provides redundancy in case of disk failure. At least 2 disks are required, Odilon also supports 3 or more for greater redundancy.
RAID 6 / Erasure Coding. It is a method of encoding data into blocks that can be distributed across multiple disks or nodes and then reconstructed from a subset of those blocks. It has great flexibility since you can adjust the number and size of the blocks and the minimum required for recovery. It uses less disk space than RAID 1 and can withstand multiple full disk failures. Odilon implements this architecture using Reed Solomon error-correction codes.

Reed Solomon codes are widely used, from the Voyager probes exploring the solar system, to the James Webb telescope, to the QR codes on mobile phones.

The supported configurations are:
- 3 disks (2 data and 1 parity, supports 1 full disk failure)
- 6 disks (4 data and 2 parity, supports up to 2 full disks failure)
- 12 disks (8 data and 4 parity, supports up to 4 full disk failure)
- 24 disks (16 data and 8 parity, supports up to 8 full disk failure)
- 48 disks (32 data and 16 parity, supports up to 16 full disk failure)

Master Standby Architecture

Odilon supports Master - Standby Architecture for disaster recovery, high availability, archival, and ransomware protection. Data replication is done asynchronously using HTTP/S over the local network or the Internet. Setting up a standby server is simple, just add the URL and credentials to the master configuration file and restart. Odilon will propagate each operation to the standby server. It will also run a replication process in background for data existing before connecting the standby server.

What Odilon is not

Odilon is not a Distributed Storage like Cassandra, Hadoop etc.
Odilon supports master-standby architecture for archival, backup and data protection, but it is not a Distributed Storage and it does not support active-active replication.
Odilon is not a File System like GlusterFS, Ceph, ext4, etc.
It uses the underlying file system to stores objects as encrypted files, or in some configurations to break objects into chunks.
Odilon is not a NoSQL database like MongoDB, CouchDB, etc.
Odilon is not designed to store json or xml but files (like pdf or jpg). It does not use a database engine, it has its own journaling agent for Transaction Management and only supports simple queries, ie. to retrieve an object and to list the objects of a bucket filtered by objectname's prefix.
Odilon is not optimized for a very large number of small files
Odilon does not have optimization for lots of small files. The files are simply stored encrypted to local disks. Plus the extra meta file and shards for erasure coding.
S3 compatibility
Odilon API is simpler than S3. It supports a subset of th the AWS S3 API, ie.the bucket/object methafor to organize the object space.

Using Odilon

Odilon Java SDK (software Develoment Kit) can be used by client applications to interact with the server, applications in other languages can access the server through the REST API.
A Java client program that interacts with the Odilon server must include the Odilon SDK jar in the classpath (for example odilon-client-2.0.jar).
A typical architecture for a Web Application is

Example to upload 2 pdf files:


String endpoint = "http://localhost"; 

/** default port */
int port = 9234; 

/** default credentials */
String accessKey = "odilon";
String secretKey = "odilon";
										
String bucketName  = "demo_bucket";
String objectName1 = "demo_object1";
String objectName2 = "demo_object2";
										
File file1 = new File("test1.pdf");
File file2 = new File("test2.pdf");
										
/* put two objects in the bucket,
the bucket must exist before sending the object,
and object names must be unique for that bucket */
										
OdilonClient client = new ODClient(endpoint, port, accessKey, secretKey);

client.putObject(bucketName, objectName1, file1);
client.putObject(bucketName, objectName2, file2);

Download Odilon

Odilon Server current version is 2.0, for older versions please visit the download page.

To run Odilon Server you must have Java 17 installed.

The executable is the same for all platforms, the difference are the scripts to start and stop the program.

From Maven Central or MVN Repository

					
						<dependency>
							<groupId>io.odilon</groupId>
							<artifactId>odilon-client</artifactId>			
							<version>2.0</version>
						</dependency>

Previous version that support Java 11 and works with Odilon server 2.0:

					
						<dependency>
							<groupId>io.odilon</groupId>
							<artifactId>odilon-client</artifactId>			
							<version>1.15.2</version>
						</dependency>

For older versions of the client SDK can be downloaded from MVN Repository or Maven Central.

Changelog

Version 2.1 (Scheduled for Sept 2026)
■ ObjectMetadata encrypted on disk
■ AES key size increased from 128 to 256 bits
■ Improvements for key management
Version 2.0 (20 May 2026)
■ upgrade to Jackson 3
■ Master-Standby replication: bug fixes, optimization
Version 1.15 (1 Feb 2026)
■ Raid 6 performance improvement by adding 32MB x N buffers pool for faster encoding/decoding
■ Spring Boot 4.0.1 and other libraries upgraded.
■ Content Length in all responses.
■ ObjectMetadata extended to contain source file length.
Version 1.14 (9 Oct 2025)
■ bug file cache expired still returned as valid in Raid 6
■ Presigned-urls stay valid until their expiration date even if the server is restarted
■ ObjectStream can be served with a http header cache ( default value is 5m, set up in odilon.properties -> server.objectstream.cache.secs )
■ Spring Boot 3.5.4, Odilon client 1.15, Jackson 2.19.2, google.guava 33.4.8-jre, Spring Vault 3.2.0
Version 1.13 (1 Jun 2025)
■ fix bug RAID 6 restore disk when fails disk number 2 of the RAID.
■ Spring Boot 3.4.1
Version 1.12
■ bug RAID 0 delete object fixed.
Version 1.9
■ Fix Replication bug for bucket rename.
■ Fix bucket Cache bugs.
■ Clean up source code (add ObjectPath and other classes).

Secure and redundant Open Source Object Storage

Enterprise-class Storage made simple

Main features

Security

Data Replication

Master Standby Architecture

What Odilon is not

Using Odilon

Download Odilon

Odilon Server Linux and Mac

Odilon Server Windows

Odilon SDK client library

Documentation

Installation and configuration

Java application development

Server design and development

Videos

Changelog