Open-source vs managed CSV importer
Open-source CSV importer vs managed Bootstrapware Importer
Searching for an open-source CSV importer, a free React Excel upload, or whether to keep schema in your repo? You can. Bootstrapware supports a local fields path forever. The paid product exists for the control plane around the component, not because spreadsheet parsing must happen on our servers.
That distinction matters for SEO and for buying: a production-ready CSV importer does not require uploading rows to a vendor. It requires a finished customer workflow and, optionally, a place to publish configuration.
Local schema (valid forever)
Pass fields (and optional duplicateKey) into the React component. Parsing, mapping, and validation still run in the browser. You never have to create a Bootstrapware account to evaluate that path. See the quickstart and configuration docs.
Choose local schema when your field definitions change with deploys, you have one or two import flows, and you do not need dashboard-published revisions or operational webhooks yet. This is the closest thing to an “open-source style” integration path without pretending every peer package is equivalent.
What the managed layer adds
- Importer definitions edited in a dashboard
- Draft vs published revisions so live clients do not see half-edited schemas
- Test and live publishable keys
- Operational sessions (counts, file type, duration). Not row contents
import.completedwebhooks with HMAC signing- Billing for production live configuration ($19.99 / month)
Spreadsheet contents still stay in the browser. Hosted mode loads configuration and may report non-content session metadata. Your backend still receives rows from onComplete. Read Importer privacy and sessions.
Side by side
| Need | Local / open approach | Managed Bootstrapware |
|---|---|---|
| Schema changes without redeploy | You build that | Publish a revision |
| Test vs live keys | Your own env discipline | Built-in key prefixes and entitlements |
| Import completion signals | Log it yourself | Sessions + webhooks |
| File contents to a vendor | Depends what you build | No. Browser-side by design |
| Customer mapping UX | You build or copy | Included in the React component |
| Cost | Engineering time | $19.99 / mo when you need production hosted config |
Practical recommendation
Start local. Graduate to hosted configuration when non-engineers need to edit schemas, when you want publish-as-release, or when you want operational webhooks without inventing them. That is the managed product. It is not “upload your customers’ files to us.”
If the question is really “should we build the whole importer?”, see build vs buy. If you are comparing platform vendors, start at Compare.
FAQ
Is Bootstrapware Importer open source?
The React package supports a fully local fields schema with no account required. Hosted configuration, publishable keys, sessions, and webhooks are the managed product around that browser-side component.
Do I have to pay to use Bootstrapware Importer?
No for local schema and development/test keys. Yes for production live hosted configuration, which starts at $19.99 per month.
Does managed mode upload my customers’ spreadsheets?
No. File contents stay in the browser. Hosted mode loads published field configuration and may report non-content session metadata such as counts and file type.
When should I graduate from local schema to hosted?
When non-engineers need to edit schemas, when you want publish-as-release without redeploying the app, or when you want operational webhooks and test/live keys without inventing them.
Related: Build vs buy · Browser-side CSV import · Configuration · Pricing