# i9 Terms of Service

*Effective date: October 1, 2026*
*Last updated: October 10, 2026*

---

## 1. What i9 is

i9 is a single binary that runs virtual machines on your own computer.
It restores a Linux virtual machine from a snapshot, streams the
snapshot as the machine runs, and lets you execute commands inside it.
A running machine can be snapshotted, forked and rolled back to an
earlier instant.

The virtual machine has its own kernel and filesystem and is isolated
from the computer it runs on. i9 installs under your home directory,
needs no administrator rights, runs no background service, and requires
no account.

The only network request i9 makes on its own is fetching the virtual
machine image you ask for. Commands you run yourself (`i9 update`,
`i9 grant request`, `i9 grant renew`) contact the hosts
the privacy policy names. i9 does not host, store or publish your work.

## 2. Acceptance

These terms are an agreement between you and Kurosea, Inc., a Delaware
corporation, which operates i9 and the i9.io services ("we"); i9 and i9.io are its product.
Its postal address is on <https://i9.io/vm/contact>.

By downloading, installing, or using i9, you agree to these terms. If
you do not agree, do not use the software.

## 3. What i9 does on your machine

i9 runs with your user-level permissions. You should understand what it
does before running it:

- **Starts a virtual machine** on your computer, using the hardware
  virtualization your operating system provides: `/dev/kvm` on Linux, the
  Hypervisor framework on an Apple Silicon Mac, and Windows Hypervisor
  Platform on Windows. Without it, i9 refuses to start rather than falling
  back to something slower
- **Downloads the virtual machine image** you name, and streams it while
  the machine is already running
- **Runs commands you give it inside that machine.** You run as `dev`
  with passwordless `sudo`, so you have root in the guest. Those commands have real effect inside the guest: they can destroy its
  filesystem, and a snapshot is the only way back
- **Writes under your home directory**, in `~/.i9`: the binary, the
  images it has fetched, snapshots you take, and traces of what ran
- **Writes a scratch file per running machine under `~/.i9/scratch`**:
  the guest's writable disk, a sparse file removed when the machine stops.
  i9's per-run sockets live in `/tmp` and are removed
  with it
- **Gives the guest outbound internet access by default**, through i9's
  own user-mode NAT. The guest is not a host on your local network and
  nothing reaches into it unless you forward a port, but it can reach out.
  `i9 run --egress` restricts what it may reach
- **Sends your OS, CPU architecture and i9 version** on the first request
  of a virtual machine image fetch — no identifier of any kind
  (opt-out: `i9 config set telemetry.enabled false`)

i9 does **not** read your projects, modify your files, or send your code
anywhere. It runs a virtual machine; what happens inside it is what you
tell it to do.

**The guest is isolated, not a security boundary you should rely on for
hostile code.** It has its own kernel and filesystem and cannot see your
files, but no virtual machine is unescapable. Run code you distrust in a
machine you are willing to lose.

i9 makes no announcement on your local network, and opens no port that
your network can reach. A session started with `i9 run --session` listens
on `127.0.0.1` and is reachable from this machine only.

Run `i9 docs DATA-HANDLING` for a complete description of data handling.

## 4. Your responsibilities

You are responsible for:

- **What you run inside the virtual machine.** You run as `dev` with
  passwordless `sudo`, so you have root in the guest.
  i9 does not inspect, filter or vet the commands you run or the software
  you install there.
- **Any port you publish.** Forwarding a guest port with `i9 vm ports
  --publish` makes that service reachable from this machine: the forward
  listens on `127.0.0.1`. It reaches your network only if you forward it
  further yourself. Nothing in i9 authenticates it for you.
- **Your own backups.** Snapshots are ordinary files under `~/.i9` on this
  computer. i9 keeps no copy of them anywhere else, so deleting them,
  losing the disk or reinstalling the operating system destroys them
  permanently.
- **The images you run.** A virtual machine image is software. Run images
  from a source you trust, and check an image you download from us against
  the `blake3` digest published for it in `manifest.json`. The four i9
  binaries each publish a `.sha256` file beside them.
- **Complying with applicable laws** in your use of i9, including export
  restrictions and any licence terms attached to the software you run in
  the guest.

## 5. Code ownership

You own everything you create with i9: the contents of your virtual
machines, your snapshots, and your traces. i9 claims no rights over them,
and no rights over an `.i9io` archive — the file format a snapshot and its
trace are stored in. You grant i9 no license to your code beyond what is
necessary to operate the software on your machine.

## 6. Telemetry

When i9 streams an image from a.i9.io, the first request of that restore
carries your operating system, your CPU architecture and the i9 version.
That is all it carries.

