One place for the working set
Bring the documents and project files together. Give the collaborator the material needed for a specific task.
Your assetsNative application collaboration
Work together.
Keep control.
Give external partners a protected workspace for sensitive documents and project files. Let them use familiar desktop applications while you keep control of the assets.
Designed for Windows. Focused application support.
The workspace conceptNYX / 01
EXTERNAL COLLABORATION
A shared project. A clear boundary.
project-brief.docxOriginal format. Familiar tools.
Protected working copy
Y
Your teamSets the rules
P
Your partnerDoes the work
Shared files, still yours.
Built for professional teams working beyond their own walls.A better handoff
Share the ability to work.
Retain the right to decide.
From the first brief to the returned revision, a workspace connects the files, the people, and the rules for one project.
Clear rules for the work
Define who can work, which actions are allowed, and when access ends. Protection belongs to the project context.
Your permissionsA deliberate handoff back
Let your partner save progress, then submit a revision for your review. A saved change and a delivered result are separate steps.
Your next decisionA complete collaboration loop
Familiar work.
A more considered handoff.
Follow a project from preparation to closure. Select a step to explore the intended experience.
WORKFLOW PREVIEW01 / 04
A brief. A partner. A plan.
Start with the files and permissions for this assignment.
project-brief.docxDOCX
- Collaborator
- Project partner
- Permission
- Edit & return
- Access term
- Agreed for this project
Keep the tools you know.
The recipient uses the NyxWard client to enter the workspace and launch a supported app.
Editing takes place in the protected working context.
Ready means submitted.
The collaborator chooses when to hand back the revision. The owner decides what to accept.
Progress savedThe collaborator can keep working.
Revision submittedReady for the owner's review.
Finish with a clear record.
Review the returned work, decide what to retain, and close the collaboration.
- Result
- Reviewed by your team
- Further access
- Ended under the policy
Access changes depend on the agreed online or offline authorization terms.
For teams with valuable work
Small team.
Serious intellectual property.
Designed for professional businesses of 10–500 people that work with external specialists and need a manageable way to protect project assets.
DESIGN & ENGINEERING
Bring a specialist into the project.
Work with suppliers and engineering partners around a defined working set and a clear return path.
LEGAL & PROFESSIONAL SERVICES
Collaborate on sensitive material.
Give clients, advisers, and external teams a focused space to review documents and return their revisions.
These are pilot scenarios. Confirm the application, version, file types, and required operations before use.
Protection with a purpose
Built around the work
you choose to protect.
The workspace design combines controlled editing with encrypted local storage. Each pilot needs a defined, tested boundary for the complete task.
Understand the boundariesA defined project boundary
Protection is scoped to the controlled workspace and its approved application workflow.
Protected working copies
The design requires workspace writes, including relevant working files, to stay in encrypted storage.
Support that is verified
An app name alone is not a compatibility promise. Versions, file types, and operations are validated together.
Start with a real assignment
Your next project
is the right starting point.
Choose one recurring external collaboration. Define what the partner needs to do, then validate the complete journey with representative files.
Pilot planning · Application scope and commercial terms to be confirmed
A FOCUSED PILOT
Three things to bring.
- 01A real task
Who is collaborating, and what should they deliver?
- 02The working tools
Which Windows app, version, and file formats are involved?
- 03A definition of success
What can be edited, returned, retained, and accessed offline?
The console is a UI preview with sample data. It does not create a live workspace.
Before you begin
A few practical details.
What is a workspace, and where does .nyx fit?
A workspace is the collaboration context: assets, people, permissions, activity, and state. The .nyx container package is a delivery format. The package and a running workspace are different objects.
Which applications will be supported?
The first application set is being validated. Office and engineering applications are candidate scenarios, not a blanket support list. Each pilot confirms exact versions, formats, and operations.
What does the recipient need to install?
The intended workflow uses the official NyxWard Windows client and a supported native application. Installation requirements and any application conflicts are checked before the pilot.
Can work continue offline?
Offline control is part of the product direction. Available actions and authorization terms must be confirmed for the chosen mode. An offline device cannot receive an immediate remote access change.
Does ending a workspace erase every copy?
Ending access is different from erasing all copies. Cleanup, recovery, and revocation behavior must be validated for the workflow. The site does not promise control over every possible output channel.
How is NyxWard priced?
Business pricing is under evaluation. The current direction is company-level pricing tied to controlled project collaboration. Final pricing, included capacity, and recipient terms will be confirmed before a commercial pilot.
NYXWARD