Stashify

Encrypted storage. Your providers. Your keys.

An open-source, privacy-focused storage system that turns third-party platforms into encrypted storage backends.

---

What is Stashify?

Stashify is an open-source, provider-agnostic storage system designed around one simple idea:

Your storage provider shouldn't have to be your storage system.

Stashify lets you use services such as Telegram and Discord as storage backends, while encryption and file management remain under your control.

Files are encrypted locally, split into chunks, and uploaded as ciphertext. Chunks can be stored on one provider or distributed across multiple providers depending on your configuration.

                          STASHIFY
                             │
                      Storage Engine
                             │
                ┌─────────────┴─────────────┐
                │                           │
            Encryption                  Chunking
                │                           │
                └─────────────┬─────────────┘
                              │
                       Storage Router
                              │
                ┌─────────────┴─────────────┐
                │                           │
            Telegram                     Discord
                │                           │
         encrypted chunks            encrypted chunks

Stashify does not provide the underlying storage.

It provides the abstraction that lets you use storage you already have access to.

---

Why Stashify?

Traditional cloud storage usually means trusting one provider with both your data and your storage.

Stashify separates those concepts.

Problem	Stashify
Vendor lock-in	Provider-agnostic storage abstraction
Provider sees plaintext	Files are encrypted before upload
Large files	Automatic chunking
Provider-specific limits	Provider-aware chunking
Single provider dependency	Multi-provider storage
Provider-specific APIs	One consistent interface

---

Features

Client-side encryption

Your files are encrypted before they leave your device.

                     YOUR DEVICE
                          │
                     Plaintext
                          │
                          ▼
                     Encryption
                          │
                          ▼
                       Chunking
                          │
                          ▼
                 Encrypted ciphertext
                          │
               ┌──────────┴──────────┐
               ▼                     ▼
           Telegram               Discord

Storage providers should only receive ciphertext.

Stashify is designed around:

• Client-side encryption
• Authenticated encryption (AEAD)
• Per-file cryptographic keys
• Proper key derivation
• Cryptographically secure randomness
• No custom cryptographic primitives
• Authenticated chunk integrity
• Local key management

Stashify uses established cryptographic libraries rather than implementing cryptography from scratch.

Security note: Stashify does not claim that multi-provider storage makes encryption stronger. Confidentiality comes from the cryptographic design and key management. Multi-provider storage primarily provides distribution, redundancy, and provider independence.

---

Key Management

Stashify uses a Repository Master Key (RMK) hierarchy for key management:

Repository Master Key (RMK)
        │
        ├── File Encryption Key 1
        ├── File Encryption Key 2
        └── File Encryption Key N

How it works

1. stash init generates a cryptographically random Repository Master Key (RMK)
2. The RMK is stored in your OS credential store (Windows Credential Manager, macOS Keychain, Linux secret-service) via the keyring library
3. Each file gets a unique File Encryption Key derived from the RMK + file ID
4. File keys are used to encrypt chunks and filenames
5. No password prompts during normal operations

Key Storage

• RMK → OS keyring (Windows Credential Manager / macOS Keychain / Linux secret-service)
• File keys → Derived on-the-fly from RMK + file ID (never stored)
• Chunk keys → Derived from file key + chunk index
• Metadata → Only non-secret identity info in .stash/identity.json

UX Flow

First device:

stash init
    ↓
Generate RMK
    ↓
Protect/store RMK in OS keyring
    ↓
Show recovery key (RMK hex) — SAVE THIS!
    ↓
Ready

Normal operations:

stash put file.zip
    ↓
Retrieve RMK from keyring
    ↓
Generate/use File Encryption Key
    ↓
Encrypt
    ↓
Upload

No password prompt.

New device / recovery:

stash unlock --recovery-key <hex>
    ↓
RMK restored in OS keyring
    ↓
Ready

Key Commands

Command	Description
stash key-commands status	Show key management status
stash key-commands lock	Remove RMK from keyring (lock repo)
stash key-commands unlock --recovery-key <hex>	Restore RMK from recovery key
stash key-commands recovery	Show RMK for backup

---

Chunked storage

Large files are automatically split into manageable chunks.

movie.mkv
    │
    ▼
 encrypted data
    │
    ▼
┌────────┬────────┬────────┬────────┐
│ chunk0 │ chunk1 │ chunk2 │ chunk3 │
└────────┴────────┴────────┴────────┘
    │         │        │        │
    ▼         ▼        ▼        ▼
 encrypted encrypted encrypted encrypted

Each chunk is independently tracked and authenticated.

The storage engine can account for provider-specific upload limitations without exposing those implementation details to the rest of the application.

---

Multi-provider storage

Stashify can store files across multiple storage providers. Currently only the Single strategy is implemented (all chunks on one provider). Additional strategies are planned.

Current strategies:

Strategy	Status	Description
Single	✅ Implemented	Store all chunks on one provider
Split	🚧 Planned	Distribute chunks across multiple providers
Balanced	🚧 Planned	Dynamically distribute chunks based on provider state
Replicated	🚧 Planned	Store copies across multiple providers

---

Provider abstraction

