BYO vs Hosted Chat
Chat has its own ladder, not Importer's single $19.99 production tier. Pick the storage model that matches your risk and ops appetite, then match publishable keys and entitlements.
| Mode | Price | What Bootstrapware stores |
|---|---|---|
| Local / demo | Free forever | Nothing, createLocalAdapter |
| BYO | $9.99 / workspace / mo | App config only. You implement a ChatAdapter; messages stay on your backend. |
| Hosted | $19.99 / workspace / mo | Config + messages + files (1 GB included). You moderate in the dashboard. |
Live entitlements
| Call | Requirement |
|---|---|
Test keys (bsw_test_*) | No paid Chat entitlement |
| Live config fetch | BYO ($9.99) or Hosted ($19.99) |
| Live Hosted messages / files | Hosted ($19.99) only |
Publishing an app stores config. It does not skip live entitlement checks. Optional Chat storage add-on ($9.99) raises Hosted files from 1 GB to 10 GB and is not stack-discounted. Stack discount (2nd product 25% off that product's list, 3rd+ 35%) is company-wide, see pricing.
When BYO is the right default
- You cannot store customer messages or files on Bootstrapware
- You already have Postgres / object storage and want RLS
- You need retention rules Bootstrapware Hosted does not offer
Implement the ChatAdapter on your API. Re-bind authorship from the session.
When Hosted is enough
- You want SSE, inbox, and storage without a BYO backend
- You accept moderating plain text and files yourself
- 1 GB (or 10 GB with the add-on) covers your attachment story
Cancel Hosted: freeze writes, export 30 days, then delete. Guide: moderate Hosted.