Setup guide

BYO vs Hosted

Both modes use the same widget and the same published app config. The difference is where RFQ records live and which plan live writes need. Attachment bytes stay on the host in both paid modes.

ModePriceWhat Bootstrapware stores
Local / demoFree foreverNothing. createLocalAdapter stays in the browser.
BYO$9.99 / workspace / moApp config only. You implement an RfqAdapter. RFQs, quotes, clarifications, and decisions stay on your backend.
Hosted$19.99 / workspace / moConfig plus structured RFQ, quote, clarification, and decision records. Attachment bytes stay on the host and do not count toward the 1 GiB cap.

Live entitlements

CallRequirement
Test keys (bsw_test_*)No paid RFQ entitlement
Live config fetchBYO ($9.99) or Hosted ($19.99)
Live Hosted writesHosted ($19.99) plus a server-minted author token

Publishing an app stores config. It does not skip live entitlement checks. Stack discount (2nd product 25% off that product's list, 3rd+ 35%) is company-wide. See pricing. Stripe env names are STRIPE_PRICE_RFQ_BYO and STRIPE_PRICE_RFQ_HOSTED. This site does not invent Stripe price IDs.

When to choose BYO

  • You already have (or want) RFQ records in your database.
  • Compliance prefers customer-owned quote and decision rows.
  • You will wire your own notifications from host callbacks.

Implement the RfqAdapter or follow the persisted BYO guide. Bootstrapware does not see titles, quotes, or prices.

When to choose Hosted

  • You want structured RFQ state without building the store.
  • You accept Hosted records and customer export/delete responsibility.
  • You want id-only Hosted webhooks.

Cancel Hosted: writes freeze immediately; dashboard JSON export for 30 days; then Hosted RFQ records are deleted. Hosted → BYO keeps the rows; there is no 30-day clock. Files never leave the host.

Hosted setup is the token route plus appId and the publishable key. Connect MCP from RFQ with Cursor.

Related: Modes · Adapter · Privacy by mode · Privacy · Pricing