Sync, sharing, and iOS

Intabula has no server and no account. A vault is a folder, and whatever syncs that folder syncs the vault. Keep the vault in iCloud Drive and the iOS app opens it on your phone.

Syncing a vault

Because the vault is plain files, anything that moves folders syncs it: iCloud Drive, Dropbox, Syncthing, Git, a network share. No Intabula server sits in between, and there is nothing to sign into.

The iOS app

The Intabula iOS app opens the vault on your phone with full-text search, table and Kanban views, creating and editing records with a live-preview Markdown editor, drafts, backlinks, the needs-attention inbox, external collections, and widgets.

The agent on iOS

The iOS app has its own agent in the Agent tab. It runs on the phone and uses OpenRouter with an API key you enter in its settings. The key is kept in the iOS Keychain on that device only and does not sync through iCloud Keychain. Conversations are stored on the phone, outside the vault.

It has auto and manual modes like the desktop agent, and in manual mode each write waits for your approval. Its operations are a subset of the desktop's: it can search, query, and read records, schemas, backlinks, the needs-attention inbox, and drafts. It can create, update, move, and delete records, create collections, and update, discard, or save drafts. OpenRouter's web search is on by default and can be turned off in settings.

These stay on the Mac: the Claude and Codex providers, linked folders and the Git tools, fetch_url, bots, saved views, renaming records, and pinning fields. Encrypted collections are not available to the phone's agent.

External collections

An external collection works like any other writable collection (schema, views, agent writes, the inbox), but its folder lives outside the vault: in iCloud Drive, on an external disk, or on a synced share. (Contrast with a linked folder, which is read-only agent context.)

Sharing a collection

To share a collection, share its folder. Example: create a Groceries folder in iCloud Drive, share it with your partner through the OS, and add it to Intabula as an external collection. They set status: got at the store and the change syncs back to you. The collection's schema travels in a dotfile inside the folder, so everyone opening it gets the same columns.

The operating system handles sharing and permissions. Intabula has no invite flows, seats, or per-user pricing. When the project is done, delete the folder.