Galpi

Where VMs run

Choose whether the per-chat VMs run on Fly Sprites, E2B nodes or Sysbox nodes, join nodes, and set VM sizes.

One choice for the whole deployment, made in the wizard's VM step or System admin → Settings → Where VMs run; the environment variable is VM_PROVIDER.

Choice VM_PROVIDER What it is
Fly Sprites sprites Fly.io runs the VMs; no servers of your own. Needs SPRITES_TOKEN and SPRITES_ORG
E2B nodes e2b Servers with KVM joined as nodes with the one-line join command in System admin → Nodes
Sysbox nodes sysbox Servers without KVM joined as nodes; VMs are Sysbox containers. Only for deployments whose users trust one another
Local local Development: folders on this computer act as VMs. Refused in production
Not chosen yet none (default) Chats get no VM

Joining a node

  1. System admin → Nodes → Add node gives a join command with a single-use token.
  2. Run it as root on the server that will be the node. It downloads the node software (node-kit/) from Galpi, installs itself and joins. Galpi never takes a root password or SSH key.
  3. Nodes, and the Galpi server, talk over a WireGuard private network (10.77.0.0/24). Galpi connects out to the nodes, so no UDP port needs opening on Galpi's side; nodes behind NAT go through a node with a public IP.
  • A joining node's location is looked up from its address and a region suggested; regions only steer GeoDNS for preview addresses.
  • E2B upgrades run one node at a time, on the node (stop new VMs → sleep → switch version → check → roll back on failure).
  • Limits (memory, concurrent VMs) can be overridden per node. Ongoing node problems are mailed and sent by webhook to administrators (at most every six hours).

When you change it

  • Saved values apply after a restart. Moving to E2B or Sysbox needs a node of that kind joined first.
  • With chats that have VMs, a confirmation comes first. Running programs are lost (dev servers and previews start again).
  • Chats move on their next question; chats idle for over ten minutes move a few at a time every minute, from a fresh copy restored at the new place. Conversations stay. Keep the old place's settings (Sprites token, node list) until everything has moved.

VM sizes (E2B nodes)

Set in System admin → Settings → VM sizes. A project owner picks a size up to the system maximum in Project settings → Preview → Workspace size; people don't pick sizes per chat.

Size Default
S 2 vCPU, 2 GiB, 10 GiB disk
M 4 vCPU, 4 GiB, 10 GiB disk (default)
L 8 vCPU, 8 GiB, 20 GiB disk (default maximum)
XL 8 vCPU, 16 GiB, 40 GiB disk

Chats without a project always use the system default. On Sprites sizes are fixed, so the setting isn't shown.

Sysbox nodes

VMs on Sysbox nodes share the node's kernel, a weaker isolation than E2B's Firecracker VMs. Galpi shows the trade-offs and asks before you choose them. Use them only where users trust one another.

Esc