Protection that holds even when something goes wrong
We assume that a server can be attacked and seized, keys can be copied, and one day a quantum computer will appear. The system is designed for all of this at once.
CUBRA technologies
What we have built ourselves. We do not disclose the details of how it works – that is part of the protection.
CUBRA’s own cipher
A second independent layer of encryption beneath the global standard.
CUBRA Entry Swarm
Our own DDoS protection technology: the node stays available under a mass attack (switching entry points under attack — in development).
Self-healing keys
Post-quantum keys renew themselves, unnoticed by people and with almost no extra traffic.
Hidden sender
The server does not know who is writing, and messages carry no “seal” for outsiders – the conversation stays between you, as if face to face.
Pressure gets you nothing
The administrator holds no keys to conversations. Additional measures to protect staff – we will explain at a meeting.
Algorithm suites by number
One app for different national requirements, with no “negotiating” down to a weaker option.
Five questions for any secure communication supplier
Almost everyone writes “secure” and “encrypted”. To compare solutions on substance, ask each supplier five questions – and see how many get a clear answer.
- Where does encryption end? If it ends on a server or gateway, the text there is open to the administrator and to anyone who breaks into the server. In CUBRA – only on people’s devices.
- What does someone who seizes the server get? The right answer is: only ciphertext. In CUBRA there are no keys on the server, and the sender is hidden.
- Are conversations recorded today protected against a quantum computer? That needs a post-quantum key exchange right now. CUBRA has one on every plan.
- What happens when one cipher is broken? In CUBRA, a second independent layer – our own cipher – works beneath the global standard.
- Does the supplier talk about limits? We describe them openly on the “Security and transparency” page.
More on choosing for yourself and your team in the article “How to choose a secure messenger: 10 criteria”.
Why us, and not just another messenger
CUBRA is more than an app. We make our own cryptographic core, our own CUBRA Node hardware, a corporate VPN, network protection and communication without the internet – all managed from one CUBRA Console panel. An organisation gets communication for its people and network protection from one supplier, on its own premises, without third-party clouds.
The doubts we hear most often
Isn’t your own cipher a risk?
It does not replace the global standard – it works beneath it as a second independent layer. If a weakness is ever found in our cipher, the standard one still protects the message – and vice versa.
Why is there no independent audit yet?
The product has not been released yet. We will carry out an independent audit before release and publish the findings; until then – thousands of automated tests, mathematical models of the protocol and internal cryptanalysis.
What happens to our data if something happens to you?
The organisation’s licence works without a network connection, the CUBRA Node sits on your premises and belongs to you, and received messages can always be opened. Your system does not depend on our availability.
We already have network equipment. Will we have to throw it away?
No. CUBRA Node can work alongside existing equipment, and CUBRA Shield network protection is switched on only where it is needed.
Can our people manage without training?
Yes. The app verifies the other person by itself, runs on inexpensive phones, and the VPN connects with a profile, without installing any apps.
A typical solution and CUBRA
What changes when secure communication is built “from person to person”.
| Question | Typical solution | CUBRA |
|---|---|---|
| Where encryption ends | On the server or gateway – where the text is in the clear | Only on the devices of the people in the conversation |
| Who holds the keys | The supplier’s server, gateway or cloud | Only people’s devices, in protected memory |
| Layers of encryption | One standard layer | Two independent layers: our own + the global standard |
| Quantum computer | Post-quantum algorithms are only just appearing | Post-quantum keys today; an even stricter suite for organisations with their own node |
| If keys are copied | They are read until the key is changed by hand | Keys renew themselves within a few messages |
| DDoS attacks | Third-party protection services or denial of service | Our own DDoS protection technology in the node |
| Metadata | The server sees who writes to whom and how much | The sender is hidden; file size and type are inside the ciphertext |
| Server seizure | The main target of an attack | Yields no conversations – even if the administrator is coerced |
| National algorithms | A separate version for each country | One app, algorithm suites selected by number |
| Low-end devices | Clients built for specific hardware | One codebase – from an inexpensive phone to a rack |
| Hardware | Tied to one manufacturer’s hardware | Our own CUBRA Node hardware; if needed, it also works alongside existing equipment |
Comparison with typical approaches on the market. Individual products may offer some of these capabilities.
See for yourself
We will show how CUBRA works in your scenario.