Odile

Questions

Your own computer, with an agent inside it. A real Linux machine, not a chat window.

The short version

The three gaps we state before anyone asks

  1. The app layer is not hardware-measured yet. Measured boot covers firmware, kernel, initramfs and command line. Hermes, the installer and the skills are pinned by a signed manifest and a published hash, but the CPU does not measure them. The installer is signed, inspectable and audited at handoff for keys, passwords and keyslots; only a measured image can prove there is no hidden backdoor. The manifest records the machine as provisioned; anything you install afterwards is yours.
  2. The console passes through the host. Serial and VNC can be watched. Never type a secret there; the sign-in goes over TLS to the guest, after the report checks out.
  3. Odile keeps three powers. We can stop or delete the machine (availability, not confidentiality); we control DNS for your slug (pin the certificate fingerprint in your recovery file — the one your machine first served; a renewal changes it) and we can set a different boot image from the panel (detectable via the measurement — compare it to the one in your ready email before you set your sign-in).

Check the machine before you trust it: the verify page shows PASS or FAIL, and you set your sign-in only after PASS.

The boot key and the sign-in

What is the boot key?
A public key in the measured command line whose private half was thrown away. It is plumbing, not a credential.
What is the Odile sign-in?
The username and password that open your workspace. You set it on your machine at first visit, and it is hashed there; we never see it. A lost sign-in is reset with your recovery code.
Do I need the boot key?
No. You never see it. The boot is sealed; your sign-in is the only thing you set.
Can Odile log in to my machine?
No. There is no user key and no private key for us to hold, no root password, no disk passphrase.
Can you reset my sign-in or unlock my disk?
No. There is no escrow and no passphrase. A lost sign-in is reset on the machine with your recovery code; if the disk will not open, the machine is rebuilt and you restore from your backup.
A recovery code and a recovery file are the way back: the code resets your sign-in, the file opens your backup. Your first visit gives you both; keep them off the machine. While the machine is still running, the agent can show it again.

Reboots and failures

What happens after a reboot?
It starts itself. A repeating job — the morning brief, a watchdog — runs when the machine comes back up if it was due while it was down.
What happens if the machine dies?
We rebuild it; you ask the agent to restore last night's backup with your recovery file — the one you downloaded on your first visit. If the machine is still running and you lost your copy, ask the agent to show you the file. Target under an hour; your last day may be lost. The drill is practiced before you get a machine.
Can I install anything?
Yes. It is a Debian machine and you are root.

Support

Can you fix something for me?

Ask the agent to run odile-diag and email the bundle to help@odile.fyi. If that is not enough, ask it to run odile-support grant --hours 24; it prints the expiry and the revoke command, and every session is logged.

A grant is a handover: it can read the mounted disk, every file, the agent's memory and past prompts, the sign-in hash, and the backup password if the recovery file is still on the machine. Expiry and revoke block new logins; an open session keeps running until it exits. A root shell can add a keyslot, copy the volume key, or leave a service behind, so ask the agent to check authorized_keys, cryptsetup luksDump and crontab -l after revoke. The grant log is written on the machine; a root shell can edit it.

Place and data

Where is the machine?
The machine is in Montreal, Canada.
What do you store?
We store your email address, your payment record at Stripe, and the metadata needed to run your machine. At HQ we hold the boot key with no private half, a hash of your setup token, and the record of your machine.
Do you track me?
No cookies, no trackers, no third-party requests.
Where does the model run?
In NEAR AI's confidential cloud, in a hardware enclave. Your prompts go from your machine to the enclave. They do not pass through Odile's servers.

When it opens

The waitlist hears first.

Back to the list