A professional workspace designed for Switzerland.
A programme bringing together email, files, documents and private AI. Swiss hosting and protection levels will be specified for each module.
In development. The functions below describe the target architecture; availability and scope will be confirmed before any commitment.
The Swiss tier provides encryption at rest and in transit. Client-side encryption applies to eligible Zero Knowledge modules. The Sovereign tier adds dedicated infrastructure and key management.
Three planned protection levels
The Swiss tier provides encryption at rest and in transit. Client-side encryption applies to eligible Zero Knowledge modules. The Sovereign tier adds dedicated infrastructure and key management.
Swiss
Swiss hosting and encryption for stored data and communications.
- Hosting, backups and logs in Switzerland
- Seven blocks under a single identity
- Encryption at rest and in transit
- Migration from Google Workspace or Microsoft 365
- No advertising, no profiling, minimal telemetry
Zero knowledge
Client-side encryption for eligible files, vault and messaging modules.
- Encryption performed on the device for files, vault and messaging
- Keys derived on the workstation, never transmitted in the clear
- Metadata reduced to what the service technically needs
- Named access log, readable by your own administrator
- A written inventory of what we hold, service by service
Sovereign
Dedicated infrastructure and organisational key management.
- Master keys held by you, up to a dedicated hardware module
- Dedicated rather than shared infrastructure
- Private artificial intelligence over your documents, with no third party egress
- Endpoint and mobile management, access without implicit trust
- Configuration audit and an annual sovereignty report
Seven services, one environment.
Planned functions; protection depends on the module and selected tier.
Gmail, Outlook
Mailboxes on your own domain, strong encryption, and end to end encryption between users of the environment. Existing archives are imported.
Messaging
WhatsApp, Teams, Slack
One to one and group conversations encrypted end to end, on desktop and mobile, with controlled retention and scheduled deletion.
Files
Google Drive, Dropbox, OneDrive
Sharing and synchronisation, with encryption performed on the device before anything is sent. The server stores blocks it cannot open.
Video calls
Zoom, Google Meet
Meetings encrypted end to end, no account required for external guests, with waiting rooms and recording disabled by default.
Documents
Google Docs, Microsoft 365
Real time collaborative writing and spreadsheets, in the browser, on documents encrypted from the workstation.
Vault
1Password, shared folders
A zero knowledge compartment for the most sensitive material: passwords, articles of association, shareholder agreements, internal investigation files. Named access, logged and revocable.
Artificial intelligence
ChatGPT, Copilot
Search, summarisation, drafting and contract analysis over your own documents, with models running on infrastructure we operate in Switzerland. Your material is never sent to a third party interface.
Client-side encryption within a defined scope
This target architecture applies to eligible files, vault and messaging modules in the Zero Knowledge tier. It does not describe every module or tier.
On your device
The document is encrypted in the application or in the browser, with a key derived from your credentials and never transmitted in the clear.
On the network
What travels is already unreadable. The transport layer becomes an extra safeguard rather than the main one.
On our Swiss servers
Storage, backups and logs stay in Switzerland. The content there is an encrypted block whose key we do not hold.
On retrieval
Only an authorised device in your organisation reassembles the document. Our system administrator sees an identifier and a size.
Data protection and the applicable framework
Commitments will be defined for each service: processing locations, key management, providers, access and retention.
A Swiss company remains subject to applicable law and may be required to disclose data it holds. Protection depends on the actual architecture and contractual scope.
Artificial intelligence without giving up the documents
AI processing requires access to plaintext content during inference. The execution environment, permissions and data lifecycle must be defined separately; encrypted storage alone does not provide zero-knowledge inference.
- Plain language search across mail and files
- File summarisation and contract clause extraction
- Assisted drafting from your own document templates
- Consistency checks between accounting records and contracts
- No training data taken from your content
Migration is the real project
Changing office suite is not a licence purchase, it is a move. Mail archives, shared calendars, files, access rights, secondary addresses and staff devices all have to follow without a service interruption.
We treat this phase as a project in its own right, with an inventory beforehand, a switch in waves and a period of parallel running. It is the same work we carry out on our own platforms, where an hour of mail downtime is paid for immediately.
- Inventory of accounts, domains, aliases, groups and devices
- Transfer of mail archives and calendars
- Switch in waves, with parallel running
- Short team training and documentation in three languages
- Support through the first three months of operation
What executives ask before signing.
The answers are deliberately direct, including where they do not favour the product.
What exactly can you see of our activity?
On the zero knowledge blocks we see that objects exist, their size, their date and the accounts that access them. We see neither file names in the clear nor their contents. On the communication blocks, some routing metadata is technically necessary. We publish the list, service by service, rather than maintaining a convenient vagueness.
What happens if we lose our keys?
That is the honest cost of zero knowledge. We cannot recover content whose key we do not have. The design therefore includes recovery keys held by your organisation, split across several holders, and on the sovereign tier a dedicated hardware module. The loss procedure is part of onboarding, not an option.
Do we have to migrate everything at once?
No. Most organisations start with the vault and the files, where the risk is concentrated, then move mail once habits have settled. Parallel running is provided for during the transition.
When is it available?
In development. The functions below describe the target architecture; availability and scope will be confirmed before any commitment.
Assess your sovereignty requirements
Describe the data to protect, number of users and deployment constraints.
Write to us