Latest User Testimonial
Latest flowlog News
Issue with flowlog.net? Is flowlog missing a critical feature? Something else?
Documentation -> Design Goals
In this page we'd like to outline the general design goals of flowlog, in random order, so that people can get a sense of the aims and likely direction of the project. Some of this will repeat the features/home page but we wanted to have these clearly listed in the docs.
Ease of Use - Small business/org/beginner friendly
flowlog will try to use the simplest, most intuitve solution that meets the needs of our target member/user base. This has several advantages, like being easy to quickly understand for the user and easier to develop/modify for developers.
Lightweight and quick to use
flowlog will try to provide flexibility without addding complexity and/or bloat. flowlog will abstain from using fat frontend frameworks, millions of ajax calls (currently zero), third party remote resources or anything else that will threaten flowlog.net/flowlog's ability to be fast and responsive.
As Secure as Possible
flowlog will prioritize security to the highest degree we find feasible for our operating environment and target use case. Any known limitations/concerns/recommendations will be disclosed in these docs and the source is always there for review by annually supporting members along with the option to self host if flowlog.net's security methods or environment are still not suitable for your use case.
Privacy and Freedom Respecting
flowlog will always be for members who care about their privacy and freedom. We never need to know the real identity of flowlog.net members and flowlog will always be licensed under the AGPLv3
flowlog will always strive to be affordable for small orgs and one person operations just trying to get started keeping their books. This is what flowlog was made for.