On-premise deployment

On-premise customer feedback platform for enterprises and governments

Q: Is the on-premise edition the same product as the cloud?

Yes. Survey builder, kiosks and devices, QR, SMS, email and web channels, closed-loop tickets, customer profiles, analytics and AI reports are all included. Nothing is removed for self-hosting.

Q: Can Qmeter run in an isolated network without internet access?

Yes, with two notes. SMS and email are sent through gateways you approve inside your network, and AI features, which use an external model on the data structure only, can be switched off. Everything else runs without an internet route.

Q: Does the vendor have access to our installation?

No standing access. There is no inbound connection from Qmeter. When you need support or an update, you grant access for that work in the way your policy allows, and you can revoke it afterwards.

Q: How are updates delivered?

As versioned releases with release notes. Your team installs them in your staging, approves, and schedules a production window. Nothing changes in production without your decision.

Q: Who handles backups and disaster recovery?

Your team, under your existing policy, because the database and files are yours. We provide the requirements and the restore procedure for the platform.

Q: Who can see personal data?

Only users with the right permission. Email and phone are masked in the interface by default; revealing them requires a permission and writes an audit event. Roles and per-branch permissions are managed by your administrators.

Q: Can it connect to our CRM, ITSM or data warehouse?

Yes. Because the platform runs inside your network, the API and integrations reach internal systems directly, without exposing them to the internet. See integrations and API.

Q: Do you support single sign-on and directory integration?

Identity and access requirements are reviewed in the technical call and scoped per deployment. Role-based access and per-branch permissions are built into the platform.

Q: How do we start, and how is it priced?

Start with a technical call for your IT, security and CX leads. You receive the architecture, requirements and controls in writing for your review. On-premise is part of an Enterprise agreement, priced per project; the cloud pricing is public for comparison.

Qmeter can be deployed entirely inside your own infrastructure: application, database and every survey channel run in your data centre or private cloud, behind your firewall, under your security policy. Customer data never leaves your network, and the platform is the same as our cloud edition, with nothing removed.

For organisations whose law, regulator or internal policy decides where customer data may live: government bodies, banks and insurers, healthcare groups and operators of critical infrastructure.

Security and GDPR details

30 minutes with your IT, security and CX leads. We bring the architecture and requirements in writing.

1000+companies use Qmeter

2M+feedbacks collected

17+years in customer experience

IT director and head of customer experience talking in a glass-walled data centre corridor

Definition

What on-premise means for a feedback platform

An on-premise feedback platform runs inside the customer's own infrastructure instead of the vendor's cloud. Surveys, answers, comments, customer records and audit logs are stored and processed where the customer decides.

Data residency: the database sits in your country and your facility.
Network control: no inbound connection from the vendor; access only when you grant it.
Full product: the same platform as the cloud edition, not a reduced version.

How the cloud edition protects data: security and GDPR.

Two ways to run Qmeter: the vendor cloud, or on-premise inside the customer's own data centre or private cloud

Fit check

Is on-premise the right choice for you?

An honest answer before you book a call. Most organisations run Qmeter in the cloud; on-premise is for the cases below.

A strong fit when

A law, regulator or internal policy requires customer data to stay in your country or your data centre.
Customer-facing systems may not run on external SaaS, or the network is restricted or isolated.
The platform must reach internal systems that are not exposed to the internet: CRM, ITSM, data warehouse, your own SMS and email gateways.
Your security team needs to review architecture, access and controls before anything goes live.
You have an IT operations team that runs servers and change management.

Not the right choice when

There is no team to run infrastructure. The cloud edition gives you the same product without operations work.
You need to be live this week. On-premise follows your procurement, security review and infrastructure timeline.

How a deployment runs

From a policy requirement to a platform your team operates

Four stages. Each one produces a document your IT and security teams can review and sign off.

Architecture and requirements

On a technical call we map the platform to your environment: application servers, database, survey channels and integration points, all inside your network. You receive the requirements and sizing in writing.

On-premise architecture: kiosks, QR, SMS, web and API feeding the Qmeter platform and the customer's database, all inside the customer network

Security and privacy review

Your security team reviews the controls: encryption in transit, role-based access with per-branch permissions, masking of personal data, audit log, retention and deletion rules. Backups and disaster recovery follow your own policy.

