Deployment and Security
Your data. Your control.
QWorks runs on your infrastructure; identity, data, integration and the operating model are configured to your existing IT standards.
- On-premises deployment
- Can run on a closed network
- Corporate SSO · IAM
- Data under your control
Four areas of control
Corporate control is kept in four areas.
Application
QWorks runs on your application infrastructure.
Data
Quality records and evidence stay in your data infrastructure.
Identity
The user and role structure can work with your existing IAM and SSO infrastructure.
Integration
It connects to ERP, MES, PLM and other systems by the method you permit.
Identity and access
The right person. The right scope. The right access.
Identity
Users sign in with their existing corporate accounts; password policy and multi-factor authentication stay in your infrastructure.
Role
Quality, production, engineering, supplier quality and management roles are defined separately.
Context
Access can be limited by site, customer, product group and organisational unit.
External users such as suppliers are scoped to reach only their own cases and the evidence requested from them.
Controlled environments
Changes do not go straight to production.
- 01Development
- 02Test
- 03Acceptance
- 04Production
Configuration and release changes move in a controlled way, according to your environment standard.
A 2-, 3- or 4-environment model is adapted to your standard.
Continuity
The operation runs. The record is kept.
Audit trail
Who did what, and when? The history of actions is kept as an audit trail; changes are tracked as well.
Backup
Backup is managed with your existing policy and tools; no separate backup island is created.
Continuity
Disaster recovery and restore targets are set according to your service levels.
Rollout
ScopeInstallVerifyOperate
A phased rollout rather than a big bang. Release upgrades are not imposed on a fixed date; your acceptance process sets the timing.
QWorks does not own your data.
Where data is kept, who can access it and what access is opened during support are set by your policy. The default data location is your infrastructure; external transfer happens only within integration or support scope that you approve.
An internet connection is not required.
QWorks can run on closed networks. Updates and support are carried out through the controlled method you permit.
AI stays inside the boundary too: QWorks Zero’s language model runs on your own servers; no data is sent to external AI services and no internet connection is needed.In developmentFrequently asked
The first questions IT and security teams ask.
Where does QWorks run?
QWorks is designed to run on your own infrastructure. The deployment location and topology are agreed with your IT team during the scoping meeting.
Is an internet connection required?
No. QWorks can run on closed networks. Release updates and support access are planned through the controlled method you permit.
Does the AI module send our data out, or act on its own?
No. QWorks Zero’s language model runs on your own servers; questions, answers and quality data are not sent to external AI services, and no internet connection is needed. Zero only proposes: an action opens when the user who asked approves it, and only within that user’s permissions; every step is written to the audit trail.
Will the provider have access to our data?
Permanent remote access is not required. When support is needed, the scope, duration and logging of access are set by you.
Does it work with our existing Active Directory / IAM?
Corporate directory and single sign-on integration are within deployment scope. The protocol and role mapping are agreed with your IT team during scoping.
Who manages backup?
Backup is managed with your existing policy and tools. Frequency, retention and restore targets follow your standard.
Are release upgrades mandatory?
No. New releases arrive in the test and acceptance environments first; your acceptance process and maintenance window set the timing of the move to production.
Let us discuss the deployment model against your own IT standard.
Let us map your infrastructure, identity, network and integration inventory together, and write the deployment topology accordingly.