CSVbox alternative — self-hosted import with PDF, OCR and audit

Q: Is Mildport a self-hosted alternative to CSVbox?

Yes. Like CSVbox, Mildport is an embeddable importer you drop into your app, but the engine is self-hosted in your own infrastructure and it handles more than CSV: spreadsheets, JSON, XML, PDF tables and OCR'd scans.

Q: Why choose Mildport over a lightweight CSV widget?

Choose Mildport when you need self-hosting and data residency, inputs beyond clean CSV, deterministic and explainable column matching, or an event-sourced, replayable pipeline with a webhook audit trail. For a simple low-cost cloud CSV widget, CSVbox may be enough.

Q: Does Mildport keep data in my own infrastructure?

Yes. Mildport runs as a Docker Compose stack in your VPC, files never leave your environment, and licenses verify offline with no phone-home.

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Mildport is a CSVbox alternative for teams that have outgrown a basic CSV widget — or that need self-hosting from day one. Same embeddable model your users tap into, but the engine runs in your own infrastructure and it understands far more than clean CSV.

CSVbox is a solid, low-friction way to put a CSV importer on a page. The two reasons teams move to Mildport are almost always the same: “our files aren’t just clean CSV” and “this data can’t go through someone else’s cloud.”

CSVbox vs Mildport at a glance

	CSVbox (cloud)	Mildport (self-hosted)
Hosting	Vendor cloud	Your infrastructure (Docker Compose)
Data path	Through vendor cloud	Stays in your VPC
Inputs	CSV / spreadsheets	CSV, TSV, XLSX, ODS, JSON, XML, PDF tables, OCR’d scans
Mapping	Cloud-run	Deterministic, explainable matcher (visible scores)
AI	Vendor-managed	Optional BYO-AI judge, off by default
Pipeline	Vendor-managed	Event-sourced, replayable, webhook audit trail
Licensing	Cloud account	Offline license key, no phone-home

Why teams pick Mildport

More than CSV. Customers send messy XLSX, JSON, XML, PDF tables and scanned documents. Mildport decodes them through dedicated sidecars so the same flow handles real-world inputs.
Self-hosted and private. Files never leave your VPC; the engine never calls home. That’s the difference between passing a security review and rewriting your data flow to pass one.
Explainable and replayable. Visible match scores and an event-sourced pipeline mean you can show why a column mapped the way it did — and replay it. See How it works.
Audit-ready delivery. Rows reach your app over a license-keyed REST API with webhook deliveries and an audit trail.

When CSVbox is the better fit

If your inputs really are simple, well-formed CSVs, you want the cheapest fully managed cloud widget, and data residency isn’t a constraint, a lightweight tool like CSVbox is the pragmatic choice. Mildport is for when format breadth, explainability or self-hosting start to matter.

Getting started

npm install @capitality-io/import-suite-ng

<mildport-import
  api-base-url="https://imports.your-infra.example"
  license-key="SIGNED_TENANT_KEY"
></mildport-import>

Define your targets and listen for import-applied — see the Quickstart. Run the engine yourself via the self-hosting overview.

FAQ

Is Mildport a self-hosted alternative to CSVbox? Yes — an embeddable importer like CSVbox, but self-hosted in your own infrastructure and it handles spreadsheets, JSON, XML, PDF tables and OCR’d scans, not only CSV.

Why choose Mildport over a lightweight CSV widget? When you need self-hosting and data residency, inputs beyond clean CSV, explainable column matching, or an auditable, replayable pipeline. For a simple cloud CSV widget, CSVbox may be enough.

Does Mildport keep data in my own infrastructure? Yes — it runs as a Docker Compose stack in your VPC, files never leave your environment, and licenses verify offline with no phone-home.

Try it on your own files at mildport.com, or read What is Mildport?