This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
I run very different businesses: a trucking company, farms, a radio station, a newspaper... Every new app asked the same questions:
who is this person?
what can they see?
what is it related to?
what changes when one piece of data changes?
Each time I was rebuilding the same infrastructure again, with auth, APIs, databases and servers, and it took up the space I needed to think about the business. So I kept going down, from the interface to state, to relationships, to identity, to permissions, until I found something basic enough to build everything else on. .me wasn't designed top-down. It came from solving everyday problems.
What feedback would help most? Try one of the demos and tell me where the syntax doesn't make sense to you, or where explain() doesn't answer the "why" you expected. I'd also love to hear about a real case of yours that you'd want to model, so I can see where it breaks.
me is a small kernel: you write data as paths, define derived values with formulas, and the kernel keeps them up to date.
When one value changes, it doesn't recompute the whole graph, only the k values that actually depend on it. We measure that in public benchmarks you can rerun, including one on GTFS-Madrid-Bench transit data.
Every derived value keeps its derivation. me.explain(path) returns the formula, the inputs and their values, so when something is false, you can see exactly which input made it false.
Identity and permissions live in the same structure: a branch marked secret can't be read without the key.
.me was submitted on Product Hunt and earned 0 upvotes and 2 comments, placing #292 on the daily leaderboard. Self-explaining data graphs for apps and AI agents. Interactive demos forme — Smart Cities, Robots, and more.
.me was featured in Robots (10.7k followers), Artificial Intelligence (483k followers), GitHub (41.5k followers) and Tech (636.2k followers) on Product Hunt. Together, these topics include over 346.6k products, making this a competitive space to launch in.
Who hunted .me?
.me was hunted by neurons.me. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how .me stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
neurons.me
I run very different businesses: a trucking company, farms, a radio station, a newspaper... Every new app asked the same questions:
who is this person?
what can they see?
what is it related to?
what changes when one piece of data changes?
Each time I was rebuilding the same infrastructure again, with auth, APIs, databases and servers, and it took up the space I needed to think about the business. So I kept going down, from the interface to state, to relationships, to identity, to permissions, until I found something basic enough to build everything else on. .me wasn't designed top-down. It came from solving everyday problems.
What feedback would help most?
Try one of the demos and tell me where the syntax doesn't make sense to you, or where explain() doesn't answer the "why" you expected. I'd also love to hear about a real case of yours that you'd want to model, so I can see where it breaks.