It includes no identifier: no install id, no account, no hostname, no
username and no hardware fingerprint, and i9 stores nothing on your
machine for telemetry. i9 does keep a signing key under `~/.i9` so that
archives you create are attributable to your own installation; it is never
sent anywhere and forms no part of the beacon. We do not store your IP address and keep no location data,
user agent or identifier. Each such request writes one analytics data
point: the funnel step, which published image line it concerned, the
name of the public file if one was downloaded, your operating system, CPU
architecture and i9 version, the format it was served in, and a timestamp.
Each is from a fixed list we define, not text your machine supplies. We
read them only as counts per platform and version, and the analytics store
deletes them after its retention window. Each ranged read of a published
image writes one more data point: the image line and version, your
operating system and CPU architecture, and the byte offset and length
read. We read these only summed across all users, to learn which parts of
an image restores need. No data point carries a file or
path from your machine, a command you ran, or anything identifying you.

i9.io and a.i9.io both run on Cloudflare, which serves these pages and
the images, operates the analytics store described above, and processes
this data on our behalf as our infrastructure provider.

Because nothing identifying reaches us, there is no record of your
machine for us to disclose, correct or delete.

Turn it off with `i9 config set telemetry.enabled false`, or opt a
single invocation out with `DO_NOT_TRACK=1` in the environment.

Privacy questions, including anything you sent us explicitly:
privacy@i9.io.

## 7. Disclaimer of warranties

**i9 IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.**

i9 runs virtual machines. A machine that starts, restores or snapshots
successfully is not a representation that the software inside it is
correct, secure or fit for any particular purpose, and the isolation a
virtual machine provides is not a guarantee against escape.

## 8. Limitation of liability

**TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, KUROSEA, INC. AND ITS
OFFICERS, DIRECTORS, EMPLOYEES, AND AGENTS SHALL NOT BE LIABLE FOR
ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE
DAMAGES, INCLUDING WITHOUT LIMITATION:**

- **Anything that happens inside a virtual machine you run**, including
  the behaviour of software you install there and its use of the
  resources, network access and filesystem i9 gives it
- **Loss of revenue, data, or profits** arising from use of or
  inability to use the software

**And, to the maximum extent permitted by applicable law, Kurosea, Inc. is not
liable for these however they are characterised:**

- **Loss of a snapshot or of data in a guest**, whether from a command
  you ran, a failed restore, or deletion of `~/.i9`
- **Exposure of a service you published** from a guest to this machine,
  or to your network if you forwarded it further

Nothing in this section excludes liability that cannot be excluded under
the law that applies to you.

**Maximum aggregate liability.** Kurosea, Inc.'s total liability to you for all
claims arising out of or relating to these terms or the software is
limited to the greater of (a) the fees you paid Kurosea, Inc. in the twelve
months before the claim arose, or (b) one hundred US dollars ($100).

## 9. Acceptable use

You may not:

- Reverse engineer, decompile, or disassemble the i9 binary, except
  as permitted by applicable law
- Use i9 to develop or distribute malware or exploits, or for any purpose
  that violates law
- Forge, alter or tamper with a grant token, use one that was not issued
  to you, or otherwise work around the limits described below
- Use i9 in a manner that interferes with the a.i9.io image service, or
  redistribute the images it serves as your own service

## 10. Usage limits, grant tokens and versions

**Usage limits.** i9 runs up to 16 vCPUs of virtual machines at a time
on a machine, free of charge (each running VM counts as its vCPUs). A
grant token raises that limit for a fixed number of days. Run
`i9 grant request` for a free 7-day grant with no vCPU limit, renewable with
`i9 grant renew`. For a higher limit, email support@i9.io and we reply
with a token. See <https://i9.io/vm/pricing>.

**Grant tokens are bearer instruments.** Anyone holding one can use it, so
treat a token like a password. A token is issued for your use, we may
revoke one that is shared or misused, and we are not liable for use of a
token you disclosed.

**Versions.** Kurosea, Inc. may block specific versions that contain critical bugs
or security issues. You are not required to update, but a blocked version
will not fetch images from a.i9.io.

## 11. Termination

You may stop using i9 at any time by deleting the binary and
`~/.i9/` directory.

Kurosea, Inc. may withdraw your access to the a.i9.io image service, and revoke
a grant token, for violation of these terms. That does not affect the
binary you have installed or the images and snapshots already on your
machine: i9 needs no account and no network to run them.

## 12. Changes to these terms

Kurosea, Inc. may update these terms. The current text is always the one served
at <https://i9.io/terms>, and each release carries the text that was
current when it was built, readable offline with `i9 docs`. Continued use after
changes constitutes acceptance.

## 13. Governing law

These terms are governed by the laws of the State of Utah, USA, without
regard to its conflict-of-laws rules. The state and federal courts in
Salt Lake County, Utah have exclusive jurisdiction, and you and Kurosea, Inc.
each consent to venue there.

## 14. Contact

Support: support@i9.io

Legal notices: legal@i9.io

Privacy: privacy@i9.io

Security reports: security@i9.io (<https://i9.io/vm/security>)

Who we are and our postal address: <https://i9.io/vm/contact>
