Opportunities › Self-hosted ETL/ELT platforms for data engineering › Proposed app
Millrace
Self-hosted data pipelines with a visual builder and no per-row billing
- Score
- 41
- confidence 41
- Evidence
- 4
- items on the page
- Rivals
- 2
- named in sources
- First version
- 70 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2020
- Established market · AI estimate
ScreensConcept
Desktop app: Data engineers build and manage visual pipelines, configure quality checks, and monitor runs—all complex, extended-focus work at a workstation. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Pipelines
3 need attention41 healthy
About this appAI proposal
Millrace is an ETL/ELT platform you run on your own servers or cloud account. Build pipelines on a visual canvas, run them with a DuckDB-based engine, and watch every run from an installable web console on your phone or desktop. Your data never passes through our infrastructure.
It is made for data engineers and platform teams who need control: regulated environments, data residency rules, or teams tired of bills that grow with every row. Pricing follows your deployments, not your data volume.
Unlike a pile of open-source tools wired together by hand, Millrace puts the builder, connectors, quality checks, reverse ETL and run history in one product. Pipelines are saved as plain files you can review in Git and take with you.
- Tagline
- Move your data. Keep your data.
- Voice
- PlainSteadyTechnicalDirect
- Why this name
- A millrace is the channel that carries water to a mill. It suggests steady flow you direct and own, in two plain words.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Visual pipeline canvas
Drag sources, transforms and destinations into a flow. Switch any step to SQL when you need it. Every pipeline is stored as readable files.
No member yet
Runs on your infrastructure
Deploy one container in your cloud or data centre. Credentials and data stay inside your network; only the console is a web app.
No member yet
Flat pricing per environment
No per-row or per-connector meters. You pay for each deployment, so a larger backfill never changes the bill.
No member yet
Built-in data quality checks
Add row-count, null, uniqueness and freshness rules to any step. Failing rows are quarantined and the run can stop or continue.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#17353ADeep Channel · primary#F6F1E7Paper · surface#1B2A2EInk · text#C8672DCopper · accent#4F8A6BReed Green · success data#A8432FClay Red · error data
Typography
Aa
Millrace
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test, priced per deployment to avoid per-row billing, which the evidence cites as a pain point.
Community
Free
- 1 environment
- Core connectors
- Visual builder and SQL steps
- Community support
Team
$249 a month
- 3 environments
- All connectors and reverse ETL
- Quality checks and alerts
- Email support
Business
$799 a month
- 10 environments
- Roles, SSO and audit log
- Git promotion workflow
- Priority support
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Millrace runs inside customers' private infrastructure, so there is no visible output or built-in sharing. Reach comes from open documentation, a free tier, GitHub presence and direct sales to data teams.
- Do they become customers?
- Free-tier users are the same engineers who buy paid tiers, so conversion can be tested directly. Test whether Community users hit the environment limit and upgrade within 60 days.
- First customers
- Platform teams of 2 to 6 data engineers at EU mid-size companies in finance or health, where data residency rules rule out cloud ETL services.
- Where to reach them
- GitHub and open-source forums: Publish the free tier and example pipelines; answer threads where people ask for self-hosted ETL without per-row billing.
- Data engineering communities: Share migration guides and write-ups on running pipelines in regulated environments on Slack groups and newsletters.
- Direct outreach: Contact data leads at regulated EU firms with a short call offering a one-environment pilot.
- First milestone
- Five paid Team subscriptions from regulated companies within 90 days of launch, each running a production pipeline.
Why people already pay for this
- VerifiedGitHub repository gained 1501 stars in 143 days
- Public claimTeams are motivated to avoid vendor cloud lock-in and per-row billing models in favor of self-hosted ETL/ELT solutions they control.
- Public claimData teams need comprehensive ETL/ELT capabilities including visual pipeline building, multiple data connectors, data quality tools, reverse ETL, and observability.
- Public claimThere is demand for ETL/ELT solutions that can be deployed on teams' own servers or cloud infrastructure rather than managed services.
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Customer-side runtimeContainer image with a job workerPipelines must run inside the customer's network; the PWA console connects to this agent.
- This app · Query engineEmbedded DuckDBRuns transforms and checks in-process without a separate warehouse cluster.
RisksAI inference
- CommercialFree open-source tools already exist and many teams will not pay. It must be tested whether buyers pay for integration, support and a visual builder.
- TechnicalConnector breadth is the hard part. A small team may ship only a few connectors at first, which can block teams that need a specific source.
- TechnicalCustomers run varied environments (Kubernetes, VMs, air-gapped). Supporting installs and upgrades can consume the team's time.
- RegulatoryRegulated buyers will ask for audits, SSO and certifications that a new vendor does not have yet. Sales cycles may be long.
- PlatformThe mobile console needs a reachable endpoint and push alerts. Strict networks may block this, limiting phone use to VPN users.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.