Pricing
Four tiers, one protocol. Everything speaks iSCSI over the internet — what changes is how much you can write, how long sessions live, and whether they survive a disconnect.
Anonymous
Free
Zero-setup iSCSI. No account.
Connect to a public target with `iscsiadm` and go. Each TCP connection is its own ephemeral session; writes are kept in a temporary overlay and discarded on disconnect.
- Write limit
- 64.0 MB
- Session TTL
- 4h
- Concurrent sessions
- 3
- Persistent
- no
- SCSI-3 reservations
- no
- Multi-LUN targets
- no
- Stored images
- —
- Bandwidth floor
- 50 Mbit/s
Free
Free
A little more room. Still no money.
Register with an email and get a bigger write budget plus a longer session TTL. Sessions still vanish at the end of their window — no persistent storage.
- Write limit
- 256.0 MB
- Session TTL
- 1d
- Concurrent sessions
- 3
- Persistent
- no
- SCSI-3 reservations
- no
- Multi-LUN targets
- no
- Stored images
- —
- Bandwidth floor
- 50 Mbit/s
Identified
$5/mo
Real work, with a shelf life.
Persistent sessions across disconnects and BEAM restarts, larger disks, included storage for images you upload, and SCSI-3 Persistent Reservations — the cluster-fencing primitive Pacemaker / ESXi HA / Windows MSCS expect from shared storage. Good for personal labs, rescue images, dev VMs, and a 2-node home failover cluster.
- Write limit
- 2.0 GB
- Session TTL
- 30d
- Concurrent sessions
- 5
- Persistent
- yes
- SCSI-3 reservations
- yes
- Multi-LUN targets
- yes
- Stored images
- 1.0 GB
- Bandwidth floor
- 100 Mbit/s
Commercial
$25/mo
CI pipelines, fleets, serious throughput.
Enough concurrent sessions to back a CI fleet, large per-session write limits, headroom on included storage, and the same SCSI-3 PR support as Identified for production cluster software. SLA and invoicing available — email sales.
- Write limit
- 50.0 GB
- Session TTL
- 30d
- Concurrent sessions
- 20
- Persistent
- yes
- SCSI-3 reservations
- yes
- Multi-LUN targets
- yes
- Stored images
- 100.0 GB
- Bandwidth floor
- 100 Mbit/s
Details, in plain terms
Write limit is the total bytes a session can write before it stops accepting more. Reads are always unconstrained — only writes count against the quota. The limit is per-session, not per-month.
Session TTL is how long a session can sit suspended (no active initiator) before the Janitor evicts it. For non-persistent tiers, the session also ends the moment the last TCP connection closes.
Persistent means the overlay survives disconnects and BEAM restarts. Reconnecting from a different host, a rebooted machine, or after a server upgrade finds the same disk state waiting.
SCSI-3 reservations are the cluster-fencing primitive Pacemaker, ESXi HA, and Windows MSCS use to keep two nodes from corrupting shared storage. Paid sessions support the full SPC-4 PR path — REGISTER, RESERVE, RELEASE, PREEMPT — and the state survives target restarts because it lives in Postgres, not just in process memory. The I_T nexus is identified by iSCSI InitiatorName, so two nodes sharing CHAP credentials are still distinct holders. Drive it with sg_persist from the
sg3-utils
package.
Multi-LUN targets let one iSCSI session expose several block devices, addressed by SCSI LUN number. Paid tiers can provision multi-LUN sessions via POST /api/sessions with {"images": ["a", "b", ...]}; the session shows up to the initiator with sequentially-numbered LUNs (0, 1, …). Free tiers can still hit the anonymous demo at iqn.2025-01.pub.scsipub:multi to see the shape — it's two LUNs from the public catalog stitched together.
Stored images is the budget for images you upload yourself. The public catalog is free for everyone on every tier. Uploads use the JSON API — see the
API reference
for the POST /api/images contract.
Bandwidth floor is the guaranteed throughput per tier bucket during congestion. Idle capacity above the floor is shared across all sessions.
Need higher limits, a dedicated host, an SLA, or an annual invoice? Email sales.