Workbase Server
| Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
|---|---|---|---|---|---|---|---|---|---|---|
| Workbase Server | 286 | 2 years ago | 9 | gpl-3.0 | Java | |||||
| Slack alternative, email integrated, build with Meteor | ||||||||||
| Ground Control | 190 | 8 years ago | 1 | mit | CSS | |||||
| A next generation blog, built in Meteor. | ||||||||||
| Meteor Emails | 95 | 5 years ago | 9 | November 29, 2016 | 17 | mit | JavaScript | |||
| Improved Meteor emails with templating, previews and automated CSS/SCSS inlining. | ||||||||||
| Latelier | 86 | 2 months ago | 7 | apache-2.0 | Vue | |||||
| L'atelier, a project management tool | ||||||||||
| Meteor Emails | 82 | 2 years ago | 2 | mit | JavaScript | |||||
| Send cold emails for free! Completely free and open source project to fight against sales stagnation in your company | ||||||||||
| Meteor Accounts Passwordless | 50 | 7 years ago | 1 | May 13, 2015 | 3 | mit | JavaScript | |||
| Passwordless for token-based one-time password (OTPW) authentication | ||||||||||
| Gh Release Watch | 45 | 8 years ago | 6 | mit | JavaScript | |||||
| Watches github repositories for new tags, and lets you know when they are released | ||||||||||
| Angular Meteor Boilerplate | 38 | 8 years ago | 1 | TypeScript | ||||||
| Full Featured Angular Meteor Boilerplate | ||||||||||
| Meteor Pretty Email | 38 | 7 years ago | 3 | October 22, 2015 | 11 | HTML | ||||
| Pretty emails for meteor | ||||||||||
| Sandcats | 31 | 3 years ago | 25 | other | JavaScript | |||||
| Services for Sandstorm self-hosters: Dynamic DNS & HTTPS certificates | ||||||||||
WorkBase is an open source, private cloud message service.
It's based on email protocol which means it can connect anyone with an email address.
Mobile App
Bring your own server
You'll have the following features and even more
- Emails
- Chats
- Groups
- Channels
- Mobile App
Why WorkBase
Source: COI - Chat Over IMAP
Most popular messaging services are currently proprietary, closed and operated by single providers. This leads to several problems:
Privacy
The provider knows all about your social network: when you communicate with whom, the frequency of your communication and the number, type and length of your messages – even with end to end encryption in place.
Unfair competition
Service providers depend on the rules set by the messaging owner and access to the API for participation. If the messaging provider changes the rules or API, you are out of luck and must adapt fast.
Lock in
Users cannot simply change to another provider; all their friends and peers are on that popular service. If they want to switch, they would need to convince all their friends to join the new service too. Other side effects are they would lose all their conversation history, if they dare to move away. Also, if you don’t like the new app version? Bad luck, you cannot go anywhere else!
Silo
Each network is closed and the users in that network are isolated. This means restricted movement between silos, no new innovation outside the controlling power, no new players, no resistance to attacks (single source code) and it simply goes against the philosophy of the internet: freedom, innovation and growth around the use of common standards.
Closed Ecosystem
The network is only controlled by a single party, you cannot start hosting your own WhatsApp, WeChat or FB Messenger Service.
No Choice
Some large providers, like Facebook, control many of the popular messaging apps, like WhatsApp and Facebook Messenger making it feel like there is no real choice.
