Opportunities › Backend infrastructure for ClickHouse analytics › Proposed app
Tidegate
Durable ingest, access rules and live queries for your ClickHouse in one service
- Score
- 36
- confidence 56
- Evidence
- 6
- items on the page
- Rivals
- 2
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2016
- Established market · AI estimate
ScreensConcept
Desktop app: Infrastructure teams configure permissions, set up queries, and monitor ingest health in a control center—backend work requiring detailed configuration and dense data views. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Ingest
Durable12,480/s
About this appAI proposal
Tidegate is a single service you deploy next to ClickHouse. It takes events over HTTP, writes them durably, enforces which rows and columns each user can see, and streams fresh results to your app. You skip assembling a message queue and a custom auth API for every project.
It is built for small software teams shipping IoT telemetry, real-time dashboards or data-heavy features who want ClickHouse without the operational overhead. Define tables, roles and rules in one config file, then point devices and front ends at it.
Unlike stitching together Kafka and a hand-written backend, Tidegate aims to be the quick path for projects where that scaffolding is not worth building. This is a proposal: a first version would cover common ingest and access patterns, not every edge case.
- Tagline
- Point your data at ClickHouse. Tidegate handles the gate.
- Voice
- PlainCalmPrecise
- Why this name
- A tide gate lets water in steadily and controls what passes, like ingest buffering and access rules for a data store.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Durable HTTP ingest
Send single events or batches to an endpoint. Tidegate buffers them on disk and inserts into ClickHouse in batches, retrying if the database is down.
No member yet
Row and column permissions
Write rules like 'tenant sees only own rows' or 'hide the email column from viewers'. Rules are applied to every query.
No member yet
Scoped keys and tokens
Issue ingest keys for devices and short-lived read tokens for browsers, each tied to a role and a tenant.
No member yet
Live query streams
Subscribe from a web app to a saved query and receive new results over a stream, without building your own socket layer.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F3D3EDeep Harbor · primary#F2F7F5Sea Foam · surface#14262AInk · text#F2A33ASignal Amber · accent#3C8D6EKelp · data
Typography
Aa
Tidegate
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Point your data at ClickHouse. Tidegate handles the gate.
PricingAI proposal
The material gives no competitor prices: ClickHouse lists plans with prices on request. These tiers are a starting point to test, likely tied to ingest volume, not a market-based figure.
Self-host
Free
- Single node
- Ingest, rules and endpoints
- Community support
Team
$49 a month
- Managed deployment
- Live query streams
- Up to 5 members
- Email support
Scale
Contact us
- High-volume ingest
- Single sign-on
- Priority support
Would you pay Team · $49 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
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. It runs behind the customer's own apps and devices, so end users do not see it. Growth comes from developer content, docs, an open-source core and word of mouth among ClickHouse users.
- Do they become customers?
- Readers of docs and examples can become paying teams, but nothing in normal use exposes the product. Test whether a free self-host tier converts to managed plans.
- First customers
- Small teams of 2 to 10 engineers building IoT telemetry dashboards on ClickHouse, with no dedicated data platform engineer.
- Where to reach them
- Hacker News and ClickHouse forums: Post a working example that replaces a Kafka-plus-custom-API setup, and answer questions in threads where setup pain is raised.
- Open-source repository: Publish the self-host core with a ten-minute quickstart for sensor data, then offer a managed upgrade.
- Direct outreach to IoT startups: Message founders and engineers who mention ClickHouse setup problems and offer to migrate one pipeline free.
- First milestone
- Five teams run a real pipeline on Tidegate, and at least two agree to pay for managed hosting within 60 days.
Why people already pay for this
- VerifiedHacker News post received 20 points and 4 comments
- Public claimTeams building with ClickHouse must set up external infrastructure like Kafka and custom backend APIs just to handle basic ingest and access patterns.
- Public claimMultiple infrastructure components are repeatedly rebuilt across projects, representing substantial scaffolding burden.
- Public claimClickHouse's complexity is a barrier to adoption, particularly for projects that want to leverage its analytics capabilities but lack infrastructure overhead tolerance.
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 · Ingest bufferDisk-backed write-ahead log in a small Go or Rust serviceDurable batching before ClickHouse inserts needs a long-running process, not serverless functions.
- This app · DatabaseClickHouse (customer-owned or managed)The product sits in front of it and runs queries on its behalf.
RisksAI inference
- TechnicalDurability and exactly-once behaviour under crashes and ClickHouse outages are hard to get right; failures would lose customer data and trust.
- TechnicalEnforcing row and column rules on arbitrary SQL safely is difficult; a bypass would be a serious security flaw.
- CommercialEvidence is thin: one Hacker News post with 20 points and 4 comments. Demand may be small or met by open-source tools.
- PlatformClickHouse may add built-in ingest or API features, shrinking the gap this product fills.
- CommercialTeams may prefer to keep Kafka for other uses, or consider a small service in the data path too risky to adopt.
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.