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. flowlog also had an Autonomous Encryption feature that allowed users to encrypt their books with a key only they knew. ITwrx could not be compelled to turn over user's flowlog info, b/c we didn't have the users' keys. They could also pay with Monero and use a VPN to access their instance of flowlog. This may sound over-the-top, but we just wanted potential users to be able to use a web application for their books, while still retaining their privacy/data security.
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 create 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 (Disabled. Currently migrating hosting infrastructure and preferring sqlite these days) 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.
We hope to get time to update the Laravel framework and/or application code, or port the application to another stack, 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 project with no revenue to speak of. We leave this page up (for now) to show the work that we are still proud of, nonetheless.