BYO vs Hosted Onboard

Onboard 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.

ModePriceWhat Bootstrapware stores
Local / demoFree foreverNothing, createLocalAdapter
BYO$9.99 / workspace / moFlow config only. You implement an OnboardAdapter; progress stays on your backend.
Hosted$19.99 / workspace / moConfig + progress records + integration-reported summaries (opaque ids, step keys, revisions, timestamps — not host context).

Live entitlements

CallRequirement
Test keys (bsw_test_*)No paid Onboard entitlement
Live config fetchBYO ($9.99) or Hosted ($19.99)
Live Hosted progress writesHosted ($19.99) plus authorToken from your BFF

Publishing a flow 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.

When to choose BYO

  • You already have (or want) progress in your database.
  • Compliance prefers customer-owned progress records.
  • You will wire your own notifications from onEvent.

Implement the OnboardAdapter. Bootstrapware webhooks for progress do not fire for your store. Still pass flowId + publishable key so published items load.

When to choose Hosted

  • You want progress and summaries without building the store.
  • You accept Hosted records (ids, keys, timestamps) and customer export/delete responsibility.
  • You want id-only Hosted webhooks.

Cancel Hosted: writes freeze immediately; dashboard JSON export for 30 days; then Hosted progress and summaries are deleted. Hosted → BYO keeps data; there is no 30-day clock.

Resolve order

  1. Progress: if adapter is passed → use it (BYO or local). Else if flowId and publishableKey are set → Hosted. Else → createLocalAdapter.
  2. Config: whenever flowId and publishableKey are set, published config still loads (Path C).

More detail: Modes.

Related: Modes · Adapter · Environments · Privacy · Pricing