Self-hosted or cloud?
Running it yourself means the database and the backups stay with you — and so does server maintenance. In a shared cloud service maintenance sits with the provider, but your data usually lives in the same database as other companies, separated by row-level filters. The decision comes down to which burden you would rather carry.
Last updated:
Side by side
| On your own server | Shared cloud service | |
|---|---|---|
| Who holds the database | You | The provider |
| Data isolation | Physical — a separate database | Usually logical — shared database, row filters |
| Responsibility for backups | You | The provider |
| Server maintenance and updates | You | The provider |
| If the service ends | The data stays with you | Depends on export terms |
| If the internet drops | Can run on the local network | Access stops |
| Up-front effort | Higher | Lower |
Why isolation matters
The common pattern in multi-tenant cloud products is that all customers share one database and records are filtered by a tenant identifier. It lowers operating cost, but isolation then depends on the software behaving correctly: a single query missing its filter can surface another company’s record. With a separate database that possibility does not exist, because the record is not there to find.
Self-hosted does not automatically mean safer
Taking the data onto your own server means taking on its security: updates, backups, access control and physical security become yours. A local server whose backups are not run regularly is riskier than a well-managed cloud. The useful question is not “which is safer” but “who carries this responsibility better”.
A middle model: single installation, hosted
There is a third option: the software runs as a single installation with a database of your own, while the provider manages the server. The shared-database problem disappears and server maintenance is not yours. Bella Pre-Accounting supports this model too; which you pick is a commercial and operational decision.
How this product handles it
- Every customer runs in their own installation and their own database — never a shared pool
- It can be installed on your own server; one Docker Compose command brings it up
- Even when we host it, the database still belongs to a single business
- Backup and restore steps are documented
Where it does not fit
Because the product is designed as one installation per company, several companies cannot share one installation. If you want to manage many small companies from a single panel, this design creates extra work for you.
Frequently asked questions
What do I need to run it on my own server?
A server that can run Docker is enough; the installation comes up with one command. Keeping the server patched, running backups and controlling network access become your responsibility — those steps are documented.
Does it work without an internet connection?
If it is installed on your own server and users are on the same local network, it keeps working when the external connection drops. If we host it, access depends on the internet.
Can I switch models later?
Yes. The database is portable, so moving from your own server to hosting or the other way round is possible. How the move would be done is discussed during setup.
Request a demo
See the product with your own data. Fill in the form and we will get back to you.