Show HN: Briefer – Multiplayer notebooks with schedules, SQL, and built-in LLMs
Hi HN! We&#x27;re Lucas and Lucas from Briefer and we&#x27;re building better notebooks.<p>Our notebooks are kind of a mix between Notion and Jupyter with extra features, like the ability to schedule notebooks, turn them into dashboards and apps, and write SQL queries whose results turn into data frames automatically.<p>We&#x27;re building better notebooks because we think they&#x27;re a great idea poorly executed - for three reasons.<p>The first problem with notebooks is that they&#x27;re difficult to share. Non-technical people don&#x27;t want to download docker containers and install Python libraries to see what the data team is doing. Then, the data team takes screenshots of their work and pastes them somewhere else. The issue with this approach is that the data gets stale, and the output is not interactive, so it&#x27;s difficult to get feedback and iterate.<p>The second problem with notebooks is that they get too messy too quickly. One morning you have 10 blocks, and by the end of the day you have 192, but only six of them are meant to be seen by other people and the rest is just you jiu-jitsuing with the data. Consequently, even if non-technical people could see your work, they&#x27;d have a hard time figuring out what&#x27;s happening.<p>The third problem with notebooks is that it takes too much work to do simple things like when you want to query a database. In that case, you need to have the database credentials in your machine, and you have to write a bunch of wrapper code. Calling APIs, plotting simple graphs, and adding interactive components is equally as annoying.<p>We&#x27;re solving the sharing problem by bringing notebooks to the cloud (so you can schedule them) and using CRDTs to manage their state. Whenever you edit a Briefer notebook, we reconcile that using Yjs, and then propagate it to everyone else who&#x27;s editing that notebook. Regarding compute instances, each workspace gets its own, and we provision them on demand.<p>By the way, we manage the execution state of your blocks using Yjs too, which makes it much more stable and responsive across all clients. When you click &quot;run&quot;, for example, we don&#x27;t immediately send a request to run the block. Instead, we change the block&#x27;s state to &quot;execution-requested&quot;. Then, the observers in the back-end react to the change and update the block&#x27;s state with the results. In other words, the front end and the server communicate with each other through the notebook&#x27;s state. One side updates the state, and the other reacts.<p>To solve the &quot;messiness&quot; issue, we&#x27;ve invested a lot of time in designing clean notebooks and allowing you to organize blocks in ways that make them more presentable. In Briefer, you can group multiple blocks into tabs and decide which blocks appear in the published version of your notebook. That way, you can hide all that data wrangling and focus on results. We also know that a vertical format is not always the best way to display results, so you can use your notebook&#x27;s outputs to build dashboards too.<p>Last but not least, we&#x27;re reducing friction in simple tasks like plotting graphs and querying databases. In Briefer, you can plot graphs using a click-through interface, and if you need to plot something more intricate like a Sankey chart there&#x27;s also a built-in AI assistant that you can prompt to generate code. When it comes to queries, we turn their results into dataframes automatically, and you can use SQL to query uploaded files too (we use DuckDB for that).<p>We&#x27;re really happy we get to show this to you all, thank you for reading about it! Please let us know your thoughts and questions in the comments.