Finance
Run OpenBooks Accounting on your own instance
Keep a double-entry ledger, invoices, bills, and reports for a small business. OpenBooks on Postgres. This is the bookkeeping app, separate from the OpenBooks Financial ERP template. You own the instance. You pay for compute — not a vendor plan.
TemplatesOpenBooks Accounting
What you get
A private OpenBooks Accounting, packaged to ship
OpenBooks Accounting on your instance — PostgreSQL, and the public URL are wired at deploy.
Dedicated instance
Keep a double-entry ledger, invoices, bills, and reports for a small business.
Public HTTPS URL
The hostname is on the app page after deploy. Open it to finish setup. Attach a custom domain when you want a branded address.
Managed dependencies
PostgreSQL ship with the template. You do not install them yourself.
Your accounts
The first login is created on this instance. Invite the team from inside the app.
Deploy in seconds
One click. Dependencies pre-wired.
Pick the OpenBooks Accounting template. StackBlaze creates the app, PostgreSQL, and gives you a hostname.
This stack
Web
OpenBooks Accounting server
PostgreSQL
managed database · TCP:5432
- Stack
- OpenBooks Accounting + PostgreSQL
- First login
- Finish the first-run steps on the public URL
- Address
- HTTPS hostname is ready at deploy
After you deploy
- 1
Open the public URL
The hostname is on the app page after deploy.
- 2
Finish first-run setup
Builds https://github.com/stackblaze-adam/open-accounting from main with the repo Dockerfile.
- 3
Use your own domain when you are ready
The stackblaze.app hostname works immediately. Attach a custom domain from the dashboard for a branded address.
Running OpenBooks Accounting on StackBlaze
How the instance is wired
OpenBooks Accounting and PostgreSQL ship together. The public hostname is the app.
The app is the public URL
Editor, login, and callbacks share the hostname StackBlaze assigns. A custom domain replaces it without a rebuild.
Dependencies stay attached
PostgreSQL are part of this template. Restart the app and the data store is still there.
Scale from the dashboard
Raise RAM and CPU on OpenBooks Accounting when it gets busy. Attached databases scale on their own.
You operate the instance
Updates, backups, and the lifecycle are yours. There is no vendor seat cap on this template.
Compare
OpenBooks Accounting on StackBlaze vs a hosted plan
| Feature | OpenBooks Accounting on StackBlaze | Hosted plan |
|---|---|---|
| Data location | OpenBooks Accounting data lives on your StackBlaze instance. | Data lives in vendor-operated infrastructure. |
| Install model | One-click template. First account on the public URL. | Create a vendor account and use their shared platform. |
| Customization | Your instance, your settings, your domain. | Limited to the host’s plan and runtime rules. |
| 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-seat fee. | Usually priced per seat, task, or plan. |
This template is OpenBooks Accounting + PostgreSQL.
FAQ
Common questions
Builds https://github.com/stackblaze-adam/open-accounting from main with the repo Dockerfile.
Ready to deploy OpenBooks Accounting?
One click. Dependencies pre-wired. No infrastructure to manage.