r/usefwd • u/ArchonMegalon • Aug 06 '25
GitHub?
So... Is there a way to contribute? What language are U using? Talking about privacy: Will we be able to self host the backend?
3
Upvotes
r/usefwd • u/ArchonMegalon • Aug 06 '25
So... Is there a way to contribute? What language are U using? Talking about privacy: Will we be able to self host the backend?
2
u/findhamza Aug 06 '25
Hey u/ArchonMegalon, thank you for the excellent questions! This gets to the heart of the project's philosophy, so I'm happy to clarify.
Let's go through them one by one.
On GitHub & Contributing: We've had a few questions about this! For now, the core fwd: applications will be closed-source. This is a strategic decision to ensure we can focus on building a reliable and sustainable service funded by the future Pro plan, rather than getting stretched too thin managing a large open-source project in these critical early days. That said, the most valuable way you can contribute right now is by being an active member of this community and our beta. Providing detailed feedback, reporting bugs, and suggesting features from a developer's perspective is incredibly valuable.
On the Tech Stack: Great question! The goal is to deliver a consistent, high-quality experience on all platforms. We're doing this with a modern, unified tech stack:
Backend: Node.js, written in TypeScript.
Desktop & Mobile Apps: The apps share a modern codebase built with TypeScript and React.
Browser Extensions: Also built with TypeScript.
On Self-Hosting the Backend: This is a fantastic question that gets right to the core of privacy and data control. Our primary approach to privacy is through strong End-to-End Encryption (E2EE). As we've discussed in other threads, the server is designed to be a "dumb router" for encrypted blobs of data. It never has access to the unencrypted content of your notifications, clipboard, or files. Because the server can't see your data anyway, the need to self-host for privacy reasons is significantly reduced. Given this E2EE-first approach, and to ensure we can offer a simple, maintenance-free, and sustainable service, we aren't planning to offer a self-hosted version at this time. This allows us to focus all our efforts on making the hosted version as reliable and secure as possible for everyone.
Thanks again for the great questions—this is exactly the kind of discussion I was hoping to have here!