---
title: "Run Paperclip AI on a Sprite"
description: "Paperclip is an open-source orchestration platform for creating teams of AI agents that operate like a company with goals and autonomous execution. This guide shows how to run it on a Sprite, a hardware-isolated Linux environment with 100GB storage, a TLS URL, and a pause/resume lifecycle that charges only for compute in use. Setup requires creating a Sprite, running npx paperclipai onboard -y to accept defaults like embedded PostgreSQL and local storage, then editing the config to bind to 0.0.0.0 in authenticated mode. The Sprite’s hostname must be added to Paperclip’s allowlist with npx paperclipai allowed-hostname to avoid an error, and the service registered via sprite-env services create before accessing the dashboard through the Sprite’s URL. Sprites provide checkpoints for rollback, automatic pausing when idle, hardware isolation to contain agent actions, and network policy to restrict HTTP access to allowed domains."
---

# Run Paperclip AI on a Sprite

[Fly.io](https://yomu.fyi/company/fly-io) · Nov 6, 2026

**Type:** Tutorial

## Summary

Paperclip is an open-source orchestration platform for creating teams of AI agents that operate like a company with goals and autonomous execution. This guide shows how to run it on a Sprite, a hardware-isolated Linux environment with 100GB storage, a TLS URL, and a pause/resume lifecycle that charges only for compute in use. Setup requires creating a Sprite, running npx paperclipai onboard -y to accept defaults like embedded PostgreSQL and local storage, then editing the config to bind to 0.0.0.0 in authenticated mode. The Sprite’s hostname must be added to Paperclip’s allowlist with npx paperclipai allowed-hostname to avoid an error, and the service registered via sprite-env services create before accessing the dashboard through the Sprite’s URL. Sprites provide checkpoints for rollback, automatic pausing when idle, hardware isolation to contain agent actions, and network policy to restrict HTTP access to allowed domains.

## Context

Paperclip is an open-source orchestration platform for creating teams of AI agents that operate like a company with org charts, goals, and autonomous execution. Running it locally requires hardware that may be scarce, so the post demonstrates how to deploy it on a Sprite, a hardware-isolated Linux environment with features like checkpoints, pause/resume, and network policy.

## Approach / What changed

Create a Sprite with sprite create paperclip , install Paperclip using npx paperclipai onboard -y to accept defaults (embedded PostgreSQL, local file storage, port 3100), edit the config to set deploymentMode to authenticated and host to 0.0.0.0, add the Sprite’s hostname to Paperclip’s allowlist with npx paperclipai allowed-hostname , register the service with sprite-env services create specifying the npx path and port 3100, restart the service, and access the dashboard via the Sprite’s TLS URL.

## Takeaways

- Paperclip requires its hostname to be in an allowlist; otherwise it returns a “hostname not allowed” error and refuses to serve the UI.
- Sprites provide hardware isolation, not just container isolation, so agent actions cannot affect other systems even if compromised.
- Sprites automatically pause when idle, reducing costs, and support checkpoints for instant rollback of the entire environment including database and config.

## FAQ

### How do I fix the 'This hostname is not allowed' error?

Add the Sprite's hostname to Paperclip's allowlist using \`npx paperclipai allowed-hostname <hostname>\` (without https://), then restart the service with \`sprite-env services restart paperclip\`. The hostname must be on the allowlist for Paperclip to respond.

### How do I make the Paperclip dashboard accessible from anywhere?

Change the config to bind to 0.0.0.0 in authenticated mode, add the hostname to the allowlist, and register the service. Optionally set the Sprite URL to public auth with \`sprite url update --auth public\` so that Paperclip's own auth layer protects the dashboard.

### What features does a Sprite offer for running AI agents?

Sprites offer checkpoints for instant rollback of the entire environment, automatic pause/resume to save costs when idle, hardware isolation that prevents agent actions from affecting other systems, and network policy to restrict agent HTTP access to allowed domains.

**Tags:** [AI Agents](https://yomu.fyi/topic/ai-agents), [Open Source](https://yomu.fyi/topic/open-source), [Orchestration](https://yomu.fyi/topic/orchestration), [Paperclip](https://yomu.fyi/topic/paperclip), [Sprite](https://yomu.fyi/topic/sprite)

- Source: [Fly.io](https://fly.io/blog/paperclip-on-a-sprite)
- Source URL: https://fly.io/blog/paperclip-on-a-sprite
- Ingested by Yomu: 2026-11-06T18:00:21.125Z

[Read original post](https://fly.io/blog/paperclip-on-a-sprite)
