Accounting
Invoices and books on your own instance
Deploy Akaunting with managed MariaDB and a public HTTPS URL. You own the instance. You pay for compute — not per invoice.
TemplatesAkaunting
What you get
A private Akaunting, packaged to ship
Invoices, expenses, and reports on your instance — MariaDB and the public URL are wired at deploy.
Invoices and bills
Send invoices and record bills from the admin. PDFs and logos stay on this instance.
Expenses and reports
Track money in and out, then read the reports from the same company workspace.
Admin on first boot
Set ADMIN_EMAIL and ADMIN_PASSWORD before deploy. First boot seeds that user and skips the web installer.
Dedicated instance
Customers, invoices, and files stay on this instance — not in a shared vendor account.
Public HTTPS URL
APP_URL is your https://…stackblaze.app hostname so links in invoices resolve.
Managed MariaDB
The company ledger lives in MariaDB. Akaunting does not run on Postgres. Uploads persist on a volume.
Deploy in seconds
One click. MariaDB pre-wired.
Pick the Akaunting template. StackBlaze creates the app and MariaDB, sets the public URL, and gives you a hostname.
This stack
Web
Akaunting server
MariaDB
managed database · TCP:3306
Tenant
managed other
platform SMTP when the pipeline has mail
- Stack
- Akaunting + MariaDB
- First login
- ADMIN_EMAIL and ADMIN_PASSWORD you set before deploy
- Address
- HTTPS hostname is already APP_URL
After you deploy
- 1
Set the admin password
Replace ADMIN_PASSWORD before you deploy. The placeholder is not a password you should keep.
- 2
Open the public URL
The hostname is on the app page after deploy. The web installer is already bypassed.
- 3
Sign in and rotate it
Log in with ADMIN_EMAIL and ADMIN_PASSWORD, then change the admin password. Uploads live under the storage volume.
Running Akaunting on StackBlaze
How the instance is wired
Akaunting and MariaDB ship together. The public hostname is the app and the links in your invoices.
MariaDB holds the ledger
Invoices, customers, and reports live in the attached database. Restart the app and the books are still there.
Files sit on a volume
Uploaded files, generated PDFs, and logos persist under /var/www/html/storage. The database is not a file store.
One URL for the company
APP_URL is the public hostname. Attach a custom domain from the dashboard when invoices should use your domain.
Add CPU when reporting gets heavy
Raise RAM and CPU on the app from the dashboard. MariaDB scales on its own.
Compare
Akaunting on StackBlaze vs hosted accounting
| Feature | Akaunting on StackBlaze | Hosted accounting |
|---|---|---|
| Data location | Invoices, customers, and files live on your StackBlaze instance. | Books live in vendor-operated infrastructure. |
| Install model | One-click template. Admin is created at deploy. | Create a vendor account and use their shared platform. |
| Customization | Your company, your locale, your domain. | Limited to the host’s plan and modules. |
| Operations | You control updates, scale, backups, and the instance lifecycle. | The vendor operates the platform and the limits. |
| Billing | Compute, storage, and bandwidth. No per-invoice fee. | Usually priced per company or per plan. |
This template is Akaunting plus MariaDB. The admin is seeded from the env you set.
FAQ
Common questions
Open the public URL and sign in with ADMIN_EMAIL and ADMIN_PASSWORD. Set a real ADMIN_PASSWORD before deploy — the placeholder is intentionally weak. Change the password after the first login.
Ready to deploy Akaunting?
One click. Dependencies pre-wired. No infrastructure to manage.