itsadoor safe, private, local AI in everything

Back to the whole site as text

Download

This is where you will download itsadoor and where you will find how to build your own hub. It offers no downloads yet.

With the pictures: open the page.

Not finished yet Nothing on this page can be downloaded yet. Every place where a download or a guide will be is shown as an empty slot.

What a home hub is

A home hub is the one computer in your home that keeps your house and its key. Your other devices borrow from it.

It is yours. It is not a server that we run.

The hub is also where the local AI will run, so its work happens at home.

You need one only if you want a second device, the web version in a browser, or backups. Without one, itsadoor works on one device.

Today the hub is a command-line program called itsadoor-host, not a polished installer.

Three ways to start

The app offers three ways to start. Their titles and words are the app’s own, and they are on the page Everything you can keep. This is what each one needs. Read the three ways in the app’s own words.

  1. A hub on this phone

    A phone, and nothing outside it. This is the one that has run, in the iPhone Simulator only.

    A hub on the phone itself needs nothing outside the phone for everyday work.

  2. A hub at home on a computer

    A computer at home that stays on, running the hub program.

    The hub program has been built and run on one Apple-silicon Mac and one Ubuntu x86-64 machine.

    The hub packages are for Ubuntu 24.04, on x86_64 and arm64.

    How much memory, disk and processor it needs: We have not measured this yet.

  3. A home hub and a portable hub

    The home hub of the second way, and a portable hub that goes with you. The portable hub is not built.

    The spec names a small carried computer, such as the Pi, as an example of a portable hub.

    How much memory, disk and processor it needs: We have not measured this yet.

Put it on your computer

The app is the first thing to put on a computer. A hub is a second step, for when you want another device, the web version or backups. Your home stays in a folder on your computer when you remove the app.

Mac

Mac app Will be: a disk image for Apple silicon (an unsigned test build) Not finished yet

What the computer needs

A Mac with Apple silicon, macOS 14 or later.

How much memory, disk and processor: We have not measured this yet.

What installing involves

  1. Check the file against the list of fingerprints (SHA256SUMS) that came with it.
  2. Open the disk image and drag itsadoor onto Applications.
  3. Open it. macOS will refuse, because the app is not notarized by Apple.
  4. In System Settings, under Privacy & Security, press Open Anyway beside itsadoor, and open it again.

What has been run

Built as an app. An automated test made a new home through the real storage engine, wrote a note, locked and unlocked the home, and reopened the note. It is not signed for distribution and not notarized.

The disk image mounts and holds the app. No one has opened the packaged app on a Mac.

It is an unsigned test build, and it is not notarized, so your Mac will warn you the first time.

Windows

Windows app Will be: a zip folder for 64-bit Intel or AMD (an unsigned test build) Not finished yet

What the computer needs

Windows 11 on a 64-bit Intel or AMD PC.

How much memory, disk and processor: We have not measured this yet.

What installing involves

  1. Check the file against the list of fingerprints (SHA256SUMS) that came with it.
  2. Right-click the zip, choose Properties, tick Unblock, and unzip the whole folder somewhere you own.
  3. Open itsadoor.exe. A blue window says Windows protected your PC. Press More info, then Run anyway.
  4. If Windows says a Visual C++ file is missing, install Microsoft’s Visual C++ Redistributable (x64) and open it again.

What has been run

Built as a zip file. The same automated test passed, but it ran without a real screen, so nobody has looked at the Windows app on a screen. It is unsigned and Windows will warn about it. The installer was never made.

Nothing has been installed or opened on Windows by anyone. The installer script has never been compiled.

It is an unsigned test build, so Windows will warn you.

Linux

Linux app Will be: a .deb package and an archive for Ubuntu 24.04 x86-64 (an unsigned test build) Not finished yet

What the computer needs

Ubuntu 24.04 LTS on x86-64, with GTK 3 and the drawing libraries that apt fetches.

How much memory, disk and processor: We have not measured this yet.

What installing involves

  1. Check the file against the list of fingerprints (SHA256SUMS) that came with it.
  2. Install the package with apt, which fetches any missing library. Or unpack the archive and run it, with no administrator rights.
  3. Open itsadoor from the menu, or type itsadoor.

What has been run

Built as a .deb package and an archive. The package was installed in a clean test container. The same automated test passed on a virtual screen. It has not run on a real desktop.

The package was installed with apt into a clean Ubuntu 24.04 container, and the program started there under a virtual display. It has not run on a real desktop.

It is an unsigned test build, and it is not in a signed package repository, so apt will say so.

Phones

Phones come later. Both slots are empty.

iPhone

iPhone app Will be: an app for your iPhone Not finished yet

