Skip to main content

What's Missing & What's Next

Lioran S3 (Lioran Bastion) is developed by Lioran Developer Solutions (LDS), an initiative of Lioran Group, founded and led by Swaraj Puppalwar (Founder & CTO).

This document provides a transparent, technical breakdown of currently available capabilities, experimental subsystems, intentional omissions, and the product roadmap.

Release Milestones​

┌───────────────────────────────────────┬───────────────────────────────────────┐
│       Lioran S3 V1 Pre-Alpha          │          Planned Next Release         │
│       Released: 01 October 2026       │       Target: 17 November 2026        │
└───────────────────────────────────────┴───────────────────────────────────────┘

:::note Release Target Notice The target date of 17 November 2026 represents our planned milestone for the next feature release. Engineering schedules may adapt as we prioritize stability, security, and verification over calendar deadlines. :::

Capability Status Matrix​

We categorize every component of the Lioran S3 ecosystem into three clear operational states:

  1. AVAILABLE : Fully implemented, tested, and ready for single-node deployment.
  2. EXPERIMENTAL : Implemented and functional in pre-alpha, undergoing active performance tuning and interface stabilization.
  3. PLANNED : Designed or under active development on our engineering roadmap.
Subsystem / FeatureStatusDescription
Rust Storage Engine (bastion-object)AVAILABLESingle-node filesystem fanout with atomic staging and rollback.
RocksDB Metadata Engine (bastion-metadata)AVAILABLETransactional metadata persistence across 9 isolated column families.
Bounded Streaming I/OAVAILABLEFixed-size memory streaming buffers (64 KiB–4 MiB) preventing RAM spikes.
Strict & Balanced Durability ModesAVAILABLEConfigurable synchronous fsync (strict) vs OS writeback (balanced).
Resumable Multipart UploadsAVAILABLEMulti-chunk parallel ingestion with part SHA-256 verification and stitching.
HTTP Byte-Range Slicing (Range: bytes=)AVAILABLEPrecise byte offset seeking for video streaming and chunked downloads.
HMAC-SHA256 Presigned URLsAVAILABLETime-expiring signed upload/download tokens for delegated client access.
Role-Based Access Keys (bk_... / sk_...)AVAILABLEProgrammatic credentials with admin, readwrite, and readonly scopes.
Official TypeScript Driver (@liorans3/driver)AVAILABLEFull-featured client SDK for Node.js, Bun, and TypeScript environments.
Official Command Line Tool (@liorans3/cli)AVAILABLEMulti-profile CLI for bucket management, object uploads, and multipart jobs.
Docker & Caddy Automated DeploymentAVAILABLEProduction container stack with automated Let's Encrypt TLS certificates.
Integrated Video Transcoding (bastion-media)EXPERIMENTALAsynchronous HLS/DASH adaptive packaging and video thumbnail extraction.
Presigned Video Share TokensEXPERIMENTALTime-limited signed streaming manifests for HTML5 web players.
Zero-Copy Socket Transfer (splice/sendfile)PLANNEDKernel-level zero-copy egress pipeline to achieve 500+ MB/s read target.
Distributed Multi-Node Clustering (Raft)PLANNEDMulti-node consensus replication, distributed metadata, and high availability.
Object Versioning & Soft DeletePLANNEDMulti-version object retention with point-in-time recovery and rollbacks.
Server-Side Encryption at Rest (SSE-KMS / SSE-C)PLANNEDEnvelope encryption with customer-managed keys and hardware security modules.
Storage Tiering & Lifecycle ArchivalPLANNEDAutomated age-based migration to cold storage and archival media.
Web Administration ConsolePLANNEDBrowser-based graphical dashboard for bucket inspection, metric graphs, and key provisioning.

What Is Currently Missing (Intentional & Deferred Scope)​

To maintain uncompromising reliability and avoid architectural bloat in the single-node V1 Pre-Alpha release, the following features are currently not present:

1. AWS S3 XML/SigV4 Protocol Emulation​

  • Current State: Lioran S3 does not implement AWS S3's legacy XML schemas, SigV4 headers, or complex IAM policy JSON evaluators.
  • Rationale: Emulating AWS S3's historical XML error responses and signature schemes introduces substantial code complexity, memory overhead, and parsing latency.
  • Alternative: Lioran S3 provides a clean, modern REST API, an ergonomic TypeScript driver (@liorans3/driver), and a CLI (@liorans3/cli).

2. Distributed Clustering & Multi-Node Replication​

  • Current State: The V1 Pre-Alpha release is engineered specifically as a single-node high-performance storage engine.
  • Roadmap: Distributed multi-node clustering utilizing a Raft-based consensus metadata layer is slated for our V2 development phase.

3. Object Versioning​

  • Current State: Overwriting an object key replaces the previous payload atomically. Previous versions are not retained.
  • Roadmap: Versioned bucket policies with immutable version IDs are scheduled for late Q4 2026 / Q1 2027.

4. Server-Side Encryption at Rest (SSE-KMS)​

  • Current State: Data payloads are stored unencrypted on disk (relying on host filesystem encryption such as LUKS or BitLocker). In-transit encryption is enforced via TLS.
  • Roadmap: In-engine AES-256-GCM / ChaCha20-Poly1305 envelope encryption with pluggable KMS backends is planned for subsequent major releases.

Engineering Roadmap​

flowchart LR
    V1["V1 Pre-Alpha (Oct 2026)<br/>• Single-node core<br/>• RocksDB metadata<br/>• TypeScript Driver & CLI<br/>• 100 GiB Chaos-validated"] --> V1_1["Next Release (Nov 2026)<br/>• Zero-copy socket streaming<br/>• Read throughput optimizations<br/>• Enhanced video pipeline<br/>• S3-compatible gateway preview"]
    V1_1 --> V2["V2 Distributed (2027)<br/>• Raft multi-node consensus<br/>• Distributed sharding<br/>• Object versioning<br/>• Web management UI"]

Milestone: 17 November 2026 (Planned Target)​

  • Zero-Copy Socket Delivery: Refactor read streaming to utilize OS sendfile/splice primitives to exceed our 500 MB/s single-node egress target.
  • Lockless Read Seek Descriptors: Eliminate micro-contention during high-concurrency 32+ worker read bursts.
  • Media Engine Stabilization: Finalize API schemas for HLS/DASH manifest generation and signed player embed tokens.
  • S3 API Compatibility Adapter (Alpha): Optional lightweight compatibility proxy for existing AWS S3 SDK integration.

Long-Term Vision (2027)​

  • Distributed Raft Consensus: High-availability clustering with automatic leader election and transparent failover.
  • Object Lifecycle Policies: Automatic expiration, transition, and cold-tier compression rules.
  • Full Web Management Console: Real-time throughput graphs, bucket explorer, access key auditing, and transcode queue visualizer.

Feedback & Collaboration​

We welcome community feedback, feature requests, and bug reports: