> For the complete documentation index, see [llms.txt](https://docs.neova.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neova.io/our-product/our-native-dapps.md).

# Our Native dApps

## NeoDrive

NeoDrive is the drive. You create an account, drop a file into a folder, and open it later. The screen is a file manager. The storage is a private network. You work with the first and never have to administer the second.

A cloud that asks people to learn wallets, content addresses, and node configuration will not replace the drive a team already has. NeoDrive is built so that it can.

### Sign in the way you already do

You sign in with an email address or your organization’s SSO. There is no wallet to install and no recovery phrase standing between you and your files.

A wallet can be linked later, from the profile. It adds an identity to the account. It is optional, and the drive works fully without it. That is how NeoDrive reaches people who will never open a Web3 tool on purpose, and people who already have a wallet and want it connected.

### The everyday product

Once you are in, NeoDrive behaves like the file spaces people already trust:

* a folder tree, a list, and sort;
* drag-and-drop upload, with a progress bar that follows the real transfer;
* trash and restore;
* favorites;
* quotas that include what is still in the trash;
* duplicate names resolved the way a familiar drive resolves them, so two files can share a folder without one silently replacing the other.

The folder structure loads in a single request. After that, moving through the tree stays local to the app. Opening a folder does not fan out into a new request for every neighboring folder. That is why navigation feels immediate even though the bytes live on a distributed network.

Beta testers describe the result in the simplest terms: it feels like a normal drive. They upload and download documents. The network stays invisible. That is the product standard.

### Fast where you notice it

Two operations show where the speed comes from.

**Rename or move.** Changing the name or the folder of a file, including a one-gigabyte file, is an update to the index. The content is not uploaded again. On a system that addresses files by content alone, a rename would mean a new file. In NeoDrive, the content address stays put and the name is free to change.

**Upload and download.** Those do cross the network. The interface still stays responsive: the file appears in the list immediately, the bar tracks the send, and the file is ready once it is stored and pinned. In our tests, a 320 MB video finished uploading to NeoDrive in about five to six seconds, in the same range as a major centralized drive and, on that run, ahead of it.

The split between index and storage is explained in Distributed infrastructure.

### Encrypted on the way out

Every file is encrypted in the browser with AES-GCM before it is sent. NeoDrive and the nodes receive ciphertext. The readable document is reconstructed on your machine when you download it.

There is no setting to forget, and no separate “secure folder.” Encryption is the upload path. Security covers the format, where the key lives, and how the private swarm limits who can even hold the ciphertext.

### Points for using it

Storing files earns points: volume uploaded, streaks, seasons, badges you claim yourself, and referrals. The gesture is small on purpose. Points recognize usage. They are separate from the points operators earn by keeping nodes online.

You use a drive. Operators run the capacity. Both sides of that loop are visible, and neither one asks you to think about the protocol.

### What stays off your plate

| You do                              | NeoDrive does                                        |
| ----------------------------------- | ---------------------------------------------------- |
| Sign in, organize, upload, download | Find a healthy node and fetch the bytes              |
| Name the file whatever you want     | Keep the content address stable when you rename      |
| Work in the browser                 | Encrypt before the file leaves the device            |
| Ignore the network                  | Admit nodes with a swarm key and a private directory |

NeoDrive is the product. The private network is how the files are kept. You keep a drive. Your files leave the model where a single host is the only place they exist.

<figure><img src="https://3571481541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKGOds7mS5uR6quk60UHJ%2Fuploads%2FCrwfHM4PP7s5ndZi7eNU%2FNeodrive%20-%20Response%20to%20Data%20Issues.png?alt=media&amp;token=3d2e3546-330d-48b8-a337-ff841c70d140" alt=""><figcaption></figcaption></figure>

**NeoSign** is a decentralized digital signature solution that offers the ease of traditional e-signatures, enhanced by blockchain-backed proof of authenticity. Every signature is recorded on the blockchain, creating an irrefutable, tamper-proof record. With encrypted documents, NeoSign ensures both privacy and integrity, eliminating the risks of forgery or unauthorized signing.

<figure><img src="https://3571481541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKGOds7mS5uR6quk60UHJ%2Fuploads%2FHmUA09VEUDBCWIBUKNk8%2FNeosign.png?alt=media&amp;token=b5992a1c-8a5b-48c4-9db4-2081bae5134b" alt=""><figcaption></figcaption></figure>

### Other dApps - Our focus now is turn into B2B & Infrastructure

Beyond NeoDrive and NeoSign, Neova is building a suite of exciting native dApps in development, addressing user needs across various domains like password management and healthcare with AI-driven solutions. As we continue refining these, Neova’s ecosystem will expand, offering users and developers a robust, interconnected environment for decentralized solutions.

Neova is shaping the future of digital ownership, privacy, and security—making decentralized solutions accessible, intuitive, and powerful for all.