Providers are implementations of the same storage interface.

                     Storage Provider
                            │
           ┌────────────────┼────────────────┐
           │                │                │
       Telegram          Discord          S3 / B2
           │                │                │
           └────────────────┼────────────────┘
                            │
                      Storage Engine

The core engine does not need to know how Telegram or Discord works.

This makes it possible to add new providers without rewriting the storage system.

Planned providers include:

• S3-compatible storage
• Backblaze B2
• Google Drive
• Local filesystem
• WebDAV
• Other community-built providers

---

Provider Support

Provider	Status
Telegram	✅ Implemented
Discord	✅ Implemented
S3-compatible	🚧 Planned
Backblaze B2	🚧 Planned
Google Drive	🚧 Planned
Local filesystem	🚧 Planned
WebDAV	🚧 Planned

Provider availability and capabilities are subject to the APIs, limits, and policies of the respective services.

About "unlimited storage"

Stashify does not provide unlimited storage.

It does not bypass provider limits or guarantee unlimited capacity.

Actual storage capacity, file-size limits, rate limits, retention policies, and availability depend on the underlying provider.

Stashify's job is to abstract those providers and make the best use of the storage available to the user.

---

Security & Privacy

Stashify is designed around a simple trust model:

              Trusted
                 │
                 ▼
           ┌───────────┐
           │ User Device│
           └─────┬─────┘
                 │
           encrypted data
                 │
         ┌───────┴───────┐
         ▼               ▼
     Telegram          Discord
     untrusted         untrusted
      storage           storage

Principles

Local-first encryption

Plaintext files are processed locally before being uploaded.

Untrusted providers

Storage providers are treated as storage infrastructure, not trusted holders of plaintext data.

No custom cryptography

Stashify uses established cryptographic implementations.

Authenticated data

Encrypted chunks provide confidentiality and integrity.

Minimal exposure

Provider APIs receive only the information required to store and retrieve encrypted data.

Open source

The codebase is intended to remain publicly auditable.

Stashify is early-stage software. Do not rely on it for critical backups until the security model, implementation, and recovery mechanisms have been thoroughly reviewed.

---

Architecture

At a high level:

                          ┌───────▼───────┐
                          │      CLI      │
                          └───────┬───────┘
                                  │
                          ┌───────▼───────┐
                          │  Core Engine  │
                          └───────┬───────┘
                                  │
               ┌──────────────────┼──────────────────┐
               │                  │                  │
               ▼                  ▼                  ▼
           Encryption          Chunking           Metadata
               │                  │                  │
               └──────────────────┼──────────────────┘
                                  │
                          ┌───────▼───────┐
                          │ Storage Router│
                          └───────┬───────┘
                                  │
                     ┌────────────┼────────────┐
                     ▼            ▼            ▼
                 Telegram      Discord       Future
                                               Providers

The architecture intentionally separates:

• User interface
• Core storage logic
• Cryptography
• Chunking
• Metadata
• Job execution
• Provider implementations

This allows the system to evolve without coupling the entire codebase to a specific provider.

---

Project Status

Stashify is currently in early development.

The architecture is being actively developed and APIs may change significantly.

Component	Status
Project architecture	In progress
Python CLI	✅ Implemented
Encryption	✅ Implemented
Chunking	✅ Implemented
Manifest / metadata	✅ Implemented (JSON)
Provider abstraction	✅ Implemented
Telegram provider	✅ Implemented
Discord provider	✅ Implemented
Async job engine	✅ Implemented
Key management (RMK)	✅ Implemented
Multi-provider routing	🚧 Planned
Resumable transfers	🚧 Planned
Integrity verification	🚧 Planned
Repair / recovery	🚧 Planned
Additional providers	🚧 Planned

Features marked Planned or Future should not be considered implemented.

---

Development

Stashify is built with Python and is designed around asynchronous I/O.

The project aims to keep the core storage engine independent from its user interfaces and provider implementations.

A typical architecture is:

UI
  │
  └── CLI
       │
       ▼
Core Storage Engine
       │
  ├── Crypto
  ├── Chunking
  ├── Metadata
  ├── Jobs
  └── Storage Router
       │
       ├── Telegram
       ├── Discord
       └── Future Providers

See CONTRIBUTING.md for contribution guidelines.

---

Roadmap

The long-term goal is to turn Stashify into a flexible encrypted storage layer that can sit on top of almost any suitable storage provider.

Near term

• Core encryption pipeline
• Chunking
• JSON metadata
• Telegram provider
• Discord provider
• Async transfer system
• Repository Master Key (RMK) hierarchy
• Resumable uploads
• Multi-provider routing

Medium term

• Multi-provider routing
• Replication
• Integrity verification
• Recovery/repair
• Provider health monitoring

Long term

• S3-compatible providers
• Backblaze B2
• Google Drive
• WebDAV
• Local filesystem backend
• Additional community providers
• Advanced redundancy strategies

The roadmap is intentionally flexible and will evolve as the project matures.

---

License

Stashify is released under the MIT License.

See LICENSE for the full license text.

---

Stashify
_{Your files. Your keys. Your storage.}