Bella Pre-Accounting is priced on three variables: how many people work in it at once, whether the installation runs on your own server or on one we provide, and how much help you need migrating existing data. There is no published list price; every installation is quoted individually.
Last updated:
The product runs one installation per company, and that installation lives either on your server or on ours. Those two models do not cost the same — in one, the hardware and backups are yours; in the other, they are ours. A three-user installation and a twenty-five-user one do not carry the same support load either. A single published number would be wrong for at least one of them.
There is no technical user limit, and each user is granted exactly the actions they may perform. The price is set by how many people work in the system.
A user who only reads reports and one who issues invoices both count as users — but their permissions differ.
Two options: your own server, or one we provide. On your own server the database and the backups stay entirely with you, and so does server maintenance. On ours, maintenance and backups are on us, and your data still sits in a database of its own.
In both models your data lives in your own database, never in a pool shared with other companies.
Customer and product lists import from CSV — that is routine. Opening balances, carried-over account movements and open invoices need hands-on work, and the scope depends on how much data you have.
If you are starting from scratch, this item disappears.
| On your server | On a server we provide | |
|---|---|---|
| Where the database lives | On your server | On ours, in a database of your own |
| Responsibility for backups | Yours (steps are documented) | Ours |
| Server maintenance and updates | Yours | Ours |
| Installation method | One Docker Compose command | We install it; you start using it |
| Physical access to the data | You only | Hosting provider and us |
| Database shared with other companies | No | No |
If you run several companies, each runs in its own installation — a direct consequence of the single-installation design, not an extra restriction.
If you do not want to run a server, the installation we provide is less work. Your data still sits in a database of its own.
Installing on your own server means the database and the backups stay entirely with you. Docker Compose brings it up in one command, and backup and restore are documented.
Each client runs in its own installation, so data never mixes. At period end you pull the report pack from each installation separately and lock the period.
Installing on your own server keeps financial records off third-party infrastructure entirely. The audit trail and security log stay in the same database.
The price is set by user count, but the product is not split into feature tiers: whatever you pay, every module is open. The difference between users is not price but permissions — each user is granted only the actions they need.
There is no technical user limit, so adding people does not stop the system. Commercially, the quote is revised when the user count changes; how that works is written into the contract.
The software is the same. The difference is who carries hosting and maintenance. On your own server, hardware, backups and updates are yours. On ours, that work is ours and its cost shows up in the quote.
No. The product is designed as one installation per company, and companies run in separate databases. Two companies need two installations. This is a deliberate choice so that data cannot mix.
Fill in the demo form. If you mention your user count, whether you want it on your own server, and whether you have existing data to migrate, we can talk about a concrete number in the first call.
Tell us your user count and where you want it to run, and we will put a quote together.
