DEV Community

Cover image for What Lioran S3 V1 Pre-Alpha Supports Today and What Comes Next
Swaraj Puppalwar
Swaraj Puppalwar

Posted on

What Lioran S3 V1 Pre-Alpha Supports Today and What Comes Next

Lioran S3 V1 Pre-Alpha: Current Scope and Roadmap

Lioran S3, also known as Lioran Bastion, launched its V1 Pre-Alpha on October 1, 2026.

The next planned version is scheduled for November 17, 2026.

I’m Swaraj Puppalwar, Founder & CTO at Lioran Group and Lioran Developer Solutions (LDS). This article is a deliberately plain description of what the current release supports, what it does not, and what is planned.

That distinction matters more than hype.

Supported today

Object storage

The server currently supports native object operations:

  • PUT
  • GET
  • HEAD
  • DELETE
  • listing
  • prefix filtering
  • cursor pagination
  • byte-range reads

Buckets

Current bucket features include:

  • create
  • list
  • inspect
  • update
  • delete
  • storage quotas
  • tags/configuration fields exposed by the driver

Streaming

Large object paths use bounded-memory streaming rather than requiring entire payloads in RAM.

Multipart

Current multipart support includes:

  • create upload
  • upload parts
  • inspect status
  • resume
  • complete
  • abort
  • high-level automatic multipart orchestration

Security

Current security features include:

  • HTTP Basic authentication
  • Argon2id password hashing
  • admin/readwrite/readonly roles
  • bootstrap password rotation
  • user CRUD
  • access key creation
  • access key rotation
  • access key revocation
  • credential masking
  • production credential checks
  • CORS configuration

Signed URLs

The server supports expiring signed:

  • GET
  • PUT
  • HEAD

URLs using cryptographic signing.

Reliability

Current storage-safety mechanisms include:

  • temporary/staged writes
  • configurable durability mode
  • object integrity metadata
  • bucket quota checks
  • host free-space guardrails
  • graceful shutdown behavior

Metadata

Metadata is stored separately from object payloads using embedded RocksDB.

Media

Experimental media features currently include:

  • video upload
  • transcoding
  • HLS generation
  • poster generation
  • playback URLs
  • downloadable processed video
  • video share links
  • image resize
  • image conversion
  • image quality optimization

FFmpeg is required for video processing.

Developer tooling

Current official TypeScript package:

npm install   @liorans3/driver@prealpha
Enter fullscreen mode Exit fullscreen mode

Current official CLI:

npm install -g   @liorans3/cli@prealpha
Enter fullscreen mode Exit fullscreen mode

Observability

Current operations surfaces include:

  • /health
  • /metrics
  • system information
  • performance diagnostics
  • CLI doctor
  • machine-readable CLI JSON mode

Current limitations

Single-node

V1 is not a distributed cluster.

There is currently no:

  • multi-node replication
  • Raft consensus
  • active-active topology
  • erasure coding

Those layers are intentionally deferred.

Not yet AWS S3 API compatible

Lioran S3 currently provides S3-style object-storage semantics, but the native API is not yet a drop-in implementation of the AWS S3 REST protocol.

This means existing AWS S3 SDKs should not be assumed to work directly.

Use the official driver or API.

Local filesystem dependency

The embedded storage architecture expects direct local filesystem behavior.

Do not casually place RocksDB over a network filesystem with incompatible locking or persistence semantics.

Media dependency

Video functionality requires:

ffmpeg
ffprobe
Enter fullscreen mode Exit fullscreen mode

Planned areas

The current roadmap includes:

AWS S3 compatibility

A compatibility layer for existing S3 ecosystem tooling.

Object lifecycle rules

Automatic expiry and storage lifecycle behavior.

Webhooks

Object mutation events such as:

object:created
object:deleted
Enter fullscreen mode Exit fullscreen mode

Fine-grained authorization

More expressive IAM-style policy controls.

Distributed storage

Future work can include clustering and replication after the single-node engine reaches the required level of correctness and stability.

Why publish limitations?

Because infrastructure documentation should help developers make decisions.

Calling a native REST object store “fully S3 compatible” before the S3 compatibility layer exists would make the documentation less useful.

Calling pre-alpha storage “production ready” because a benchmark looked good would make it less useful again.

The current goal is to build the system in visible stages and document the actual contract at each stage.

Release timeline

October 1, 2026
V1 Pre-Alpha launched

November 17, 2026
Next planned Lioran S3 version
Enter fullscreen mode Exit fullscreen mode

Resources

Product:

https://liorans3.sbs

Documentation:

https://docs.liorans3.sbs

Repository:

https://github.com/LioranGroupOfficial/LioranBastion-Rust

Lioran Group:

https://lioran.group

Lioran S3 is developed by Lioran Developer Solutions, part of the broader infrastructure work of Lioran Group, founded and technically led by Swaraj Puppalwar.

Top comments (0)