If the self hosted server goes down the app at least still works with local data
23.01.2026 23:10
👍 0
🔁 0
💬 0
📌 0
If the self hosted server goes down the app at least still works with local data
We don’t have full peer to peer transport yet but that’s something we might look into in the future
The self hosted server has full persistence!
My talk from @sync_conf 2025 is ready!
Check it out to learn how:
1) CRDTs + cryptographic permissions work
2) @jazz.tools is now a general-purpose database
3) our unique Jazz Cloud infra compares to
- traditional stacks
- other sync engines
- Durable Objects
www.youtube.com/watch?v=wils...
For now, the new UniFFI RNCrypto is opt-in (see instructions below), but the perf improvement is so impressive that we will roll it out as the default once it has been proven in a few adopter apps.
If you are trying it in your app, ping us on Discord!
jazz.tools/docs/react-...
Jazz 0.19.0 brings our high-perf Rust core to all Jazz environments:
- Browser/workers via wasm-bindgen
- NodeJS via NAPI-RS
- *New*: ReactNative/Expo via UniFFI
In the future, we'll offer idiomatic Swift, Kotlin, Go, etc. bindings as we move API-level code into Rust as well.
@anselm.io (@jazz.tools)will help us grapple with the question of when our sync systems become a full-fledged database.
Anselm's talks at Local-First Conf have always been crowd-pleasers, so he's sure to delight at Sync Conf.
Shipping the feature and going to bed early
it has begun
People keep asking us if @jazz.tools will have vector search...
What's better than building a first class vector search feature for Jazz in maybe a couple months?
A single person right now being able to ship it as a small, very neat, very high quality library *on top of* Jazz!
vimeo.com/1111603758
Given our realisation that *actually, @jazz_tools is a database* (see QT)...
...we're hosting another meetup in SF this Wednesday!
(RSVP below!)
Thinking of Jazz as a DB begs the question: how does it fit into the stack?
bsky.app/profile/jaz...
If you're in SF on Wednesday, we'd love to hear from you and brainstorm in person! Drinks, snacks and good vibes are on us
lu.ma/icpt219a?ut...
We'd love to hear what you think about this new way to think about Jazz, as we adapt our homepage, docs, and most importantly as we shape our feature roadmap accordingly.
What would you expect most vs. what we have now?
One that’s inherently
- distributed
- high-throughput multiplayer & LLM ready
- verifiably secure
Which means Jazz will do everything a DB does
But you can use it in more places
And it’ll scale better
And offer better DX
Do more out of the box
And do the previously impossible
narrative update
Jazz isn’t replacing databases and backends
Jazz isn’t local-first only
Jazz isn’t a sync engine only
Jazz is simply a *new kind* of database
🧵
The wait is finally over!
It’s time for another
FUTURE OF CODING LONDON
Tuesday, July 22 @ 18:00
Kindly hosted by Granola at their office
Sponsored by @jazz.tools
RSVP here:
lu.ma/lo2medup
Demo/Talk submission here:
foc-london.notion.site/21c379f0e4c...
Two weeks after alpha-3 which foreshadowed our move to @jazz.tools for greater stability, alpha-4 gets it done!
blog.muni.town/roomy-space-...
Special shoutout to @flo-bit.dev who took the lead on this release.
Up next is bridging so Roomy & Discord (later Matrix) folk can share the same space.
My full talk from @localfirstconf.com is up!
Featuring 1y of progress on @jazz.tools
And: two big announcements + the most sketchy, yet successful demo I've ever done.
- Waffle, a Discord/Slack alternative built on Jazz
- Soul, our upcoming AI toolkit for Jazz
www.youtube.com/watch?v=e3-y...
> The AI just is "one more collaborator" and you just dump the tokens into Jazz state as they come in.
This is the correct mental model
Streamed LLM responses are the perfect example of why we didn't base @jazz.tools on an existing DB, but are building a new backend + DB from scratch.
Originally we just wanted to support Figma/Notion-like apps where we knew we had to sync 100,000s of tiny edits per second... 🧵
x.com/marbemac/st...
Quoted tweet by James Cowling: ""Local first" is a nice goal towards low latency and offline support but in practice the source of truth for almost any app that stores important data is the server. "Sync engines" are a solid architectural model that bridges state on the client and state on the server, without dealing with polling, inconsistency, and all the distributed systems bs that should be a relic of the past. They are how everyone will interact with backends in the future. We see @convex_dev as "react for backends" but there are an emerging group of great platforms in this space."
Sync engines are an incremental improvement to the "centralised server + client" model - the minimal possible step towards the real-time nature of apps today.
But we can do much better 🧵
Love meeting new builders online
me: “Hey Jazz supports ProseMirror now, we should build a ProseKit example or something”
*minds my own business for 3h*
@ocavue.bsky.social: “here’s the example”
"Local First is accidentally perfect for the AI age"
Great talk from @anselm.io of @jazz.tools on how AI and Local First software are the perfect partners.
@localfirstconf.com is off to a fantastic start, the number of new people is mind blowing.
For us at @jazz.tools, today was all about getting hands-on and helping people building cool stuff with Jazz - and handing out our first vibe coding certifications!
screenshot of canvas with different drawings: pink floyds rainbow triangle, the jazz logo, a tic-tac-toe game, some text, a heart, etc
my endless shared canvas with @jazz.tools is kinda usable now, come draw something at:
flo-bit.dev/jazz-endless...
Megathread of everything we're announcing for @jazz.tools at @localfirstconf.com
It's been a hell of a year in the best sense and I can't wait to share what we've been cooking.
(And this doesn't even include our "one more thing" 🤫)
Stay tuned as I expand on details over the next couple days!
Join the @jazz.tools team at Local-First Conf!
- learn how to vibe-code apps with Jazz
- get a first glimpse of AI that “already knows how to use your app”
I love doing adopter support calls for @jazz.tools
"No you don't need to do that..."
"This extra indirection isn't necessary..."
"Yes, you can use CoValues as both UI state and the persisted source of truth - you don't need to copy back and forth"
"No you don't need to 'save' "
Discord driven development
Shoutout to @jmsv.bsky.social for the 3h suggestion-to-🚢
Shoutout to @bensleveritt@mastodon.social for the months of gruelling work in the ProseMirror mines that made this a quick win
Nothing better than telling people to edit just their package.json for a 12x perf improvement.
I still think we can do better for this particular hot path internally.
But their app’s “screen of everything” *cold start* is now bottlenecked by React & the DOM!
bsky.app/profile/jaz...