DeOS is short for Decentralised Operating System - an operating system which works across any number of computers in a network,  using the blockchain as a register.

DeOS is a private online environment built on Razormind blockchain architecture delivering high up-time and scalability for users who want a tamper-proof environment with no single point of failure. DeOS combines the best of storage, computing, and security architecture in one elegant solution. 

Able to quickly and reliably respond to requests involving terabytes of data, DeOS mitigates against downtime by decentralising data and computation in realtime across the network - while employing blockchain encryption to safeguard these assets from theft.

DeOS is architected for:

  • Low-Latency: DeOS is designed to store data and serve requests predictably and quickly, even during peak times.
  • Availability: DeOS replicates and retrieves data intelligently, making it available for read and write operations even in failure conditions.
  • Fault-Tolerance: DeOS is fault-tolerant so you can lose access to DeOS nodes due to network partition or hardware failure and never lose data.
  • Operational Simplicity: DeOS allows you to add machines to the network easily, no increased operational burden.
  • Scalability: DeOS automatically distributes data around the network and yields a near-linear performance increase as capacity is added.

DeOS is available in Open Source and Enterprise models. DeOS' Open Source model is designed for enterprise teams, academics and enthusiasts. DeOS' Enterprise model adds monitoring, big data, analytics, and 24/7 support

Industries

Razormind deploys DeOS across companies in key industries to help them better manage and safeguard their data, saving them hundreds of thousands annually in downtime and mitigating against cybercrime, and fines for the breach of data protection acts. 

Business

DeOS serves as a secure Desktop environment, Blockchain as a Service, and Enterprise Platform for operating business processes securely. 

Financial Services

DeOS drives productivity across front and back office operations by decentralising and safeguarding trading and customer data.

National Infrastructure

DeOS provides secure networking solutions, trusted blockchain based databases, custom government organisational tools and collaboration to meet public needs.

Retail and Commerce

DeOS delivers high-availability, low-latency architecture required to ensure the smooth 24/7 shopping experience for online consumers while protecting their payment details. 

Mobile

DeOS delivers high availability and low-latency architecture necessary for the development of popular high traffic apps.

Gaming and Betting

DeOS ensures the speed and availability of data required for online gaming while protecting gamer's account details from 3rd parties using blockchain tech.


What is a DeOS Node?

Each node in a DeOS cluster is the same – containing a complete, independent copy of the DeOS package and the blockchain. There is no “master.” This uniformity provides the basis for DeOS's fault-tolerance and scalability. DeOS is written in C++ and Erlang, languages designed for massively scalable systems.


Data Distribution

Data is distributed across nodes using consistent hashing. Consistent hashing ensures data is evenly distributed around the cluster and new nodes can be added automatically, with minimal reshuffling.

Replication

DeOS automatically replicates data in the cluster (default three replicas per object). You can lose access to many nodes in the cluster due to failure conditions and still maintain read and write availability.


Scaling Out

Unlike other solutions, DeOS enables you to scale up/down easily. Growing your cluster doesn’t require increasing your operational staff. When you add or delete nodes, data is rebalanced automatically with no downtime. Developers don’t need to deal with the underlying complexity of what data is where. Any node can accept and route requests.

When Nodes Fail

If a node fails or is partitioned from the rest of the cluster, a neighboring node will take over its storage operations. When the failed node returns, the updates received by the neighboring node are handed back to it. This ensures availability for writes or updates, and happens automatically.