01 · Capabilities
Any format.
Zero friction.
StellrCloud accepts the media you actually work with - high-res images, long-form video, dense PDFs, and audio - with the same path from drop to Secure ID.
Video · Images · Documents
Upload anything that matters.
From small clips to multi-gigabyte masters. Fast transfer, uncompromised quality, lifetime and access controls built in.
02 · Defaults & Limits
Clear ceilings.
Predictable cost.
Every new account receives 15 GB of storage credits. Storage is consumed at the moment of upload and is not returned when an object expires. Re-up capacity at $0.035 per GB whenever you need more.
After the configured lifetime ends, the upload becomes inaccessible and the object is retired. Storage credits already spent remain spent.
Per upload unless you configure otherwise. At expiry the content is no longer reachable.
Granted to every new account. Consumed permanently on upload.
Add capacity in increments from 15 GB up to 30 TB.
If an upload would exceed your balance, pay a $5 surcharge or purchase the needed capacity.
Lifetime model
The clock starts when the upload is finalized. You set the window - days, months, or keep the 1-year default. Once it closes, access is revoked and the object is retired. Ideal for temporary handoffs, expiring deliverables, and clean hygiene.
Storage credits
Storage is a credit, not a reusable pool. Usage is committed at upload time and is not reclaimed when the object expires. This keeps the Secure ID model simple and predictable.
Re-up range
Purchase additional capacity in any amount from 15 GB to 30 TB at a flat $0.035 per GB. Scale only when you need it — no forced tiers.
Coming · Compression
More content.
Same footprint.
StellrCloud will integrate Oligos as a compression layer for eligible uploads. At a measured ~5.62× ratio, significantly more original content can fit inside the same storage credit.
That turns storage credits into an extremely efficient surface for media, archives, and document sets - without changing the Secure ID model or lifetime controls. Applied where beneficial; quality and integrity remain non-negotiable.
Explore OligosCompression is applied selectively to suitable content. Exact ratios depend on file type and entropy. The Secure ID and lifetime rules remain identical.
03 · The process
Three steps.
One key.
Upload
Drop files into the protected client. No account maze - straight into a controlled environment with lifetime defaults ready. Storage credits are consumed here.
Configure
Set lifetime, retrieval count, view timeouts, and confirmation screens. Attach utility policies and 2FA when you need them. You define the rules.
Copy Secure ID
Take the generated Secure ID and store it safely. That string is the only path to the content - mathematically required.
The Secure ID is the ultimate key to your upload. Without it, decryption and access are mathematically impossible. Lifetime, retrieval limits, timeouts, utility policies, and 2FA apply independently of who holds the ID.
04 · Custom configurations
Gate access.
Shape every retrieval.
Beyond lifetime and Secure ID, every upload can carry fine-grained access rules. Filter who proceeds, cap how many times content is retrieved, and limit how long retrieval details stay visible - all configured at upload time.
Filter before unlock
Screens that appear before content is accessed. Use them to filter who is - and who is not - supposed to proceed. Intentional friction that keeps unauthorized eyes out without changing the Secure ID itself.
- 01 Pre-access gate before any decrypt path opens
- 02 Separate intended recipients from everyone else
- 03 Configured per upload; travels with the object
Cap how many times
Set the maximum number of times a resource can be retrieved. Once the count is reached, further retrievals are blocked - but the resource still persists until its lifetime ends. No early deletion, full control over exposure.
- 01 Hard ceiling on successful retrievals
- 02 Object remains until lifetime expiry
- 03 Ideal for one-time handoffs and limited shares
Limit viewing windows
Define how many seconds or minutes an individual may see retrieval information. When the window closes, the user is booted. Short windows reduce shoulder-surfing and leftover sessions.
- 01 Per-session visibility in seconds or minutes
- 02 Automatic boot once the timer elapses
- 03 Stacks cleanly with retrieval count and 2FA
Configurations compose
Confirmation screens, retrieval counts, and timeouts are independent levers. Use one, two, or all three on the same upload. Pair them with utility policies and email 2FA for multi-layer control - or leave them off for a clean Secure ID-only share. Every rule is set at upload time and enforced for the full lifetime.
Who may attempt access
How many successful retrievals
How long details stay visible
05 · Extended enforcements
Define utility.
Require approval.
Beyond lifetime, Secure ID, and access configs, you can attach enforceable expectations to every upload - and gate final unlock behind your own email approval. Control how content is meant to be used, and who actually gets in.
Outline how content may be used
When configuring an upload, you can define its utilities - explicit expectations you express about how the content is intended to be utilized. These are not decorative labels; they are the stated purpose of the upload.
- 01 Specify permitted uses: review only, derivative work, internal distribution, archival, etc.
- 02 Set clear boundaries so recipients understand what the Secure ID grants - and what it does not.
- 03 Attach expectations at upload time; they travel with the object for the full lifetime window.
Unlock only after you approve
Enable two-factor approval on any upload. Even with a valid Secure ID, the content remains locked until you explicitly approve the access attempt via email.
- 01 Someone presents the Secure ID and requests access.
- 02 You receive an email notification with the request details.
- 03 Only after your approval does the upload fully unlock for that access.
2FA access flow
Secure ID used
Recipient presents the ID to request the upload.
Content stays locked
Partial handshake only - full decrypt is held.
Email approval
You review and approve or deny from your inbox.
Full unlock
Only after approval is access granted completely.
Multi-layer control by design
Confirmation screens filter intent. Retrieval counts and timeouts bound exposure. Utility policies make purpose explicit. Email 2FA makes access contingent on your live consent. Together they extend the Secure ID model: possession of the key is necessary, but never sufficient when you choose to enforce stricter rules. Configure any combination at upload time - or none. Your call.
06 · Coming soon
Already strong.
Still expanding.
The core model is live: Secure ID, lifetimes, confirmation screens, retrieval counts, timeouts, utility policies, and email 2FA. Next waves deepen owner control, capacity, and ties into the rest of the Stellr ecosystem.
Admin Secure ID
A Secure ID reserved for you alone. Unbounded by the upload’s confirmation screens, retrieval counts, timeouts, or other recipient-facing rules - full owner override when you need it.
Download controls
Configure whether content can be downloaded or remains view-only. Pair with timeouts and retrieval counts for strictly ephemeral shares.
Pay-as-you-go
A flexible plan for heavy users who outgrow default storage - transparent metering without forcing you into rigid tiers.
Oligos integrations
Native compression via Oligos on eligible uploads. Stretch storage credits while preserving integrity and the Secure ID model.
Extended lifetimes
More lifetime options beyond the 1-year default: 1.5 years, 2 years, 3 years, and indefinite - for archives and long-horizon handoffs.
Ecosystem depth
Deeper integration with Orrin, Yabble, and Exegesis - so Secure ID objects move cleanly through agents, protocols, and context-aware workflows.
07 · Built for
Students
Share coursework, financial docs, and portfolios without friction - access only for people you choose, with automatic expiry when the term ends. Cap retrievals for one-time submissions.
Employees
Receive and send work files under lifetime controls. Secure IDs, confirmation screens, timeouts, and optional 2FA keep transmission intentional without heavy IT overhead.
General use
Anyone who needs content uploaded, secured, time-bound, retrieval-limited, and reachable only by those granted the key - personal or professional.
Ready
Store. Transmit. All with intent.
Start a protected upload. Keep the 1-year default or set your own lifetime. Add confirmation screens, retrieval counts, timeouts, utility policies, and 2FA if you need them. Leave with a Secure ID.
Minimal. Time-bound. Locked by design.
Secure storage and transmission for the files that matter - with clear limits, access configurations, utility policies, and optional approval gates.