Plexon Nous
on a Machine of Your Own

Plexon Nous is the part of Plexon that runs your workflows, bots and boards, kept on a machine that does not get closed at night. On the Nous box it is already on. On a spare computer with Plexon installed, one switch does it: Settings, This computer, "Let my other computers connect to this one". It then shows a six-digit code for the other computer to type. A box with no screen (a Linux service, a container) has a short setup guide for whoever looks after it.

• Already on, on the Nous box
• One switch on a spare computer; a Linux service and a container image for a box with no screen
• Comes back after a reboot with nobody logged in

Settings, This computer, Plexon Nous lists the computers on your account that are ready, with when each was last seen and whether it can be reached from here. Pick one, type the six-digit code it shows, and the app connects and restarts onto it. The code is good for five minutes and one use; three wrong tries cancel it. Across a network the connection is encrypted with that machine's own certificate, and the key the app keeps for it lives in the operating system's keystore. A machine set up from the command line is added with Enter by hand instead.

• Your computers listed by name, a six-digit code to pair
• Pinned to that machine's own certificate, never a certificate authority
• Nothing to type for a computer on your account; Enter by hand for one set up by hand
• Switch to the local computer brings the app back

Everything that runs on a timer or answers a message keeps going on Plexon Nous: schedules, Gmail and WhatsApp reply handling, Telegram and Slack bots, dashboard refresh. Open the app on the laptop later and the runs are there.

• Schedules and polls fire on Plexon Nous
• Reply workflows answer Gmail and WhatsApp there
• Telegram and Slack bots answer from there
• Boards refresh on their timers and show fresh numbers when you open them

When you connect, the app asks the signed-in Plexon on your laptop for a device grant and hands it to Plexon Nous. It then signs in on your account's device seat, not yours: switching back does not sign it out and it does not sign you out. It appears under Devices on your account page, where Revoke signs it out.

• One grant per machine, listed under Devices
• Revoke from the account page; its automations stop until it is paired again
• Your own sign-in is untouched

The app talks to one Plexon at a time, this computer's or Plexon Nous. While it is pointed at Plexon Nous, the workspace is that machine's folder. A file you attach is uploaded there and the model reads it there; images and documents the app shows are read from that machine; a connector sign-in still opens in your laptop's browser and completes on Plexon Nous.

• Attachments upload to the Nous workspace
• Open and Reveal say where the file is instead of failing
• Connector sign-ins finish through your own browser

While the app is connected to it, every folder is that machine's. Browse shows its disk, New folder makes one, New workspace finishes on it, and Send a folder copies a folder from your computer to it, up to 1 GB a send.

• Browse, New folder and New workspace work on its disk
• Send a folder: node_modules and build output stay behind unless you keep them

Moving a workflow you built on the laptop to Plexon Nous, with everything it depends on, is planned as an export and import; no date is promised. If you have no machine to leave on, Plexon Nous Cloud is the same thing run by Plexon, turned on from the same Settings tab, and part of Premium.

• No moving a workflow between the two yet; build it where the app is connected
• No machine to leave on: Plexon Nous Cloud, part of Premium