Replicache

@RhysSullivan @clerk @auth0 @Cloudflare @Netlify @vercel @SST_dev @OpenStatusHQ Are we a lizard because our name starts with 'rep' for 'reptile'??

My 2025 todo list app tech stack ✨ 👤 @clerk for user management 🔒 @auth0 for auth ☁️ @Cloudflare Pages for hosting the ToS 🛠️ @Netlify for hosting the privacy policy 🚀 @vercel for hosting the app code 📦 @SST_dev handles deployment 🖥️ @OpenStatusHQ for uptime monitoring ⚠️ @getsentry for error monitoring 🪵 @AxiomFM for logs 📊 @PlausibleHQ for analytics 📽️ @msftClarity for session replay 🚦 @LaunchDarkly for feature flags 🧪 @posthog for A/B testing 🔍 @algolia for content search 📅 @calcom for scheduling collaboration times 🗝️ @unkeydev powering api ⬆️ @upstash for rate limiting 🦎 @replicache for syncing todos to local storage ✍️ @payloadcms for blog CMS 📕 @mintlify for docs 💳 @stripe for managing payments 🍋 @lemonsqueezy to make using stripe easier 🐻‍❄️ @polar_sh as a merchant of record 🏓 @PaddleHQ for invoices ✉️ @resend for sending broadcast emails 📬 @driaug_ by for sending reminder emails 📖 @mintlify for documentation 📤 @t3dotgg's UploadThing for image uploads 📁 @awscloud S3 for videos 🗄️ @tursodatabase stores todo table 🌎 @PlanetScale stores workspace table 📉 @neondatabase for storing notifications table 🤖 @OpenAI for ghiblifying images 📝 @AnthropicAI claude for summaries 🇨🇳 @deepseek_ai for fact verification 🔗 @langchain to analyze LLM usage 🇩🇪 @joinwarp for HR 🕵️@deel for operations 🧑‍⚖️@Rippling for payments 💛@tryramp for corporate cards 🟪 @linear for task tracking 😭 @Jira for team morale Let me know what you think! #buildinpublic #indiehacker

It's finally out!! I had a really great time talking to @thdxr and @adamdotdev about @zero__ms, @replicache, and how I've come to spend most of my career working on sync. Learn the backstory of Rocicorp here: youtube.com/watch?v=yTVHv3…

The most annoying problem for Zero's launch was what bug tracker to use. GitHub is way too slow, and Linear doesn't have public bugs or permissions – both required for OSS projects. This was driving me nuts, until I realized the only possible solution… ⏩ (link in reply)

@Sikandar_Bhide @supabase I wrote one using @replicache + @supabase realtime shootmail.app/blog/local-fir…

I wrote about @replicache and moving pierre.co to a local-first architecture. It has been a faint glimmer of light in the currently very dark javascript ecosystem: docs.pierre.co/changelog/loca…

Teams that use @replicache, what other frontend technologies do you use with it? Any traditional frameworks like React?

@Valcho @pocketbase @tinybasejs I enjoyed SignalDB's query api but in terms of maturity and feature completeness it's hard to compete with @replicache

X is right. Being this fast needs a content warning.

Alright, finally looked into local-first web apps. I get it. This is the future.

@CoinLandingPage @basehub_ai @liveblocks We built this over our underlying infra, based on @replicache and Pusher. For the in-editor cursors, we use prosemirror + yjs. We prefer keeping everything running on the same infra, although we'll probably lean onto Liveblocks for comments!

Beyond excited to share that Matt Wonlaw (aka @tantaman) has joined @rocicorp as our seventh partner. Matt is well-known in the local-first community for his work on vlcn.io and related projects, and I'm delighted he has chosen to join forces with us. We've all been working together now for several months, and I cannot wait to share the results. Let's just say that they will be _materializing_ very soon.

Been playing around with @tursodatabase and managed to adapt @SST_dev console's code so it creates a database per workspace and syncs everything nicely with @replicache 🤩 It's a bit hacky at the moment, but it works...

Rails is wonderful in so many ways, but damn is it slow on the frontend. The best performing rails app I’ve used is content site dev(dot)to. They did so many cool performance hacks to make it snappy: youtu.be/Afy7H04X9Us?si… Regardless I’m all ⚡️ @replicache now

In response to user feedback, we recently did a big iteration of the "strategies" section of the @replicache docs: doc.replicache.dev/strategies/ove…

@fredkisss You have to make some (relatively minor) changes to your schema to support Replicache, and you have to implement two special endpoints – /push and /pull. You can get a feel for what's involved here: doc.replicache.dev/byob/intro

Question : Do you need to structure your backend differently if you want to implement an offline first app with @replicache ? I want to make such an app with Django as my backend, I have already a DB model, but idk if I have to modify it to work specifically with replicache

Poke.

@t3dotgg @nestframework the real and only ts backend framework and @replicache for building realtime sync apps

@meijer_s @replicache

@WarrenInTheBuff Use @replicache. cc: @aboodman

Watch this @localfirstfm podcast with @aboodman ( @replicache ) about #localfirst stuff, storing data in browsers and more. It goes deep into the history and problems of client side storage. youtube.com/watch?v=cgTIsT…