Hi everyone!

I m Rajiv, and I ve been working on a project called tseda (Time Series Explorer).

If you ve ever stared at a messy time series dataset and wondered where to even start, I built this for you! It s an app designed to take the headache out of exploring and decomposing regularly sampled data (hourly or greater).

The "Why" behind it:
I wanted a tool that didn't just give me a raw plot, but actually helped me understand the structure of the data. tseda uses Singular Spectral Analysis (SSA) to break things down into Trend, Seasonality, and Noise, but it does the heavy lifting for you automating window selection and suggesting component groupings so you aren't just guessing.

Vedic astrology isn't just zodiac signs. There are documented

systems Samudrika Shastra for palm reading, Mukhanga Shastra

for face reading, full Jyotish for birth charts each with

thousands of specific rules that have been studied for centuries.

Hey community, first time here.

I am Manish and I am building TectorAI - a weaving thread that joins all research platforms. Have been in research workflows for my entire career(banking, consulting, commercial strategy) and realized all platforms & tools create excellent research reports - intelligence, but consumption is still difficult. Insights I found disappeared the moment tab was closed. I would end up hours looking for info or recreating my old research.

Hey everyone! I'm Abhishek, founder of Clipo AI.

Quick background: I spent 8 years building AI systems for video content deep learning research with Sony Japan, then founding AI engineer at Vidyo.ai (now Quso.ai). After working with hundreds of creators, I kept seeing the same problem: one great video recorded, then 6+ hours spent turning it into clips, posts, carousels, and thumbnails using 5-6 different tools.

So I built Clipo one upload, 20 pieces of publish-ready content. Clips with virality scores, branded carousels, voice-aligned LinkedIn/Twitter posts, thumbnails, AI images, subtitles, and more. 12 products in one connected workflow.

We're launching on Product Hunt tomorrow (May 6). This is my first time building in public I've always been the behind-the-scenes engineer. Would love to connect with other makers here.

Hey !

I'm Shivi a Project & Product Manager with 4 years of experience, and honestly, one of the most curious people you'll meet when it comes to new AI products.

I spend a lot of my time exploring what's being built in the AI space, testing tools, breaking things, and figuring out what actually solves real problems vs. what's just hype. No engineering degree, but that's never stopped me from getting hands-on and building.

I believe some of the best product thinking comes from people who obsess over the why and the who- not just the how. And that's where I live.

Hi Product Hunt. I am Andreea, founder of 2 Minutes Responder. We launched today.

I built this after watching people make offers on UK properties without knowing the flood zone would make it uninsurable, or that the net yield was negative from month one after real costs. The data has always been public. Nobody had put it together before the offer.

2MR does it in 90 seconds. Flood zone, net yield, crime trend, school rating, 5-year growth. Any UK postcode. Free.

Would love to hear from anyone in property or investing. Happy to run any UK postcode publicly right here in the comments if you want to see it in action.

My name is Eva and I'm from Czechia. I studied Russian translation at university, that was supposed to be my path. For a few years it was: I worked as a project coordinator at a power engineering company. Then things shifted, my field got affected by what was happening in the world, and I had to rethink my career.

I had been curious about programming for a long time, partly because my boyfriend is a software engineer and watching him work made it feel less abstract. There was a boom of programming courses in Czechia at the time, so I took the chance and started from zero, spending evenings building little card games and trying to make sense of JavaScript.

A few months later, I found a job as a frontend engineer at a digital agency. That first year was hard. I was learning fast, building real products for real clients, and constantly feeling behind. Impostor syndrome was a daily companion. But I kept going. My partner became my mentor, and I owe him a lot of who I am as a developer today.

A year later, I joined Native, an American startup building a B2B AI conversation platform. For a language enthusiast like me, it was a dream. Over three years I grew from frontend engineer to senior product engineer, architecting real-time WebSocket systems, driving activation growth, working closely with design and product. That place taught me how much of engineering is actually about people, trade-offs, and listening.

Hi all, I am Yaoshen Luo. Here is my late self-introduction.

I ve been in the industry for 14 years. I used to develop positioning and navigation systems for Baidu Maps, worked on recommendation engines, and eventually managed a team of 30+. Currently, I am deeply involved in the R&D of Voice Agent SaaS services.

Hey everyone

I m Qasim, currently building my first product

I kept running into the same problem while working, constantly switching apps mid-task and breaking focus without even realizing it

Tried using timers but they didn t really change anything for me, they just tracked time while I was distracted

Hi, I'm a research data engineer working with academic teams on data collection, cleaning, versioning, and reproducible analysis.

A lot of research data work breaks down before the model, chart, or paper ever happens. Sources change, scripts are undocumented, licenses are unclear, and six months later nobody can explain exactly how the dataset was created.

I'm especially interested in open science, dataset provenance, archival workflows, and practical ways to make research easier to rerun without slowing everyone down too much.

Curious how others here handle this: when you publish or share a data project, what do you document first... raw data, collection timestamps, cleaning scripts, licenses, environment files, or something else?