Promptbook versus Make
When to choose Promptbook
When work needs local files and a browser on a host you manage. For example, the team can process a recording from a company folder and prepare material for several publishing channels.
When to choose Make
When you want to connect existing apps quickly with ready-made modules, such as adding a contact and creating a task after a form submission.
| Feature | Promptbook | Make |
|---|---|---|
| Self-hosting | YesYour computer or server | NoMake cloud, network connector |
| Runs with your computer off | ConditionalWhen hosted elsewhere | YesCloud scenarios |
| Where your data lives | On your host: project files with Git change history. | Scenarios and history in Make cloud; connected sources separate |
| AI models | Claude, GPT, Gemini, Qwen, … including local. Automatic choice from available models for the task. | GPT, Claude, Gemini, … depending on connection and plan |
| Scheduled tasks | YesRecurring agent tasks | YesSchedules and events |
| Integrations | Universal browser. Web apps even without a connector. | Ready-made modules, HTTP/API, MCP and custom connections |
| Passwords and credentials | Local encrypted Wallet; passwords outside the agent’s context. | Connections and keys managed in Make |
| Trust model | Zero Trust: E2E App–engine. The relay cannot read working content. | Trust in Make cloud; service permissions and encryption |
| Mobile and remote control | YesApp over E2E to your own engine | YesMake web interface; no local engine |
| AI tools and selection | Codex, Claude Code, Gemini CLI, Qwen Code, OpenCode, … Automatic choice by task and availability. | Make AI Agents and model connections in scenarios |
E2E protects the App–engine connection. External AI and services receive authorized inputs. Git keeps file history; it does not encrypt files or undo external actions. Wallet stays outside Git. Data and security ↗ Connection architecture ↗
Feature details
Self-hosting
PromptbookThe engine that runs and schedules agent work lives on your computer, company server or VPS under your control.
MakeScenarios run in Make. The Enterprise connector bridges access to supported systems on your own network.
Runs with your computer off
PromptbookClosing the controls leaves work running. Shutting down the engine host stops it. An engine on a running server can continue.
MakeService scenarios can run without your desktop. Steps through an on-premise connector need it to be available.
Where your data lives
PromptbookAgents, tasks and conversations stay in project files on your host, with an auditable Git change history. Git does not encrypt files or undo actions in external services; Wallet stays outside it.
MakeScenarios and history in Make cloud; connected sources separate
AI models
PromptbookClaude, GPT, Gemini, Qwen and other models through supported tools and extensible integrations, including local models depending on the adapter and task. You are not tied to one vendor. External models receive the inputs they need.
MakeGPT, Claude, Gemini, … depending on connection and plan
Scheduled tasks
PromptbookGive a team of agents an ongoing responsibility, goal and rules. The engine runs one-off and recurring tasks.
MakeScenarios can run on a schedule or event and use AI agents as part of the flow.
Integrations
PromptbookA universal browser operates web apps much like a person, including services without a ready-made connector or API. Capabilities depend on access, permissions and each service’s restrictions.
MakeReady-made modules, HTTP/API, MCP and custom connections
Passwords and credentials
PromptbookWallet is an encrypted credential vault on your host, separate from Git. A protected integration fills verified sign-in forms without putting passwords in the agent’s context. Protection requires keeping Wallet isolated from agent tools.
MakeConnections and keys managed in Make
Trust model
PromptbookZero Trust for the App–engine connection: working content is encrypted between endpoints, and neither the relay nor central backend decrypts it. External AI and tools receive authorized inputs; account and operational metadata remain separate.
MakeTrust in Make cloud; service permissions and encryption
Mobile and remote control
PromptbookUse the control App to assign work, follow chats and manage the project over an authenticated E2E connection to your own engine. The local Console has separate access on the engine host. Closing the App does not stop the operation.
MakeMake web interface; no local engine
AI tools and selection
PromptbookCodex, Claude Code, Gemini CLI, Qwen Code, OpenCode, GitHub Copilot, … A shared interface supports further integrations. Promptbook automatically chooses a suitable available tool and model for the task, capabilities and configured accounts, respecting your choices and limits.
MakeMake AI Agents and model connections in scenarios
Core features reviewed 10 November 2026. Integrations, models and access reviewed 11 November 2026.