There is no installable iPhone build.

Not yet on a real iPhone. A hub app and a Desk app have been built and run in the iPhone Simulator, and nothing has run on a physical phone.

What exists is a build for the iOS Simulator on a Mac. It runs only inside Xcode’s Simulator and will not install on a phone.

Android

Android app Will be: an app for your Android phone Not finished yet

Android 14 or later (API 34), a 64-bit Arm phone.

Not yet. Nothing has been built.

The size of phone is what the plan names. No phone app has been built for Android.

Build your own hub

If you would rather build your own hub on a small computer at home, the repository has everything below. None of it is a download. Each part says what it is for and what has been run.

A stronger computer will mean a stronger local AI. On the Beta page, the large box is the one the offer says runs a strong local AI model.

  • The hub program For: It keeps one home and serves it to your own devices over an encrypted connection. You build it from the source folder with the Rust toolchain. Run so far: Built and run on one Apple-silicon Mac and one Ubuntu x86-64 machine. Anyone with the Rust toolchain can build the hub from the source folder.The hub program has been built and run on one Apple-silicon Mac and one Ubuntu x86-64 machine.The hub listens only on this computer until you choose the network.
  • Ubuntu packages For: They put the hub on an Ubuntu computer as a service under its own user. The personal and the business hub are separate packages. Run so far: Installed in a clean x86_64 container and in a virtual machine. The arm64 packages were built and not run. The hub packages are for Ubuntu 24.04, on x86_64 and arm64.
  • The container image For: It runs the hub as a read-only container with a volume for the home. Run so far: Built and run on x86_64.
  • The virtual machine disk For: It is a disk made from the stock Ubuntu 24.04 cloud image with the hub package installed. Run so far: The personal and the business disks were booted on KVM and walked through, 45 checks each. No arm64 disk exists. The hub virtual machine disk was made with a 16 GB disk, and the build machine for it was given 2048 MiB of memory and 2 processors.
  • Bootable hub images (Ubuntu 24.04) For: A whole computer that does nothing but run the hub: for a PC with UEFI, a Raspberry Pi 5 and a Raspberry Pi Compute Module 5. Run so far: Built. The PC images booted in a virtual machine. The Pi 5 image was run only as its kernel and files in a generic arm64 virtual machine. None has ever been booted on real hardware. The images are for a PC with UEFI, a Raspberry Pi 5 and a Raspberry Pi Compute Module 5.A bootable hub image is 17.7 GB for a PC and 18.1 GB for a Raspberry Pi.To flash one you need a USB drive, SD card or NVMe drive that you are willing to erase completely.None of the images has ever been booted on real hardware.

What you would gather

To build the images you need a Linux x86_64 machine with Docker and KVM. To use one you need a PC or a Raspberry Pi and a drive to erase. How much memory and how fast a processor a hub needs is not stated anywhere. We have not measured this yet.

Building the images takes a Linux x86_64 machine with about 60 GB free disk and 8 GB free RAM.

To flash one you need a USB drive, SD card or NVMe drive that you are willing to erase completely.

Home hub program Will be: the hub program, and its Ubuntu packages Not finished yet
Guide: build your own hub Will be: a step-by-step guide to a dedicated small computer at home Not finished yet
Hub images Will be: ready-made images for a PC and a Raspberry Pi 5 Not finished yet

Build a community hub

A community hub is the separate program that runs a place you host. It is optional. Your home hub does not need it, and it is not part of the app.

It is not built. There is a written plan and a configuration file, and nothing runs.

The plan says what it must do: start closed, let people in only by your invitation, keep running after a restart, and never let anyone in just because the connection dropped.

The community hub itself is not built: no program, no package and no listener.

A community hub starts closed, and being connected does not let anyone in.

The spec’s starting limits for a community hub are 16 sessions at a time and a 512 MiB memory cap. They are starting recommendations, not measured capacity.

How much a community hub can hold in practice: We have not measured this yet.

What a place you host will be

Community hub program Will be: the separate program that runs a place you host Not finished yet
Guide: build a community hub Will be: a guide to running a place you host Not finished yet

Before you start

  • Your passphrase is the only key. There is no fingerprint, face or device keystore unlock yet.
  • The app makes and restores no backups. A backup is made by typing a command on the hub, a command-line program that has run on one Mac.
  • Nobody outside has reviewed the security of the app. Pairing, sessions, sealed storage and key handling have had no review by anyone other than their authors.
  • The app has no AI in it yet. What the local AI is being built to do.
  • Write the recovery code on paper when it is shown. It is shown once, and it is the only other way into your home.

What has been built is on What exists today.