> 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/roadmap.md). # Roadmap 2025 rebuilt the stack. 2027 opens it as infrastructure other products can run on. The private network is already a place to store bytes: a drive, a data set, a database copy, a static site. The year opens with Neosign certificates. Then backup and replication a company can turn on. Then a build-and-host platform on the same swarm. ### 2026 : Delivered #### The infrastructure, rebuilt from scratch The old layout is gone. In its place is one private IPFS network, built to be operated. * A **closed swarm**. A swarm key admits the nodes. The public DHT stays off, so files are not published on the open IPFS directory. * A **Private Indexer**. Nodes announce what they hold. A lookup answers in one request, with providers already ranked by success, freshness, and latency. * A **Swarm Accelerator**. Reads start on the best node and open another path if that node is slow. Recent files stay warm in cache. That is what the new infrastructure makes possible. Content is discoverable inside a private network. A download does not wait on a single slow peer. An operator joins, announces capacity, and is measured by real availability. Any client that can write a CID and read it back can use the same directory and the same gateway. NeoDrive is the first of those clients. #### NeoDrive, rebuilt The drive was rewritten on top of that network. Sign-in is email or SSO. Folders, upload, trash, restore, favorites, and quotas behave like a drive people already know. Encryption happens in the browser, before the file leaves the device. Names and the tree live in an index, so opening a folder, renaming, and moving stay instant. The network only holds the encrypted bytes. A one-gigabyte rename no longer rewrites the file. A download no longer depends on guessing a peer. The product and the infrastructure finally match. ### Q1 2027 : Neosign certificates Neosign is Neova’s electronic signature. In the first quarter of 2027 it launches its certificates. A certificate names the signer. The signature is made with that certificate, so the document says who signed it and when, and the result can be checked later. The signed file stays on the private swarm, next to the rest of the company’s documents in NeoDrive: encrypted in the browser, found through the indexer, read through the accelerator. Issuing the certificate and keeping the signed document are two different jobs. Neosign does the first. The network does the second. A company signs in the same place it already stores the file. ### Early 2027 : Infrastructure products for companies The swarm already accepts data, database copies, and static sites as storage. Early 2027 is when that becomes a product a company can buy and run, the way they already buy backup software. **Automatic backup.** A console issues access to the swarm. A backup job uses that access and runs on its own, in the spirit of what teams know from Veeam. Data leaves the primary system and lands on the private network. There is no second cloud to stand up, and no IPFS to operate by hand. **Decentralized replication.** The same access model keeps copies across the swarm, on nodes you can name, including a copy outside the primary building. The directory knows where each copy lives. The accelerator reads from the healthy one. Around those two, the network opens as a B2B infrastructure layer: data hosting, database copies, and static delivery, each reached through credentials the console generates. NeoDrive stays the drive. These are the workloads beside it. ### End of 2027 : Build and host on the swarm The last step of the year is a hosting and build system on the same network, in the spirit of what teams know from Vercel. You connect a project. It builds. The result is published on the private swarm and served through the accelerator. Preview, production, and rollback sit on content addresses, not on a single host’s disk. The swarm key still decides who can join. The indexer still decides who holds the files. Static sites are the first shape of this. The build platform is what turns that storage target into a place you deploy to. ### Where this leaves you | When | What you can do | | ----------- | ---------------------------------------------------------------------------------------- | | Now | Use NeoDrive. Store on the private swarm. Read how the indexer and the accelerator work. | | Q1 2027 | Sign with a Neosign certificate. The signed document stays on the swarm. | | Early 2027 | Turn on automatic backup and decentralized replication for company data. | | End of 2027 | Build and host on the swarm. | The detail of the enterprise workloads is in Enterprise.