Help & Knowledge Base

Frequently Asked Questions

Authoritative answers about Lioran S3, architectural design, licensing, performance benchmarks, and deployment.

What is Lioran S3 and who builds it?

Lioran S3 (engine name: Lioran Bastion) is a high-performance single-node object storage server and media engine engineered in Rust. It is developed and maintained by Lioran Developer Solutions (LDS), an initiative of Lioran Group, founded and led by Swaraj Puppalwar (Founder & CTO).

Is Lioran S3 open source?

No. Lioran S3 and Lioran Bastion are proprietary software developed and owned by Lioran Developer Solutions under a Proprietary Source Code License (Copyright © 2026 Lioran Developer Solutions. All rights reserved). Access to source code, documentation, or binary packages does not grant an open-source license or transfer intellectual property rights.

What is the current release status and when is the next release?

The current release is Lioran S3 V1 Pre-Alpha, officially released on 01 October 2026. The next planned feature release has a target milestone of 17 November 2026, focusing on zero-copy socket streaming optimizations and stabilized video packaging pipelines.

Is Lioran S3 AWS S3 API compatible?

No. Lioran S3 implements its own modern REST API, native connection protocol (bastion://), official TypeScript driver (@liorans3/driver), and CLI (@liorans3/cli). It is designed to be lean and memory-efficient rather than an emulation layer for AWS S3 XML/SigV4 protocol compatibility.

What performance and resilience has been empirically verified?

In our official 100.52 GiB soak and chaos benchmark (Run ID: 20260930T111856-d14352), Lioran S3 ingested 6,050 objects across 15 buckets with 32 concurrent workers at an average write throughput of 87.3 MB/s (peak burst: 663.2 MB/s). During active streaming writes, 5 hard SIGKILL crashes were injected; the engine recovered cleanly 5 out of 5 times with 0 unexpected write failures. Read throughput averaged 281.7 MB/s (peak: 414.1 MB/s). 188 random samples were cryptographically audited with 0 SHA-256 checksum mismatches and 0 missing objects.

Where can I view the raw benchmark and chaos proof logs?

All 12 raw benchmark artifacts from the 100.52 GiB run—including summary.json, summary.txt, crashes.log, integrity.log, metrics.jsonl, and recovery.log—are publicly available at https://liorans3.sbs/proof/ and documented in detail on the official documentation site.

How does Lioran S3 prevent memory spikes during large file uploads?

Lioran S3 strictly decouples the metadata plane from the object data plane. Payloads stream through bounded-size memory buffers (typically 64 KiB–4 MiB) directly between network sockets and disk files, guaranteeing that objects are never buffered entirely in RAM. Raw payload bytes are never stored in the RocksDB metadata database.

How does write durability and crash consistency work?

Lioran S3 supports configurable crash durability modes. In 'strict' mode, every write buffer is flushed and synced to disk storage via synchronous fsync calls before an upload is acknowledged with HTTP 200 OK. In 'balanced' mode, the engine leverages OS writeback caching for higher throughput. In both modes, writes use a two-phase staging-and-promote protocol with automatic rollback if metadata commits fail.

Can I self-host Lioran S3?

Yes. Lioran S3 is designed as a self-contained, single-node storage server. You can deploy it using Docker Compose (paired with Caddy or Nginx for automatic TLS termination) or run the native compiled binary directly on your Linux, macOS, or Windows servers.

How do I install the CLI and TypeScript Driver?

The CLI can be installed globally via npm with `npm install -g @liorans3/cli@prealpha`. The TypeScript/JavaScript client library can be added to any Node.js, Bun, or TypeScript project with `npm install @liorans3/driver`.

How does authentication and access control work?

Lioran S3 provides administrative authentication with Argon2id password hashing, expiring HMAC-SHA256 presigned URLs for delegated browser uploads/downloads without leaking credentials, and role-based programmatic Access Keys (admin, readwrite, readonly) using `bk_...` / `sk_...` credential pairs.

Where can I report bugs or ask questions?

You can file bug reports and feature requests on our official GitHub repository (https://github.com/LioranGroupOfficial/LioranBastion-Rust), participate in discussions on Discord (https://discord.gg/WsWWThjPMp), or email the team at contact@liorans3.sbs.

What is the commercial and refund policy?

Except where required by applicable law, payments made for Lioran S3 commercial products, licenses, services, or subscriptions are non-refundable once payment has been successfully processed. Please review our documentation and evaluation builds before making any purchase.

Still have questions?

We're here to help. Reach out to our engineering team or join our Discord community.