Opportunities › Time-series data management for PostgreSQL › Proposed app
Tickshelf
Retention, rollups and partition health for time-series in plain PostgreSQL
- Score
- 46
- confidence 49
- Evidence
- 3
- items on the page
- Rivals
- 1
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2017
- Established market · AI estimate
ScreensConcept
Desktop app: Engineers review and configure retention rules, SQL, and growth forecasts—dense technical work done at a desk with keyboard and multiple screens. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Partition map
2 need attention412 GB
About this appAI proposal
Tickshelf is a web console for teams who store metrics, events, logs or sensor data in ordinary PostgreSQL. Connect a database and it shows how your time-based tables are partitioned, how fast they grow, and which old data can go. You set retention and rollup rules once, review them, and Tickshelf runs them on a schedule.
It works with open-source Postgres features and does not require a proprietary extension, so your data stays portable. Every change is shown as plain SQL before it runs, and you can copy that SQL into your own migrations instead.
It is for engineers who have outgrown one big table but do not want to adopt a separate time-series database or write partitioning scripts by hand.
- Tagline
- Keep time-series tidy in the Postgres you already run.
- Voice
- PlainPreciseCalm
- Why this name
- A tick is one time-series reading; a shelf is where old ones are kept in order. Two plain words that say what the product does with your data.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Partition map
See every time-partitioned table, its partitions, row counts and sizes in one view, with gaps and oversized partitions flagged.
No member yet
Retention rules
Set how long to keep raw data per table. Tickshelf drops or detaches expired partitions on schedule and logs each run.
No member yet
Rollup builder
Define hourly or daily summaries of raw rows and keep them after the raw data expires.
No member yet
SQL preview
Every action shows the exact SQL first. Copy it into your own migrations or approve it to run.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F6B6BDeep Teal · primary#F4F1EAPaper · surface#1F2A30Ink · text#D98324Amber · accent#B5492FRust · data, warnings
Typography
Aa
Tickshelf
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Keep time-series tidy in the Postgres you already run.
PricingAI proposal
TimescaleDB's pricing page (verified) lists two paid plans from $30 to $36 a month. The Team tier sits at the low end of that range. The free tier and the Business tier are starting points to test.
Free
Free
- 1 database
- Partition map and SQL preview
- Manual runs only
Team
$30 a month
- 3 databases
- Scheduled retention and rollups
- Growth forecast
- Shareable reports
Business
$90 a month
- 15 databases
- Slow query hints
- Run history for 1 year
- Slack and email alerts
Would you pay Team · $30 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
- Shared outputs. Teams share read-only health reports and the generated SQL plans by link with colleagues, finance and auditors. Each page carries the Tickshelf name and a link to try it on another database.
- Do they become customers?
- Report viewers are often engineers or managers who run their own Postgres and could sign up. Test whether shared-link visitors start a free connection, not just open the page.
- First customers
- Backend or platform engineers at startups of 5 to 30 people running self-managed or hosted Postgres with a metrics or event table over 100 GB.
- Where to reach them
- Hacker News and Postgres forums: Post a write-up on managing time-series in plain Postgres with a free read-only analysis of a user's schema.
- Open-source observability communities: Offer retention and rollup templates for common metrics and event table layouts in their chat and forums.
- Direct outreach to engineers: Message engineers at small teams who have written about partitioning or retention pain on their own Postgres.
- First milestone
- Ten teams connect a real database and five pay for the Team plan within 60 days.
Why people already pay for this
- VerifiedHacker News post received 39 points and 1 comments
- Public claimpg_deltax is positioned as an Apache-licensed alternative to TimescaleDB, a commercial time-series database extension
- VerifiedTimescaleDB's pricing page lists 2 paid plans, from $30 to $36 a month
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 · Scheduled job runnerQueue-based background worker serviceRetention and rollup jobs must run on time against customer databases, with retries and logs.
- This app · Secret storageEncrypted credential vaultDatabase connection strings must be encrypted and kept separate from app data.
RisksAI inference
- TechnicalRunning changes on customers' production databases is risky. A bad drop or lock could hurt trust, so dry runs, approvals and tested rollbacks are needed from day one.
- CommercialEngineers may prefer to run scripts or a database job scheduler themselves. A console must save clearly more time than a few SQL files to be paid for.
- DataCustomers must give database credentials to a third party. Many security teams will refuse unless there is a read-only mode and a self-hosted agent.
- CommercialThe evidence is thin: one post with 39 points and 1 comment. Demand for a paid console, rather than the extension itself, is unproven.
- TechnicalWithout a compression extension, savings come from dropping data and rollups, not storage compression. This may disappoint users expecting the same features as TimescaleDB.
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.