Alternatives
Products that do what IFTTT DataStore does
Give your Applets a memory
- 1
- 2
- 3
- 4
- 5SD
Hey HN! Charles here from Prequel (https://prequel.co). We just launched the ability to sync data from your own app/db/data warehouse to any of your customer’s Google Sheets, CSV, or Excel – and I wanted to share a bit more about how we built the Google Sheets integration. If you’re curious, see here for a quick GIF demo of our Google Sheets destination: https://storage.googleapis.com/hn_asset/Prequel_GoogleSheets.... Quick background on us: we make it easy to integrate with and sync data to data warehouses. Problem is, there are plenty of folks who…
2023
- 6
LoveCapsule▲76Your child’s memories, stored in your Google Drive—forever.
Apr 2026 · lovecapsuleapp.com
- 7IR
Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…
2025 · github.com
- 8
- 9
- 10SJ
2017 · github.com
- 11
- 12
- 13
- 14CO
I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself dozens of times a day across these apps. The deeper problem 1. Not portable – context is vendor-locked; nothing travels across tools. 2. Not relational – most memory systems store only the latest fact (“sticky notes”) with no history or provenance. 3. Not yours – your AI memory is sensitive first-party data, yet you have no control over where it lives or how it’s queried. Demo video:…
2025 · github.com
- 15
- 16
- 17
- 18
- 19IO
Look, every journaling app out there wants you to organize things into folders and tags and templates. I just wanted to write something down every day. So I built this. One note per day. That's the whole deal. - Can't edit yesterday. What's done is done. Keeps you from fussing over old entries instead of writing today's. - Year view with dots showing which days you actually wrote. It's a streak chart. Works better than it should. - No signup required. Opens right up, stores everything locally in your browser. Optional cloud sync if you want it - E2E encrypted with AES-GCM, zero-knowledge,…
Mar 2026
- 20
- 21
- 22AB
we've been working on a KV store for the past year or so which is 2-6x faster than Redis (benchmark link below) yet disk persisted! so you get the speed of in-memory KV stores but with disk persistence. To achieve this we've created our custom filesystem that is optimized for our special usecase and we're doing smart batching for writes and predictive fetching for reads. In addition to basic operations, it also provides atomic inc/dec, atomic json patch, range scans and a unique key monitoring mechanism (pub-sub) over WebSockets which essentially allows you to receive notification on…
2025 · hpkv.io
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →