Your own infrastructure
The application runs on your servers. You decide on location, backup strategy and maintenance windows.
Data protection
On-premise: tenant data that never leaves your house
A handover report holds names, signatures and photographs taken inside private homes. If you would rather not hand that to a cloud provider, run the solution on your own servers with the same functionality.
- Runs entirely in your own data centre
- No data processing agreement with a cloud third party
- No transfer outside the EU
- Connects to internal databases and Active Directory
- Full control over retention and deletion
- Quoted individually according to scope
The difference in numbers
100 %
of data kept in your own house
0
external processors in the chain
Quote
based on scope rather than per user
Cloud or your own house, honestly weighed
The online edition is the faster route. It is usable immediately, billed per user and month, and somebody else looks after operation, backups and updates. For many organisations that is exactly right.
On-premise is more work. It needs servers, it needs someone to look after them, and adoption is a project rather than a sign-up. In return you get something a cloud product fundamentally cannot offer: the data sits with you.
We put it this plainly because both routes are legitimate. The question is not which is better but which fits your organisation. If you have no in-house IT, do not run on-premise. If you will not release tenant data outside the building on principle, do not go to the cloud.
What a handover report actually contains
It is worth being concrete. A handover report holds:
- Names and addresses of tenants, sometimes with contact details
- Signatures from both parties, which sit close to biometric data
- Photographs taken inside private homes, where personal belongings may be visible
- Meter readings, from which conclusions about daily habits can be drawn
- Contract details and information about the tenancy
Taken together that is a considerably more sensitive record than, say, a maintenance report on a building. Which is why the question of where data lives is sharper for handover reports than for most other mobile applications.
The legal frame
With a cloud product the provider becomes a processor. That requires a contract under Article 28 GDPR, an assessment of the technical and organisational measures, and where the provider sits outside the EU an additional safeguard for the transfer. All of it is workable, but it is work that has to be reviewed regularly.
Running in your own house removes that chain. There is no external processor because nobody but you has access. You remain the controller, without an intermediate step.
That is what we mean by "can be operated in a GDPR-compliant way". The software makes an architecture possible in which the data protection question is solved structurally. Whether the actual operation is compliant still depends on your processes. No software vendor can guarantee that, and anyone who claims otherwise is promising too much.
Scope and price
Unlike the online edition, on-premise is not billed per user and month but quoted individually on request, because the effort depends heavily on your environment.
Relevant factors include the number of users, the forms required and how complex they are, the type and scope of the database integration, the Active Directory connection, and any requirements around high availability and backup.
That is why an on-premise project starts with a technical conversation rather than a price list. A figure only makes sense once it is clear what is actually needed.
Why organisations choose it
GDPR by architecture
What never leaves the building needs no contractual safeguard. That is the more robust of the two options.
Full data sovereignty
You decide who has access, how long records are kept and when they are deleted, with no provider in between.
Short path to the database
Integration with Oracle, MS SQL or MySQL happens inside your own network, with nothing opened to the outside.
Your security policy applies
Your rules on network segmentation, access and logging continue to apply unchanged.
Predictable updates
Updates follow your schedule rather than a vendor's release calendar.
Frequently asked questions
What server environment is required?
That depends on user numbers and requirements and is clarified in the technical pre-discussion. The solution runs in common data centre environments; the specific requirements for operating system, database and sizing are matched to your existing infrastructure.
Do the mobile apps still work with on-premise?
Yes. The iOS and Android apps talk to your server rather than to a cloud. Offline capture with automatic synchronisation works unchanged, with devices syncing as soon as they can reach your server.
Who handles maintenance and updates?
Operation sits with you, provision of updates with us. How closely we accompany that, from pure delivery through to agreed maintenance services, is part of the quote.
Can we move from online to on-premise later?
A move is possible in principle and does happen in practice, for example as an organisation grows or data protection requirements tighten. The effort depends on the volume of data and the forms in use, and should be discussed beforehand.
Does on-premise make us automatically GDPR-compliant?
No. On-premise removes the questions around processing agreements and international transfers, because no external processor is involved. Your own obligations remain fully in place: records of processing, a deletion concept, access permissions and informing data subjects.
Let us talk about your environment
On-premise starts with a technical conversation, not a contract. We look at what you have and say honestly whether it fits.