1. Open source-first: Papermark is 100% open-source and open to contributions. Host it yourself, fork it, modify it to your desire! Document infrastructure as never been so open and accessible!
2. Fully customizable: you can use custom domains to share a pitch deck or documents and custom branding.
3. Real-time analytics: we use Tinybird's Clickhouse under the hood to enable real-time analytics. We will also add more advanced analytics like heatmaps.
4. AI-driven: this is very much in experimentation, but we aim to add create specific usecases like creating summaries, memos, asking the document questions to Papermark.
To your second question, we are working on a clean REST API that developers can use to access the full suite of Papermark programmatically. This will enable new usecases and integrate much better with existing applications and tools. We are still looking for design partners before we launch it.
Papermark is providing you actionable insights for your files. Just like you have Mixpanel or Datadog for your application, there is Papermark for your files.
Let me know if you have any questions and if you're a developer, how you feel about deeper integrations with your tech stack / apps.
Hi HN! We’re Marc and Iuliia from Papermark (https://papermark.io). We're building an open-source, modern document sharing platform with real-time engagement analytics and 100% customization.It all started as a tweet [1] and led to our launch on Product Hunt [2] last month. We crossed over 1000 stars and over 10 contributors on GitHub (https://github.com/mfts/papermark).Incumbents, like...
The big BUT is that software needs to be maintained whereas a video once uploaded on YouTube doesn‘t need to be edited again.
I have a feeling that Birk and the Polar team have the right insights to build the right tools to serve the specific needs of open-source software maintainers.
tea/gui is fully open source and available on GitHub.
We will be adding more capabilities like actions (turn postgres into a service), scripts store and more.
tea.xyz will not have fees once it goes live with its funding protocol for open-source software.
The user journeys are documented as screenshots and are available for free. Included are pre-built templates that replicate said user journeys in the Marbleflows platform.
Marbleflows makes it dead simple to create flows for user onboarding and other use cases.
I honestly believe that understanding the entire dependency graph of open source project will help redistribute money to all packages democratically.
I’m curious to hear what other devs think
In the end for open source to be open source it should be publicly accessible.
Anything else should be defined in the license as the maintainer/creator wishes.
It's a quick code and deploy walkthrough
I was so excited I made a video about it and shared my thoughts on why and how GitHub should integrate this. https://youtu.be/kfOimInsnr4
I made this walk-through video of the project inclusive the deployment to Vercel and Railway:
I made a quick video to explore the open source project https://www.youtube.com/watch?v=TaIQhG8AL0w
Prisma is the unbundled version of Graphcool.
Graphcool's main selling point was that everything was hosted: "The Parse for GraphQL".
Prisma's main selling point is that you can host your own database wherever you want and Prisma generates the Schema and TypeDefs for you based on CRUD operations. Compared to Graphcool, you get one instead of two endpoints (Relay and Simple API endpoints are the same in Prisma). Now you can connect your client directly to the Prisma endpoint or you build a GraphQL Server (with graphql-yoga or apollo-server) between your client and database.
All resolvers (auth, file hosting, etc) are written on this GraphQL Server level.
Prisma is a lot more flexible and now also bigger enterprises with legacy databases can use them more easily.
Hope that answers your question. Again, I don't work there but really like their product.