flowlog
flowlog is a double entry bookkeeping and accounting web application focusing on power through flexibility, while maintaining maximum ease-of-use. The public beta was released in q1 2019. It requires users to learn a small amount about setting up their books and accounts, but is then able to perform all accounting and reporting tasks with only basic transaction information provided by users.
Privacy was also a major inspiration for it's somewhat novel design, as users don't have to enter all their customers' and vendors' info into some "cloud" application. They could make their books' accounts pseudo-anonymous, while still getting all the accounting precision they need.
Many bookkeeping application either require you to enter your whole business into their proprietary application, probably with subjugating EULA/Privacy Policies, or they don't do much beyond showing invoices and totals by timeframe.
flowlog is a multi-user application with multiple orgs/books per flowlog account holder, with an organization's users addable per set of books, with different group permissions available. You can creat a auditor account for your CPA, for instance, that only allows viewing, but not changing your books/accounts/transactions. It was designed to be flexible enough to handle disparate organizations' bookkeeping/accounting needs without adding complexity or configuration.
ITwrx also wrote the forum, Knowledgebase(docs app code), live demo for trying flowlog out, and issue tracker applications/features used in the flowlog.net website.
The flowlog.net site/flowlog application is currently frozen(no new user registration and no development) because there was minimal adoption and ITwrx added billing features (which allowed creating and sending invoices, and getting paid on your own org's flowlog.net invoice page with either USD via paypal or cryptocurrency) but Paypal changed what methods were available for applications to use and the cryptocurrency exchange we used had to stop accepting business from US customers due to regulatory uncertainty. We could update the billing to use Stripe, and either drop, or self-host the Crypto Currency part, but that would mean more unfunded work, so it hasn't happened. Also, keeping the Laravel framework base of flowlog up to date became onerous with few users justifying the effort.
flowlog also had a somewhat unique funding model that we were hoping to get feedback on. The idea was for a commercial FOSS appplication where users made a small donation every month that paid for their hosting account on flowlog.net and gave then direct access and influence over the project via the issue tracker, in-app contact form, direct and community support through the forum, etc. all while respecting users' privacy and freeedom. We never actually charged for flowlog.net usage, because it was free for the first 100 users during the beta, and we never moved past that stage. flowlog even had an optional feature to encrypt an org's books' data with a key only they knew. ITwrx would not have this key, and could not decrypt their data nor be compelled to release that data. This was to provide maximum privacy for those that preferred it, while still using a "Cloudy"/remotely hosted web application.
There are videos in the support section of flowlog.net if you want to see it in action.
We hope to get time to update the Laravel framework and/or application code(we've learned a lot since then, hopefully) and release the source code in case anyone wants to use or continue development on flowlog, but it's hard to find time to donate for that effort when we already spent over a year on the whole project for no financial recompense. We leave flowlog.net up to show the work that we are still proud of, nonetheless.