Build vs buy
Build resource discussions yourself vs buy Bootstrapware
The host already has users, tenants, and records. A team can build a thread list, a composer, and a table. The honest question is who keeps the edge cases.
What a finished version includes
- Resource-scoped threads and flat replies
- Host-minted authorization, not a page URL
- Mentions that do not grant access
- Per-user read state
- Resolve and reopen with a version check
- Cursor pagination
- Edit, delete, and tombstones
- Export
- Host theme
- Ongoing docs and dependency maintenance
Those items match the Comments product. They are not a survey of every homegrown widget. The defaults we ship (10,000 characters, 20 mentions, page size 50, a 1 GiB Hosted cap, five-minute tokens) are our plan.
What buying Bootstrapware includes
- React widget with threads, mentions, unread, and resolve, see features
- Local adapter free for demos
- BYO adapter path ($9.99) so discussion text stays on your database
- Hosted store ($19.99) with id-only webhooks and JSON export
- MCP app config for Cursor. Never comment bodies
Prototype vs production checklist
| Capability | Afternoon prototype | Production implementation |
|---|---|---|
| Post a comment | Form plus insert | 10,000 code points, plain text, operation id, edit and delete |
| Which record | Trust the page URL | Tenant, resource type, and resource id inside a server-minted token |
| Mentions | Parse an @ from the text | Host-authorized user ids. A mention does not grant access |
| Unread | A boolean on the row | Per-user marker that moves only when the thread is actually opened |
| Resolve | Flip a status | Version check, readable resolved threads, draft kept on conflict |
| Delete | Delete the row | Tombstone so replies survive, body removed from ordinary reads and export |
| Pagination | Offset | Opaque cursor with a timestamp and id tie-break |
| Upgrades | Ship once | You own bugs, abuse, and migrations, or you take the package |
Cost framing
There is no vendor fee for doing it yourself, and this page does not invent an engineering-hour estimate.
| Cost | Build | Buy Bootstrapware |
|---|---|---|
| First working UI | A thread list and a composer | An npm embed |
| Ongoing ownership | Your team | Widget, plus your database on BYO or our store on Hosted |
| Cash price | Your time and infrastructure | Free / $9.99 / $19.99 per workspace per month |
FAQ
Should I build discussions myself?
Build when you want full ownership and will keep the edge cases. Buy when the job is threads on records you already authorize and you do not want to own that subsystem forever.
Why isn't an AI-generated comment list enough?
A list and composer is cheap. Resource-scoped authorization, mentions that do not grant access, per-user read state, versioned resolve, cursor pagination, and tombstones are a product surface you maintain.
What does buying Bootstrapware cost?
Free local and test, BYO $9.99 per workspace per month, Hosted $19.99 per workspace per month, plus the company-wide stack discount. This page does not convert your engineering time into a dollar savings figure.
Related: Cursor guide · Pricing · AGENTS.md · All comparisons