After 18 years of corporate and academic life me and my c-founder @hschildt decide to do something new and we launched Skimle (https://skimle.com) which trying to be "Excel for text" - enabling systematic analysis and structuring of all qualitative data. You can for example analyse interview notes, meeting notes, statements and reports to find themes and insights.
Have a look and if you like it, hit all the appropriate upvote and like buttons!
Hey everyone I recently launched ScreenQuest, an Android screen time tracker built around a simple idea:
Blocking apps doesn t work. Friends do.
After trying (and uninstalling ) multiple app blockers, I realized the problem isn t a lack of tools it s a lack of accountability. Most blockers are easy to disable. It s much harder to ignore the fact that your friends can see your screen time.
I built BottleXP an AI sommelier that lives in your pocket, the idea came from I was traveling across Europe and realized wine here is incredible. So many options, so affordable. But as a casual drinker, I had no idea how to choose.
We ve just launched Aepto! It helps you manage domains, SSLs, website monitoring, and performance insights in one place. Custom reminders, smart notifications, and centralized views make running multiple sites easier and less stressful.
Most features are available for free, so anyone can get started right away.
I've built ClawStreet - a stock trading platform for autonomous AI agents.
The concept:
Autonomous AI agents (powered by OpenClaw framework, or your own) register themselves, choose trading strategies, and compete on a live leaderboard using real market data. Completely paper trading - no real money at risk.
I built SubTrackHub, a developer-first engine that connects your AWS accounts, GCP projects, and GitHub organizations to find the cost leaks that standard billing consoles miss.
The problem: For most teams, cloud spend is fragmented. You have AWS instances in one tab, GitHub seats in another, and a dozen SaaS tools on different credit cards. Because the data is scattered, you miss the "sneaky" costs like idle NAT Gateways, forgotten test instances, or zombie GitHub seats for employees who left months ago.
SubTrackHub fixes that. Instead of just showing you a graph of your bill, it deep-scans your infrastructure to pinpoint exactly where the waste is. It moves beyond basic billing APIs to ingest the AWS CUR (Cost and Usage Report), giving you sub-penny accuracy on exactly what s happening in your VPCs.
At the start of most projects, database diagrams feel really helpful. Everyone understands the structure, relationships are clear, and discussions are easier.
Then the project grows and somehow the diagram gets left behind.
I d love to hear what actually broke the database diagram workflow in projects you ve worked on.
Was it too many migrations happening too fast?
People changing the schema directly in SQL?
The diagram slowly drifting away from production?
Tools becoming annoying to keep in sync?
Or simply no one feeling responsible for maintaining it anymore?