Fundatio Trilunae Independent public-interest initiative in formation
Language
Menu
Development status

Development and publication work have resumed. Service APIs remain unavailable unless explicitly documented as live.

Triluna service model

Triluna Dropkit is a free ephemeral transfer boundary with 0 KB of production capacity.

Dropkit is designed for client-encrypted, short-lived transfers. It is free by policy, but it is not accepting files: production transfer capacity is exactly 0 KB, and the maximum retention policy is 24 hours.

Current policy

The present constraints are intentional and enforceable in the service contract.

Price
Free. There is no checkout, credit balance, or paid storage claim in this service model.
Transfer capacity
Exactly 0 KB in production: zero objects, zero object bytes, zero transfer bytes, and zero allocated storage bytes.
Retention ceiling
At most 24 hours (86,400 seconds). Future shorter retention is possible; a longer production value is rejected.
Content boundary
A future server may receive only client-produced ciphertext, encrypted metadata references, ciphertext integrity data, and lifecycle state—not files in plaintext, filenames, content keys, or private keys.

Future ciphertext lifecycle

Capacity may grow later without changing the privacy boundary.

The schema and node descriptor reserve a chunked, streaming-ready object manifest: each future chunk is an opaque object reference with ciphertext size and integrity digest. A transfer moves through created, uploading, ready, downloaded, expired, deleted, or failed states. Cleanup claims and retryable deletion state are modelled, but no storage binding or scheduler exists in this 0 KB configuration.

Increasing capacity later requires a separately reviewed client-side streaming-encryption format, recipient key-delivery design, ciphertext-only storage binding, quota and rate controls, abuse response, cleanup executor, deletion verification, and security review. A NAS or larger storage node changes capacity; it does not relax the E2EE requirement.

No misleading predecessor

A disabled, source-only private-object prototype remains a lifecycle reference only. It is not publicly available, is not renamed as Dropkit, and does not make an E2EE claim. This page describes the new, deliberately unavailable ciphertext-only service boundary.