ixi cloud from the app

ixi Local needs no account. When you want one, it can reach ixi Cloud: sign in, upload a project so you can share it, or copy a cloud project onto this Mac to work on it offline. Each transfer is a one-time copy, not a sync.

sign in

1. In the menu bar choose Customize → Customize ixi…, then ixi Cloud under ixi in the sidebar. The card starts with "Optional. Everything on this Mac works without an account."
2. Press Sign in to ixi Cloud…. Your browser opens ixi Cloud. Sign in there if you aren't already.
3. ixi Cloud shows Connect an app to ixi. Check what it says: access goes to an address on this computer ("An app on this computer."), the app calls itself ixi Desktop, and the list of what it can do ends with "Copy whole projects in and out of your orgs, and delete a project after moving it". Press Approve.
4. The browser tab says Signed in to ixi Cloud: "You can close this tab and return to the ixi app." The panel shows Signed in as and your email.

ixi waits 5 minutes for the browser; Cancel stops waiting. The sign-in is kept in your Keychain, and nothing on the app's own pages ever sees it.

Approving lets ixi Desktop act as you in ixi Cloud, as the page lists: read what your account can see, create and edit nodes, run models, processes and pipelines (runs spend your organization's credits), and copy projects in and out of your organizations. To disconnect it, go to Organization settings → API keys in ixi Cloud.

Open ixi Cloud opens ixi Cloud in a window of its own. That window signs in to ixi Cloud separately, as a browser would. Sign out removes the sign-in from this Mac and stops any transfer that's running.

upload a project

From the canvas:

1. Open the canvas menu → Share…. Under Sharing — available in ixi Cloud, press Upload to ixi Cloud to share. The page says "Confirm the upload in the dialog ixi shows."
2. If you aren't signed in, ixi asks Sign in to ixi Cloud to share. Press Sign In… and sign in as above.
3. If you're in more than one organization, ixi asks which one: "Upload “…” to which organization?", with a button for each (up to six), and "Everyone in the organization you choose will see it and can edit it."
4. ixi asks "Upload “…” to … in ixi Cloud?": "A copy goes to ixi Cloud, where everyone in … will see it and can edit it. Its files are uploaded to ixi Cloud storage. Your keys and connectors stay on this Mac." Tick Remove it from this Mac once the cloud copy is verified (move) to move it instead of copying. Press Upload.
5. When it's done, ixi says "“…” is in ixi Cloud". Open in ixi Cloud opens the copy, where Share… works as it does in the browser.

Nothing uploads until you confirm in ixi's own dialog: the canvas page can ask, but it can't start an upload or choose where it goes.

From the panel: This Mac lists your projects. Press Upload to cloud… on one and pick the organization. The form says "Everyone in … will see it and can edit it in ixi Cloud." Tick the move box if you want it, and press Upload. When it's done, Open in ixi Cloud to share opens it.

Everyone in the organization you upload to sees the project and can edit it, as with a project made in ixi Cloud. That holds for every canvas in it, including ones you made private on this Mac. To share it further, or to make it private, use Share… in ixi Cloud.

	what happens
copy (the default)	the project stays on this Mac, and ixi Cloud gets a copy
move	after the upload, ixi reads the cloud copy back and checks that every file is there. Only then does it remove the project from this Mac. If the check fails, or you cancel, the project stays on this Mac

make a project available offline

Signed in, the panel lists each of your organizations with your role. Press Show projects to list its projects:

• Open opens the project in an ixi Cloud window.
• Make available offline copies it onto this Mac, where it shows up under This Mac and on your dashboard. It works offline from then on.

The cloud original stays where it is: this is always a copy, never a move.

transfers

The Transfers card shows every upload and download: what it is (Upload, Move to cloud or Make available offline), its step (Preparing…, Checking what is already there…, Sending files…, Saving…, Verifying the copy…, Removing the original…, Done), and how many files and megabytes have gone. Cancel stops one; Dismiss clears one that has finished.

Files the other side already has are never sent twice. A file over 90 MiB goes in pieces, and if the connection drops, only the pieces that hadn't arrived are sent again. A transfer you start again after a cancel or a failure sends again every file the other side hadn't saved yet.

Already there means the other side has this project already, from an earlier transfer. A transfer never writes over it. Import as a copy makes a second, separate project with new ids. That's also the way to bring a project over again after you've changed it.

what travels

A transfer takes the project and every canvas it owns:

• nested canvases, process canvases, and the workspaces of sandbox, 3D and composer nodes;
• the 10 newest versions of each canvas, always including the current one;
• files and media, and each node's generation history;
• tables and their rows;
• pixie chats and the pixie inbox;
• process runs, which arrive idle, and pipeline sessions, which arrive stopped if they were running;
• 3D checkpoints.

These stay behind:

• keys, connectors and secrets, always, in both directions. Your keys never leave this Mac, and an ixi Cloud organization's secrets never come down to it. ixi Cloud runs on its own keys and your organization's credits;
• terminal pixie settings and sessions, always. On the other side the pixie is an ixi pixie again;
• approvals. One given before the move doesn't carry over: "This approval was given before the project moved and does not carry over — ask again.";
• sharing. People you shared with don't come along. In ixi Cloud the copy belongs to you, and everyone in the organization you chose sees it. On this Mac it's private;
• canvases the project only links to: ones another canvas owns, ones in another organization, and ones you can only view;
• older versions, anything that was mid-run, and 3D variants you hadn't promoted.

limits & good to know

• Big files go in pieces. A file over 90 MiB moves in 64 MiB pieces, both ways, and a file can be up to 5 GiB. The file appears on the other side only once every piece has arrived and the whole file checks out.
• A project holds up to 2,000 canvases and 50,000 files for a transfer.
• Uploads count toward your organization's storage in ixi Cloud. ixi checks there's room for the whole project before it sends anything, and checks again before each big file. When it's full, the upload is refused; see billing limits. An upload counts once, when it's saved, however many times a piece was sent.
• One transfer per project at a time.
• Signing out can't cancel the sign-in on ixi Cloud's side yet. It stops working by itself within 7 days. To end it sooner, disconnect it under Organization settings → API keys.
• Nothing leaves this Mac by itself. Projects upload only when you press Upload.

related

• ixi local: what stays on this Mac and what lives in ixi Cloud.
• sharing: who can see a canvas in ixi Cloud.
• terminal pixies: pixies on your own Claude Code, which never leave this Mac.