OctoberListCalendar
SMTWTFS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
4 ready3 with a post date
Plan an Instagram grid from a board, then switch between list and calendar views.
App gallery
Start from an example
Real hosted apps people built on Playbook boards. Open one, or copy its starter prompt and make your own.
For studios and teams
Your workflow, minus the busywork
Everyone has a workflow no off-the-shelf tool quite fits. Describe yours once, and it runs on top of Playbook after.
Playbook MCP connectedAcme workspaceOne prompt
› Build an intake form for the retail partners we invite to the Partner submissions board. Require SKU, region and usage rights on every upload.
●playbook.list_custom_fields()
●Write index.html, form.js
✓Live at partner-intake.playbookapps.cloud
Lands inPartner submissionsOpen toInvited partners
- Follows your permissionsApps open to anyone with the link, behind a password, or only to your workspace.
- Lands where you chooseUploads go straight into the board you name, ready for review.
- No servers or IT ticketsPlaybook hosts every app at its own link. Nothing to set up or maintain.
- Off in one clickChange who can open an app or delete it anytime. Your assets stay in Playbook.
What you get
Everything your app needs
Hosting, access, search and uploads come with every app, on top of the board you already have.
Your board is the database
Add a photo in Playbook and the app shows it.
your-app.playbookapps.cloud
Anyone with the link
You choose who gets in
Public link, password, or workspace only.
Search that understands
Visitors find work by describing it.
Collect uploads and feedback
Clients drop files in, your team approves.
Live in minutes, no servers
Its own link, no hosting or keys to manage.
Works with your agent
Claude, ChatGPT or Cursor deploy it over MCP.
Frequently asked questions
What’s a hosted app?
A customizable web app connected to a Playbook workspace and deployed at its own playbookapps.cloud address.
No. Connect an AI agent like Claude, ChatGPT or Cursor to Playbook and describe the app you want. It writes the files and deploys them for you. If you’d rather write it yourself, an app is a few plain static files with no build step. See the hosted apps guide.
Every asset on the board and its sub-boards, with previews, colors, tags, statuses, custom fields and who uploaded them. It can also run keyword and AI search inside the board. It can’t see anything outside that board.
You choose: anyone with the link, anyone with a password, or only people who can view the board in Playbook. You can switch at any time, and the change takes effect within about a minute, with no rebuild.
Yes, when the board’s share link allows uploads. Files go straight into the board. In an app open only to your workspace, signed-in teammates can also edit titles, statuses, fields and tags, approve assets and leave comments.
Yes. Teams use hosted apps for partner intake forms, asset finders open only to one team, and exports in their company’s sizes. Describe the workflow in one prompt and the app runs on the boards, fields and permissions you already have in Playbook.
Yes. Write to [email protected] with the app and the domain you want, such as gallery.yourcompany.com. You add two DNS records, we connect it, and the app’s playbookapps.cloud address forwards there. See your own domain.
In Playbook. An app has no database of its own: it reads the board each time, so adding or editing an asset in Playbook updates the app within a few minutes.
It depends on your Playbook plan (see pricing). Updating an app you already have always works, even if you’re at your limit.
Playbook API is the file layer for the app you're building. Your app uploads, processes, stores and delivers images, video and documents through one API. It's powered by the same platform managing over 400 million visual assets.
One API and one key cover uploads, image delivery, video streaming and storage. Every file is accessible through your workspace, where your team can search, comment on, approve and share it without you building an admin panel, and your coding agent can manage the same files through MCP.
Yes. Large files go up in parts through signed uploads, straight from the browser to storage, so they never pass through your server. You can send up to 100 files in one batch.
It's stored once. Playbook checks the contents of every upload, and a file with identical bytes merges into the asset that's already there instead of creating a copy. For AI-generated variants you want to keep separate, mark the upload as ai_generated and merging is switched off.
Keep your S3, GCS or R2 bucket as the primary store, and Playbook processes, searches and delivers on top of it. If you're moving from another provider, send up to 100 files URLs per call and Playbook fetches them in the background.
Not for your coding agent. It signs in to Playbook with your account the first time it connects. Your app's server uses an API key, which you create in the Playbook app with no approval needs.
Files are encrypted at rest, and anything that leaves Playbook goes through signed links that expire. Your team signs in with SSO, accounts are managed through SCIM, and every action is recorded in audit log.