Security and privacy controls inside the customer network: encryption in transit, role-based access, PII masking, audit log, retention and deletion, backups under the customer's policy

Installation and internal integration

The platform is installed with your IT team on your servers or private cloud. CRM, ITSM, data warehouse and your own SMS and email gateways are connected inside the network, without an internet route.

Internal integrations: Qmeter connected to CRM, ITSM, data warehouse and the customer's own SMS and email gateways without an internet route

Operation and updates

Your team operates the platform. Releases arrive with release notes, go through your staging and your approval, and are installed in a production window you choose. Vendor access happens only when you grant it.

Release process for on-premise: release notes, the customer's staging, the customer's approval, then a production window on the customer's schedule

Where it runs

Who requires on-premise

Four kinds of organisations where the location of customer data is decided before the platform is.

Citizen feedback terminal in a public service hall

Government and public sector

Data sovereignty rules and national data centres. Citizen records stay inside the state's infrastructure.

Public sector →

Customer feedback tablet at a bank teller desk

Banks and financial services

Regulated customer data, segregated networks and audit requirements from the regulator.

Financial services →

Patient feedback kiosk in a clinic reception

Healthcare groups

Patient data kept under the same governance as the medical record, in the same facility.

Healthcare →

Smiley feedback terminal beside the tray area just after airport security

Transport and critical infrastructure

Operational networks with restricted external connectivity and strict change control.

Transport →

What is included

What the deployment covers

The controls and guarantees your review will ask about.

Data residency

Database, files and logs stored in your facility and your country.

Network isolation

Runs behind your firewall; no inbound connection from the vendor.

Encryption in transit

All traffic between devices, browsers and the platform is encrypted.

Role-based access

Roles and per-branch permissions managed by your administrators.

Personal data masking

Email and phone are masked; revealing them needs a permission and is logged.

Audit log

Who viewed, changed or exported what, and when.

Retention and deletion

Retention rules and deletion requests handled inside the platform.

Internal integrations

API reaches CRM, ITSM and data warehouses that are not on the internet.

Learn more →

Updates on your schedule

Release notes, your staging, your approval, your production window.

How it compares

On-premise, private cloud or vendor cloud?

Three ways to host a feedback platform, and what each one means for control.

	Qmeter on-premise	Vendor cloud (typical)
Where customer data lives	Your data centre or private cloud, your country	The vendor's cloud, often in another jurisdiction
Network exposure	Behind your firewall; no inbound vendor connection	Public internet endpoints operated by the vendor
Who operates it	Your IT team, with our support	The vendor
Feature set	Identical to the cloud edition	Self-hosted editions in the market are often reduced
Updates	On your schedule, after your approval	Continuous, decided by the vendor
Reach into internal systems	Direct, inside the network	Through exposed endpoints or middleware

General observations about hosting models, not claims about any named vendor. Your own requirements decide; we put ours in writing before you commit.

Data protection

Privacy and confidentiality, by design

Hosting decides where data lives. These controls decide who can see it.

Anonymous by default

Ratings carry no personal data; identifying fields are added only when you decide.

Masking and permissions

Personal data is masked in the interface; revealing it requires a permission and writes an audit event.

AI with a data boundary

AI reports work on the data structure, not on customer answers, and can be switched off in isolated deployments.

Your data stays yours

Everything stored in your database belongs to you and remains available to you at the end of the contract.

The cloud edition's data-protection details are on the security and GDPR page; the on-premise architecture and requirements are shared in writing on request.

FAQ

On-premise deployment, answered

Short, honest answers. For anything else, talk to our team.

Where is customer data stored in an on-premise deployment?›

In your own database, on your servers or private cloud, in your country and your facility. Answers, comments, voice and video, customer records and audit logs never leave your network.

Is the on-premise edition the same product as the cloud?›

Can Qmeter run in an isolated network without internet access?›

Does the vendor have access to our installation?›

How are updates delivered?›

Who handles backups and disaster recovery?›

Who can see personal data?›

Can it connect to our CRM, ITSM or data warehouse?›

Do you support single sign-on and directory integration?›

How do we start, and how is it priced?›

Keep exploring

Get started

Bring your IT and security team to the first call

Thirty minutes: the architecture, the controls, the requirements. You leave with documents your team can review, not a sales deck.