Akaunting is free, open-source online accounting software for small businesses
akaunting.com
akaunting.com
[1] https://github.com/akaunting/akaunting/blob/master/LICENSE.t...
It's interesting that it will "automatically" switch to GPLv3 in 4 years (as specified in the license).
Would be nice if more closed source software were released with such a license.
Edit: the production Use Grant are atrocious :
> You may make production use of the Licensed Work, provided you do not use it in any of the following ways: (1) Use the Licensed Work with a total of more than two users or one company or one thousand invoices.
> It's interesting that it will "automatically" switch to GPLv3 in 4 years (as specified in the license).
> Would be nice if more closed source software were released with such a license.
And it would be nice if there was a better term than "source available" to describe licenses such as BSL and SSPL, and ideally to differentiate usage grants. GitHub project under BSL with the above very constraining usage grant vs GitLab project BSL with "do whatever you want just don't host to sell to others" vs code with no license thrown on a .zip on an FTP are all "source available".
If you have more than two users you cannot use it in production.
SO it only useful if you have exactly two users.
The SSPL seems far close to being open than the BSL.
I think the problem is that they don't understand the term. Open source is a legal term, with many side meanings, while they seem to be referring only to the fact that the source code is published and therefore is in the open.
It's not really "free" but is also very much "open source," as the source is completely available.
Interesting choice of a TLD. At first I thought it was free (like eu.org) but it seems that it's around $15, so pretty much like other domains. Is there a particular reason you went with .us.org?
What kind of manufacturing do you plan to support? And what does it mean to be specific about support for American manufacturing?
Github link on https://erpnext.com/ goes to https://github.com/erpnext which is pointless.
Actual repo seems to be https://github.com/frappe/erpnext and is GPL-3.0.
I run a manually installed, locally hosted instance. It's not much of a hassle.
Someone should just write a ledger-cli graphical view with the text file as still the primary way to input new data.
Really all I want is an 80s TUI accounting app that "just works" as ledger does but with a menu driven interface with keyboard shortcut support.
Modern stuff like multi-user capabilities, plugins, templates, API etc. wouldn't hurt.
Terrible name but pretty solid product.
Written in PHP.
How do I receive a payment against an invoice?
It isn't free as in software, as both FSF and OSI requires software compatible with their goals to have no limitations on use.
Edit: it seems the on-premise version supports apps: There is no app included in any plan. All apps must be purchased separately from the App Store.
I think the traditional standalone accounting software will be a thing of the past here after the implementation of the new accounting law.
Also cloud based accounting systems are probably easier to make money on.
on premise is the exception
Ledger - https://ledger-cli.org/
So my obvious questions are 1. if it's free, how do they make money / maintain it, and 2. if it's online, how is it kept secure. So...
> That's right, completely free. The Standard plan of the On-Premise (self-hosted) version is free in terms of price and freedom (source code available).
If by "completely free" you mean "with a lot of restrictions, starting with self-hosting" and by "freedom" you don't mean the same thing everyone else means by that (since as everyone else pointed out this is not open source).
Okay, fine, by "free, open-open source online accounting software" they mean "free or online but not both, and source-available". That's more lies than I would want from accounting software, but let's see if they're secure.
From the front page:
> As we talk about your financials, you must be sure that data is in safe and software doesn't abuse them. Open Source software provides you full privacy.
Again, not open source, but source-available does mean auditable. Of course, it doesn't mean privacy-respecting (even real FOSS can expose your data, you can just see that it does and patch it), and it helps but it certainly doesn't automatically mean secure.
Then on https://akaunting.com/plans :
> Is my data safe?
> Completely safe. Our servers are protected physically and electronically. Any connection between you and Akaunting Cloud is protected by 256-bit SSL encryption, and backups are taken hourly, daily, weekly, and monthly.
So, uh. I cannot stress enough how much that would not reassure me. No mention of at-rest encryption, no audits, no reason to think they aren't hosting the thing on servers that never get security patches. "We use HTTPS and take backups" is something but it's the bare minimum for any paid SaaS, not something to brag about and nowhere near good enough for something with all your financial information.
"We are secure because we use HTTPS, not HTTP" is rather 1994 more than 2024.
(Although it's worth noting that that's not the biggest limitation either, just the one that stuck out to me when I wrote the comment)
and to save you few click, it uses PHP as the underlying platform and language
Then you get to watch the mountain of errors and ridiculous amount of time wasted.
PHP pays the bills and these days has fewer novices writing utter junk, that's a plus in my book!