Opportunities › Durable message streams on object storage › Proposed app
Tidelog
Durable event streams that keep their data in your own object storage bucket
- Score
- 51
- confidence 57
- Evidence
- 5
- items on the page
- Rivals
- 2
- named in sources
- First version
- 60 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2011
- Mature market · AI estimate
ScreensConcept
Desktop app: Software engineers work with event streams, replay offsets and configure retention policies at a desk with dense dashboards. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Streams
All healthy14 streams
About this appAI proposal
Tidelog is a hosted stream service for software teams that build event-driven systems, data pipelines or real-time apps. You create a stream, append messages over plain HTTP, and read them back by offset, by long-poll or as server-sent events. Messages are kept durably in object storage, so there are no brokers to size, patch or rebalance.
Cost follows the data you store, not the rate you push it. A web console, installable as a PWA, lets you inspect streams, tail them live, replay from any offset and check what retention costs, from a phone or a laptop.
It uses ordinary HTTP rather than a proprietary wire protocol, so any language with an HTTP client can use it, and moving away means reading your own files from your own bucket.
- Tagline
- Streams that live in storage, not in servers.
- Voice
- PlainCalmPrecise
- Why this name
- A tide log records what comes in and goes out over time, like an append-only stream. The name is two short plain words joined, easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Plain HTTP stream operations
Create, append, read, long-poll and server-sent events over standard HTTP. No special client library is required.
No member yet
Storage-based cost
Durability sits on commodity object storage, so the bill follows retained data instead of throughput.
No member yet
Bring your own bucket
Point streams at a bucket you own. Your data stays readable by you even if you leave.
No member yet
Offset replay
Read from any offset, or from a timestamp, to rebuild a consumer or debug a bad deploy.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F3D4CDeep Harbor · primary#F2F7F5Sea Foam · surface#14232AInk · text#F26B3ABuoy Orange · accent#4FB3A5Shallow · data
Typography
Aa
Tidelog
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Streams that live in storage, not in servers.
PricingAI proposal
The material gives no competitor prices: AutoMQ lists plans with prices on request. These tiers are a starting point to test, tied to stored data as the opportunity suggests.
Free
Free
- Up to 3 streams
- 5 GB stored
- 7-day retention
- Console access
Team
$49 a month
- Unlimited streams
- 500 GB stored
- 90-day retention
- Scoped tokens
- Email support
Scale
$299 a month
- 5 TB stored
- Bring your own bucket
- Custom retention
- 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. Reach comes through developer content, open documentation, benchmarks and examples. Streams are used by services behind the scenes, so use does not by itself show the product to new buyers.
- Do they become customers?
- Developers who find it through docs or posts can sign up and pay directly. Test whether free-tier users convert once their stored data grows past the free limit.
- First customers
- Small backend teams of 3 to 15 engineers at startups that run Kafka or a managed broker for modest-volume event pipelines and feel the cost.
- Where to reach them
- Hacker News and dev blogs: Publish a cost comparison and a how-it-works post for durable streams on object storage.
- Open protocol docs and examples: Offer curl and SDK-free examples for append, long-poll and SSE so a trial takes minutes.
- Direct outreach: Contact engineers who commented on the Hacker News thread and offer a free pilot.
- First milestone
- Five teams run a real production stream for 30 days and at least three agree to a paid plan.
Why people already pay for this
- VerifiedHacker News post received 159 points and 31 comments
- Public claimDurable streams can be built on object storage with cost advantages
- Public claimStream operations include create, append, read, long-poll, and server-sent events
- VerifiedAutoMQ sells paid plans with prices on request, on its own pricing page, plus prices on request for larger customers
- Verified
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 · Stream engineRust HTTP service on a container hostLong-lived connections for long-poll and SSE need a runtime beyond Vercel functions.
- This app · Durable storageS3-compatible object storageHolds the stream segments; customers may also bring their own bucket.
RisksAI inference
- TechnicalObject storage latency and per-request costs may make small, frequent appends slow or costly unless batched, which weakens the cost story for high-rate streams.
- CommercialKafka and AutoMQ are established, and teams with existing Kafka clients may not move to a new HTTP interface without a compatibility path.
- TechnicalDurability and ordering guarantees are hard to get right; data loss in an early version would end trust quickly.
- DataCustomers may hold sensitive events, so bring-your-own-bucket, encryption and access controls must be solid from the start.
- CommercialThe only market signal is one Hacker News post; interest from developers may not turn into paid usage.
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.