Buy BLZ Tokens Now on Binance & Huobi
Token Sales Details Coming Soon

Pre-register now for first access to the token sale, coming soon:

Stay up to date with Bluzelle's newsletter

Empowering the New Decentralized Internet

DApp (Decentralized App) Developers need a blockchain database service to achieve their full potential. Enter Bluzelle.

Reliable Uptime

Even the big cloud providers are prone to downtime. Bluzelle eliminates any single point of failure.

Enterprise Scale

Bluzelle operates across ‘swarms’ of computers. Distributed data is accessed intelligently on demand.

Dynamic Speed

Data is sharded across many nodes, swarms and locations - then optimizes storage to maximize speed.

Bluzelle Team

  • Pavel Bains


  • Neeraj Murarka


  • Nitin Cunha

    Senior Developer

  • Scott Burch

    Senior Developer

  • Mehdi Abdeh Kolahchi

    Senior Developer

  • Richard Nistuk

    Senior Developer

  • Dmitry Mukhin

    Senior Developer

  • Ashok Venkateswaran

    Director of Enterprise Sales

  • Leandro Bark

    Head of Sales

  • Yingyao Xie

    Product Development Associate

Bluzelle FAQ

  • What is Bluzelle?

    Bluzelle is a decentralized, on-demand, scalable database for dApps. It is for software developers who are dissatisfied with the costs, limited scalability, and complexity of existing database systems. Bluzelle is low-cost, quick to deploy, provides utmost performance, and has a solid scalability path. Bluzelle provides enterprise-grade database services at a price for all aApp developers.

  • How is Bluzelle different from Storj, Filecoin?

    Storj and Filecoin are file-based services. They decentralize the storage and access to files. They operate purely on the manipulation of files, which has a very different application. File decentralization can be used for access to website resources (images, stylesheets, html, etc) or to enable globalized scalable access to documents. Bluzelle’s data decentralization services would be consumed by software at a more intimate level, that is opaque to the end-user, replacing existing database systems.

  • Without Bluzelle, what are developers doing?

    Currently developers typically run their own database servers and manually manage all the aspects, within cloud computing environments. Some opt to use shared-database environments.

    Customers with larger budgets pay for managed services cloud computing environments (ie: Rackspace, AWS, Azure, etc), or opt to run their own data centers complete with their own IT departments to manage these.

  • When is the token launch? Will there be a pre-sale?

    The token launch will be in Nov 2017.

  • When will Bluzelle be live?

    We plan to release an intial version with a set of features in December 2017.

  • Where is Bluzelle based?

    We are a Singapore company and headquartered there. Singapore is the gateway to Asia and allows us to build our business in Asia. We also have an R&D center in Vancouver, Canada. The majority of our technology team will be in Vancouver but we also plan to build a global team in many regions proficient in blockchain.

  • How can I get involved?

    If you are a developer, come and join our community. We’re looking for early users to help test and build our network.

  • What does Bluzelle mean?

    Picking a name is very hard given that almost every domain is taken. We decided to work on word combinations. We liked the color blue (Pavel went to UCLA). Pavel and Neeraj’s parents are from India so they thought of the Indian Gazelle. Gazelle’s are meant to be fast and agile. That’s what they wanted the technology to be. So Bluzelle was born.

  • Is there a masternode for this token and how many do you need?

    There is no master node in the Bluzelle database architecture. It is decentralized and so the model has swarms of nodes.

  • What are the specs / requirements for hosting the nodes? would a NAS do?

    There will be some minimum requirements to be a farmer node... as you can imagine, the farmer nodes dictate the limits of a swarm, so minimums apply to ensure the network performs well. An NAS would work. Most of the time, the NAS is configured or can be configured to use NFS or SMB/CIFS or even AFP so that processes on your farming machine can read/write to the device. So it should be fine.

  • How will the information be secured?

    We'll be using NSA grade encryption throughout the technology - user's identities, their associations to their data, and each shard of data, are just some of the items we'll be encrypting.

  • In your primer you said that the data is immutable, is it right? All the data?

    Yes, when you store the data it is immutable in the blockchain sense. That means you can update the data however previous versions of it still exist as per blockchain architecture.

  • Would only dApps require a decentralized database? Or do you think that mainstream companies would also be open to using Bluzelle?

    Decentralized database brings many advantages to the table that not just dApp developers will benefit from. In fact, the wider "net" for target markets is general software developers, whether that be video games, enterprise, banking and finance, security, aviation, or almost anything else you name. Some of these will naturally take longer to adapt and accept decentralized tech. dApps are the natural and least friction target market for us.

    And these others can use Bluzelle almost out the gate. But it is important to take focus on the most appropriate starting target market when Bluzelle comes out.

  • Why contributing to Bluzelle network would not breach my security?

    As a farmer, your security is pretty well protected. Our software is open-source so anyone can review. As a user of the database, your data is encrypted by default.

  • Will BLZ tokens only be used for "purchasing" space in storage?

    BLZ tokens can be spent for database (not file storage) services, but they can also be 'earned' by offering up your computing resources for our database storage - you can also cash them out later.

  • How does Bluzelle compare with BigchainDB?

    BigChainDB's current product is a technology where you either have to get your own nodes and run your own network but decentralized. Not a ready-to-go DB. It does not use a swarming or crypto-economic model that guarantees decentralization and instead relies on "caretakers", which are organizations that agree to share the responsibility of managing the network.

  • How do you incentivize farmers to put up their hardware at the start?

    We have a few methods to build up our supply - 1) Gifting of BLZ Tokens 2)Adding resources from Channel partners like Azure & BT 3)By referral 4)Providing API keys and small amounts of tokens to developers during hackathons and events etc

  • Will it be an open or closed alpha?

    We are likely to open the Alpha to developers who are actively engaged in our Slack community and open it up from there once we get to Alpha 3 or 4.

  • Who decides the hosting prices?

    We are working on formulas where the network can create the price so it's fair to all based. We are exploring real-time pricing. These are currently being explored

  • What if the swarm stops providing the service?

    The only way a swarm stops providing the service is if the entire network is down. If a decentralized network is down, then we have a whole new set of global problems. ;)

  • Will the system always replace a leaving node with a joining one?

    If for some reason a swarm has many nodes leave in a short amount of time, nodes from other swarms can join or swarms can come together.