I built ConvertSuite Pro after repeatedly running into the same problem in internal and client environments: teams needed to convert or normalize files, but the available options were always awkward.
The usual workflow looked like some combination of:
throwaway Python scripts
one-off command line tools
spreadsheets
or people pasting sensitive data into random online converters
None of that felt great, especially in environments where data handling rules are strict or machines are air-gapped.
So I built a tool that centralizes this into a single system that can run completely offline.
What it is
ConvertSuite Pro is a self-hosted conversion engine packaged as a Docker container.
It exposes a unified /api/convert endpoint and also provides an internal UI for manual work.
Everything runs locally, in memory.
No cloud calls, no external services, no telemetry.
What it supports
Right now there are ~20 conversion profiles covering common structured, semi-structured, markup and binary formats (CSV, JSON, Excel, YAML, XML, Parquet, PDF, images, Base64, Markdown, HTML, etc.).
The emphasis is on deterministic, repeatable outputs rather than clever heuristics.
Who it’s for
The target users are security teams, internal IT, and data/platform engineers who need a controlled and reproducible way to run transformations without everyone reinventing scripts.
Design choices
I intentionally chose:
containerized deployment
stateless backend
in-memory processing
because many of the places I’ve worked in care more about predictability and containment than feature richness.
Why not just script it?
In many cases you absolutely can.
But in practice that leads to drift, duplication, and knowledge living in individual notebooks and repos.
The goal here is to provide a shared internal utility.
Status
It’s production usable, but still early.
I’m mainly looking for feedback from people who work in constrained or regulated environments.
Factual7418•1h ago
I built ConvertSuite Pro after repeatedly running into the same problem in internal and client environments: teams needed to convert or normalize files, but the available options were always awkward.
The usual workflow looked like some combination of:
throwaway Python scripts
one-off command line tools
spreadsheets
or people pasting sensitive data into random online converters
None of that felt great, especially in environments where data handling rules are strict or machines are air-gapped.
So I built a tool that centralizes this into a single system that can run completely offline.
What it is
ConvertSuite Pro is a self-hosted conversion engine packaged as a Docker container. It exposes a unified /api/convert endpoint and also provides an internal UI for manual work.
Everything runs locally, in memory.
No cloud calls, no external services, no telemetry.
What it supports
Right now there are ~20 conversion profiles covering common structured, semi-structured, markup and binary formats (CSV, JSON, Excel, YAML, XML, Parquet, PDF, images, Base64, Markdown, HTML, etc.).
The emphasis is on deterministic, repeatable outputs rather than clever heuristics.
Who it’s for
The target users are security teams, internal IT, and data/platform engineers who need a controlled and reproducible way to run transformations without everyone reinventing scripts.
Design choices
I intentionally chose:
containerized deployment
stateless backend
in-memory processing
because many of the places I’ve worked in care more about predictability and containment than feature richness.
Why not just script it?
In many cases you absolutely can. But in practice that leads to drift, duplication, and knowledge living in individual notebooks and repos.
The goal here is to provide a shared internal utility.
Status
It’s production usable, but still early. I’m mainly looking for feedback from people who work in constrained or regulated environments.
I’d love to hear:
what formats you wish were supported
whether the API design makes sense
what would make this viable in your workplace
Happy to answer any technical questions.