Permanent storage built into your workflow
Release artifacts, source archives, documentation snapshots. Developers can store what must outlive the current project, host or company.
Store for DevelopersImmutable artifacts
Store release binaries, build outputs and archives as permanent transactions with verifiable hashes.
Open standard
Files are standard Arweave transactions — retrievable by txID from any gateway. No proprietary format.
Small files free
Configs, license files, package metadata and docs are usually under 100 KB — stored free forever.
01Code and data outlive projects
A GitHub repo can be deleted. A hosting account can close. A company can shut down — taking internal archives with it.
Long Drive stores your files on Arweave, outside any single project or company. As long as the network exists, the data remains.
02What developers store
Source archives and release snapshots for projects you care about. Public documentation and changelogs. License and provenance files. Config templates.
Never store secrets, API keys or private credentials — Arweave content is public. Use encryption only where confidentiality is compatible with public storage.
03The practical case
An indie developer archived the source of an abandoned open-source project — a tarball around 200 KB plus docs. One-time fee: under $0.20. The project lives on after its repo is gone.
This is preservation the way the permanent web intends: code that survives maintainers, hosts and companies.
Developer FAQ
How do I retrieve a file later?
Use the transaction ID with any Arweave gateway, e.g. https://arweave.ar.io/{txID}. No Long Drive account required for public files.
Can I automate uploads?
A public API is on the roadmap. Today you can upload through the web interface or integrate directly with Arweave (Turbo/gateway).
Is Arweave storage suitable for backups?
For immutable, archival backups — yes. For frequently changing data, remember each version is a new transaction and consider whether public storage fits.