Self-hosted Akaunting
Independent services for Akaunting running on your own server.
Installation, version upgrades, private modules, Turkey localisation, data migration and a maintenance retainer. You buy and hold your own licence at list price, in your own name. We sell labour and judgement, never resold licences.
What this is
Akaunting is a Laravel application. Self-hosting it is a server job, not a download.
It is not the English word "accounting" spelled oddly — it is a specific piece of software: PHP 8.1 or higher, Laravel with Livewire and Vue, Laratrust for permissions, DomPDF for documents. It has opinions about your host. Three facts worth knowing before you commit to it.
- The licence. Akaunting is source-available, not open source — each release converts to GPLv3 four years later.
- BSL 1.1
- Users, companies, invoices: the ceiling on free production use written into the licence's Additional Use Grant.
- 2 · 1 · 1,000
- PHP extensions the install requires — in the CLI binary as well as the web one. Shared hosts routinely miss one of the two.
- 13
We are not Akaunting Inc. We do not resell its licences or its App Store apps, and we do not take a margin on them. You buy those directly, in your own name, which keeps the licence yours and keeps us clearly on the labour side of the arrangement.
Our founder worked on the Akaunting team as a Senior Software Developer from 2018 to 2022, and that is a work history you can look up, not a badge. Nobody here is an "official Akaunting partner", because no such programme exists for implementers. If a firm tells you it is one, ask them for the page.
Akaunting Inc. sells its own dedicated support, priced by response time. We do not try to undercut it. We compete on being reachable in Turkish during Turkish business hours, on knowing what GİB expects, and on being willing to open an SSH session at nine on a Friday evening.
Sound familiar?
The sentences people send us.
Taken from Akaunting's own forum and issue tracker, including its Turkish-language category. If one of these is your week, you are on the right page.
Install, update, server
- The installer stops at step 3 and the log file is empty.
- It tells us to ask our host for PHP 8.1 or higher. We are already on 8.2.
- The one-click update died at 20% and now it says "Not able to download core".
- Every page takes forty seconds and every module reports version 0.0.0.
- Our host has disabled proc_open and proc_get_status for security reasons.
- We restored the database and every invoice attachment was gone.
Turkey, tax, and the day job
- We need e-Fatura. We have no PHP developer and no idea which module to trust.
- There is no tevkifat on the invoice screen and our mali müşavir keeps asking for it.
- The chart of accounts is Anglo-Saxon. We need TDHP codes.
- Half the interface is still English because the paid apps were never translated.
- Recurring invoices simply do not go out, and nothing is logged when they do not.
- We cannot type 100,50 as a price. It saves 100.
Four pages, four jobs
Pick the one that matches your week.
Each is a separate engagement with its own scope, and each page states what is out of scope as plainly as what is in it.
Installation & hardening
Upgrades & rescue
Custom modules
e-Invoicing & Turkey localisation
Where to start
There is a cheap first step, and it is not a sales call.
Five rungs. Most people arrive at rung two or three because something is already broken; the ladder still runs the same way, it just starts in the middle.
The Akaunting ladder
Every rung is a bounded engagement with a written output. You can stop at any of them and nothing you have bought stops working.
- 1Health checkFixed price · 5 business days
A written report: the version you are on and what it is known to get wrong, every installed app and the upgrade coupling it creates, a hosting pre-flight for HTTP and CLI PHP, your backups tested rather than assumed, licence-tier exposure, and an upgrade plan in the order it has to happen.
- 2Installation or server move3–5 days
The right PHP for both HTTP and CLI, TLS, a cron entry proven by test-firing a recurring invoice, SMTP with SPF and DKIM and one invoice PDF delivered to a real inbox, database and storage backups with the restore actually performed once.
- 3Upgrade and rescueFixed price per version jump
Staged copy first, core before apps, snapshot with the rollback rehearsed, then a regression pass on the reports that genuinely break in real releases. Includes the classic incidents: stuck at 20%, a 500 after the update, a half-applied migration, a locked-out admin.
- 4Modules and Turkey localisationPaid discovery, then fixed phases
Built only on documented extension points, so the next upgrade cannot delete your feature. Delivered as a private module in your own repository. Turkey work — e-document connectors, TDHP chart of accounts, tevkifat — is scoped and priced separately, because the risks are not comparable.
- 5Managed maintenanceMonthly, tiered by response time
Monitoring and error tracking, staged upgrades on our schedule rather than yours, verified backups with a quarterly live restore drill, and a monthly written report naming the version installed and what was checked. Exclusions listed as clearly as inclusions.
Akaunting Health Check
The front door. Low risk, fixed price, and it ends in a document you own whether or not you hire us for the fix. Most of what goes wrong later is visible here.
- Your version against the release notes that matter — 3.2.1 fixed an expense being counted twice on the Profit and Loss report
- PHP for HTTP and for CLI, separately, plus all 13 required extensions
- proc_open and proc_get_status, memory limit, max execution time
- Cron: whether recurring invoices and reminders have ever actually fired
- Mail: SPF, DKIM, DMARC, and whether an invoice PDF lands in an inbox
- Backups: database and storage, with a restore attempted rather than assumed
- Licence tier against your real company, user and invoice counts
- An upgrade plan, in the order it has to happen
The licence
Akaunting is not open source, and that changes what anyone can honestly offer you.
LICENSE.txt is the Business Source License 1.1, with GPLv3 as the change licence four years after each release. The Additional Use Grant is the part that decides how a project like yours should be structured — and almost nobody selling Akaunting work in Turkey has read it.
- You buy and hold your own On-Premise licence, in your own name.
- It runs in your own infrastructure account, on a card with your name on it.
- We are a contracted operator with named access, and that access is revocable by you on the same day you ask.
- Before you build on it, we put in writing which tier your company, user and invoice counts actually require.
- App Store apps are bought by you at list price. We never mark them up and never resell them.
We are not lawyers and none of this is legal advice. What we can do is tell you what the clause says and how we structure work around it: the Additional Use Grant limits free production use, forbids stripping out the branding, and forbids running Akaunting as an "Accounting Service" — a commercial offering that lets third parties benefit from its accounting features. That last clause is why we do not host multi-tenant Akaunting for anybody, including accounting practices, and why we will say so on the first call rather than after the contract.
Scope
What we take on, and what we will turn down.
A vendor willing to lose the enquiry is telling you the truth about the rest of the page.
We do this
- Installation, hardening and server moves, on a host you choose and own
- Version upgrades, including a 2.x install that has to reach 3.x
- Rescuing a half-applied update, a locked-out admin, a 500 after an upgrade
- Private, client-owned modules built on documented extension points
- Turkey work: e-document connectors, TDHP chart of accounts, tevkifat scoping, paid-app translation
- A maintenance retainer with a stated response window and a monthly written report
We do not do this
- Managed Akaunting hosting as a product. We set it up on your host and hand you the keys.
- Multi-tenant Akaunting for your own clients. The licence forbids it, and we will show you the clause.
- Reselling Akaunting licences or App Store apps, at a margin or otherwise.
- "GİB compliance" as a promise. We build and maintain the integration; the fiscal opinion is your mali müşavir's.
- Acting as your mali müşavir, or signing off a mizan.
- Rebranding Akaunting by hacking out its branding. That is what the White Label app exists for.
- Fixing the Turkish translation of the core product. It is already complete, key for key with English, and selling you that would be a lie.
How it is priced
Three models, and we tell you which one applies before you commit to anything.
Every engagement is quoted in writing against a scope that says what is out as well as what is in. Where the scope is not visible from outside, an assessment comes first and its fee is credited into the work.
Fixed price, fixed scope
Quoted after assessment
Health check, installation, an upgrade per version jump, a TDHP chart pack, a paid-app translation set. Anything we can see the whole of before we start.
- Written scope with acceptance criteria
- A duration, not a range
- Assessment fee credited into the work
Paid discovery, then phases
Quoted after assessment
Custom modules, e-document connectors, tevkifat work. The discovery is a real deliverable: a written spec with acceptance criteria that you keep whether or not you continue with us.
- Timeboxed and priced separately
- Fixed price per phase after it
- Optional per-release compatibility retainer
Monthly retainer
Quoted after assessment
Managed maintenance, tiered by response time and number of environments. Inclusions and exclusions both written into the agreement, so nobody argues about them at the wrong moment.
- Staged upgrades, core before apps
- Quarterly live restore drill
- A monthly report naming the version installed
Starting prices for these packages are being finalised. Ask on a call and we will give you a number, not a range.
Straight answers
What people ask us on the first call about Akaunting.
Are you an Akaunting partner?
Does self-hosting actually make sense for us, or should we stay on Cloud?
Do we have to buy a paid licence?
Can you just host it for us?
Our install is broken right now. What happens today?
Will you work with our mali müşavir?
Every good build starts with a conversation.
Tell us the process that hurts. We will tell you honestly whether we are the right studio for it — and if we are not, who is.