Australian-developed encryption for government, critical infrastructure and enterprise Australian-developed · Sydney Confidential briefings available

What we do

File protection built for real operational work.

QES provides a consistent way to protect and restore files across Windows desktop, web browser and Android workflows—while fitting around the systems organisations already use.

The core capability

Put protection directly into the file-handling lifecycle.

QES helps organisations protect information before it is sent, uploaded, synchronised, archived or handed to another team. The resulting protected file can move through approved infrastructure without requiring that infrastructure to become the sole guardian of its contents.

At the authorised destination, QES restores the original file so work can continue. This operating model lets organisations strengthen high-value workflows without attempting a disruptive replacement of every surrounding platform.

QES Desktop for Windows

Designed for sustained, high-volume and repeatable file operations.

The desktop experience supports users and teams that need more than an occasional single-file action.

Files and folders

Protect or restore individual files, complete folders and operational sets while preserving the structure users expect.

Managed folder workflows

Support repeatable inbound and outbound processing through configured folders for approved operational use cases.

Operational continuity

Desktop processing is designed around large workloads, recoverable jobs and a controlled update lifecycle.

Source-file handling options

Apply organisation-approved handling choices after successful protection or restoration, including secure-delete workflows where enabled.

Activity visibility

Give authorised users and administrators clear operational status, history and usage information without cluttering the workflow.

Policy-aligned access

Require authenticated access before users can perform meaningful QES file operations.

QES Web

Controlled file protection from the browser.

QES Web provides a focused browser workflow for authorised users who need to protect or restore files without installing the Windows client.

  • Direct browser-based file and folder actions within supported limits
  • Consistent QES user experience and protected-file compatibility
  • Suitable for controlled access, evaluation and lighter operational workflows

Browser capabilities are intentionally matched to the security and performance characteristics of the web environment. Desktop-only functions remain clearly identified.

QES Android

Extend protected-file handling into mobile and field operations.

QES Android enables authorised users to work with protected files on supported Android devices, giving mobile teams a controlled path for file protection and restoration.

  • Authenticated access and device-oriented security controls
  • Local file protection and restoration for supported mobile workflows
  • Consistent use of the QES protected-file format across operating surfaces
WindowsWebAndroidOne QES workflow

Organisation-level capability

More than a file button.

QES is intended to support accountable deployment across customers, teams and operating roles.

Administration

Account and access operations

Support customer onboarding, authorised users, trial engagements and operational account management.

Visibility

Usage and activity

Provide the operational information required for support, allocation management and customer reporting.

Deployment

Controlled software delivery

Distribute supported client releases and manage the update path appropriate to the environment.

Support

Guidance and adoption

Equip users with clear operating guidance, product help and defined escalation channels.

QES does not ask organisations to abandon the systems that run their business. It gives sensitive files a stronger way to move through them.

That is the operating advantage: protection can be introduced where the consequence is highest, then expanded with evidence.

Assess the fit

Choose a representative workflow and put QES against it.

We will map the operating requirement, relevant QES surface, evaluation method and deployment path.

Encrypt everything.