Ocaltio
Storage that grows with everything you already own — one explorer for every disk, and encrypted pools that get larger every time you attach another backend.
Open OcaltioOverview
Most storage products ask you to move in. Copy files into their cloud. Abandon the NAS. Ignore the laptop under the desk. Pay again for capacity you already paid for once.
Ocaltio does the opposite. It connects the storage you already have — servers, NAS boxes, FTP hosts, S3 buckets, WebDAV, and every machine running the Ocalt client — into one surface. You browse it like a single drive. You share from it. You grow it without a migration project.
That surface is Ocaltio. The pools that scale with you are Vast Drives.
The problem we actually solve
Your files are already everywhere:
- A home NAS on the LAN
- An old FTP account from a host
- S3 or B2 for archives
- Nextcloud over WebDAV
- Laptops and desktops with free disks
- A Pi in the garage
Each one has its own client, password, path, and failure mode. “Where is that file?” becomes a scavenger hunt. Backup means *another* copy into *another* silo. Capacity means buying more of someone else’s disk while yours sits half empty.
Ocaltio does not replace those systems. It links them, indexes what you care about, and — with Vast Drives — pools them into encrypted capacity that grows when you attach more backends.
What you see: one explorer
Ocaltio is a full file manager, not a thin upload page.
- Sidebar — every place that holds bytes is a row with a live capacity meter. Click the row; you are there.
- Root & Mounted — your account’s own storage, with quotas you can see.
- Attached drives — SFTP/SSH, FTP, FTPS, S3-compatible, WebDAV, and Ocalt machines, each with its own usage bar.
- Vast Drives — named encrypted pools built from those backends.
- Shared — every link you have handed out.
- Queries — account-level usage, always visible so you know what the platform itself is spending.
The main view is deliberate: list, icons, or thumbnails; sort by name, size, modified, or kind; back, forward, up; breadcrumbs; details pane. It is meant to feel like the file manager you already trust — not a dashboard that forgot how files work.
Connecting backends
Add a drive is a short, stepped flow — type, connection, name — so only the questions that matter for that kind of host appear.
| Kind | What it is for |
|---|---|
| SSH / SFTP | NAS, VPS, Pi, any host you reach with SSH |
| FTP / FTPS | Classic hosting and older file servers |
| S3-compatible | Amazon S3, MinIO, Backblaze B2, Wasabi, and the rest of the S3 API world |
| WebDAV | Nextcloud, ownCloud, and similar |
| Ocalt machine | A laptop, desktop, or server already running the OcaltQL Client — outbound, already authenticated |
Credentials are stored encrypted and are not shown again after setup. Machines appear when the client has connected; there is nothing to dial from the browser if the client is already online.
You can open a drive, browse it, upload into it, rename, delete, compress, extract, and share — the same operations as on Root or Mounted. Cross-drive work is staged sensibly so the product does not pretend two remote hosts are the same filesystem when they are not.
Vast Drives — the product’s growth story
A Vast Drive is not a folder shortcut and not a “virtual drive” of pointers alone. It is a named, encrypted pool you create on purpose.
- Name it — “Personal pool”, “Archive”, “Client media”.
- Attach backends — any combination of the drives you already linked.
- Confirm — see combined capacity before you commit.
You can create as many Vast Drives as you need. Each has its own membership. Membership is editable later: add a new NAS to the archive pool, pull a laptop out of the personal pool, without rebuilding everything.
How placement works
When you put a file into a Vast Drive:
- The file is stored encrypted.
- It is stored whole on one attached backend (not scattered shards — clear recovery, clear accountability).
- Placement prefers capacity: backends with more free space are preferred.
- The index lives with Ocalt — so the pool stays one namespace even though the bytes sit on machines you control.
- On each machine, storage uses a uniform folder convention, so operations stay predictable.
In the UI, Vast files show an encrypted badge. The details pane shows encryption and which backend holds that file. Capacity meters for each Vast Drive reflect the sum of the backends attached to that pool — so “how big is this pool?” is a real number, not marketing.
Everyday file work
Everything a serious file manager is expected to do is present:
- Navigate with history, up, and breadcrumbs
- Multi-select, range select, cut / copy / paste between places
- Rename in place, delete with confirmation, new folder
- Upload from the toolbar or drag and drop from the desktop
- Compress and extract archives
- Preview text-like files; share others when preview is not the point
- Share a single file to a link (and QR) — listed under Shared so you can see what is out in the world
- Search from the top bar — results replace the main list, scoped under the place you are in
- List / Icons / Thumbnails — real previews for images and video
- Sort by name, size, modified, kind
- Details pane for the folder, a selection, or a single item — including Vast placement metadata
- Context menus on files, empty canvas, and drives (including “add this drive to a Vast Drive”)
This is not a subset demo of “upload and hope.” It is the full explorer loop: find, move, name, protect, share, recover context.
Security and control
- You keep the backends. Ocaltio orchestrates access; it is not “everything must live on our disk.”
- Vast contents are encrypted before they sit on attached capacity.
- Secrets for remote drives are stored encrypted and not echoed back in the UI after entry.
- Sharing is explicit — one file, one link, listed under Shared so you can see what is out in the world.
- Account queries are visible so platform usage is not a surprise.
We do not claim magic immunity from a compromised endpoint. We do claim a design where capacity is yours, pools are intentional, and encryption is the default path for Vast data.
Who it is for
- People and teams with existing hardware who refuse to double-pay for cloud copies of data that already has a home.
- Builders who already speak SFTP, S3, and WebDAV and want one pane instead of five clients.
- Anyone running the Ocalt client on machines that should contribute disk without becoming a public server.
- Organizations that need shared links, clear capacity, and pools that can be split by purpose (personal vs archive vs project) without separate products.
How adoption feels
- Sign in to Ocaltio.
- Add the backends you already trust (or install the client on a machine and add it as a drive).
- Work in Root / Mounted / individual drives as a normal explorer.
- When you want capacity that grows, create a Vast Drive, attach backends, and drop files into the pool.
- Share when you need to; search when you cannot remember the path; watch meters when you plan the next disk.
No “big bang” migration. No “all or nothing” cloud. Link → attach → grow.
One sentence
Ocaltio turns every disk you already own into one explorer — and Vast Drives turn those disks into encrypted pools that get larger every time you attach another backend.
Endless storage is not a slogan about infinite free bytes. It is a stance: stop treating last year’s NAS and this year’s bucket as separate products. Connect them. Measure them. Pool them under encryption when you want. Share on purpose. Stay in control of where the bits live.
That is Ocaltio. That is Vast Drive. Your storage, unified — and built to grow without asking you to leave home.