Access to the internet, knowledge and useful AI should not depend on wealth, a premium subscription or owning the most powerful device.

VOLPAROSSA is building a Decentralized Intelligent Cooperative Network (DICN): an open-source network where participants share connectivity, storage and computing power. One reusable core brings those resources to a family of privacy-respecting applications.

The ambition is not simply another service to subscribe to. It is infrastructure that people can help operate, understand and shape together.

Our purpose · The network · Applications · Progress · Our principles · Get involved

An open-source project in active development. This is the future we are working toward, not a catalogue of finished products.

We want people everywhere—rich or poor—to be able to connect, learn, create and benefit from AI without being left behind as technology advances.

The long-term goal is access through a cooperative network without every person needing their own SIM card, mobile data subscription or paid AI plan. Local connections between participating devices and shared internet uplinks would provide an alternative where suitable links and peers are available, reducing dependence on any one mobile provider.

A modest device should be a doorway to shared capabilities, not the ceiling on what its owner can do. Fair participation must make room for limited resources, and accessibility, language support and usable interfaces belong in the design from the beginning.

We aim to reduce the number of data centers needed for everyday digital services by making better use of devices, connections and storage that already exist.

Share eligible content instead of repeatedly downloading it. Reuse useful models instead of duplicating every effort. Place suitable work where spare capacity can be used responsibly. Build for longevity rather than making constant hardware replacement a condition of participation.

This goal has to be measured: additional replicas, transfers and computation also have costs. Decentralization is not, by itself, proof of lower energy use. The aim is less total waste—not moving an invisible burden onto participants.

We want to strengthen the infrastructure behind open-source, privacy-friendly applications: communication, files, photographs, navigation, coding and more.

Here, sovereignty means practical control for people and communities: the ability to inspect the software, choose how resources are shared, keep control of private data and move to other tools. The goal is to reduce dependence on a single vendor, account system or always-on personal server without replacing it with another mandatory gatekeeper.

Private messages, files and journeys must not become the price of admission. Nor should they silently become shared training data. Participants should contribute deliberately, within limits that respect their own work, battery, bandwidth and storage.

Our goal is wider access to education, independent journalism, science and culture, with resilience against arbitrary censorship by governments or platforms.

We want people to compare sources, examine evidence and encounter perspectives beyond their immediate surroundings. The hope is to support informed dialogue and reduce polarization—not to make everyone agree or claim that a network can settle every dispute.

That also means respecting creators' rights and supporting fair, sustainable access to quality media. Shared distribution is not permission to bypass copyright or paid access. The network's own restrictions must be transparent and open to challenge; disagreement alone should not be treated as abuse.

The VOLPAROSSA core brings together five complementary layers:

These are shared services, not separate networks for every application. Public caching, private storage and message delivery have different permissions and lifecycles. Resource sharing should serve the device owner as well as the wider network.

One compatible background core should serve several applications and continue its accepted work when a frontend closes. Application access and explicitly chosen system-wide operation remain separate permissions.

Private storage follows one shared redundancy policy. Its contribution rule counts the physical space used on other devices, including recovery copies and overhead: a 1 GB encrypted file with two copies requires roughly 2 GB plus overhead of space for others. If usage falls, that contribution target falls too; existing fragments must be safely handed off before occupied capacity is released. Automatic accounting and maintenance are still being integrated.

Shared AI is the default architecture, not a collection of isolated local assistants. The goal includes protected private tasks, images, audio and spoken interaction, plus autonomous research and software maintenance under the same resource and privacy boundaries. Authorized updates should eventually be distributed and installed automatically, with independent checks and recovery. These capabilities are not all operational yet.

Financial participation is separate from network contribution. Joining VOLPAROSSA does not open a financial account, invest money or authorize payments.

Shared access is not connectivity created from nothing. Devices still need a reachable connection, external internet access still needs someone's real uplink, and hardware and electricity still have costs. We are working to share that infrastructure more fairly, not promising unlimited free capacity or coverage everywhere.

The application family builds on existing open-source work rather than asking everyone to abandon familiar tools. These are integration projects at different stages of development, not finished replacements for their upstream applications.

These are independent VOLPAROSSA integrations, not official products of the upstream projects. Upstream attribution and applicable licenses must be preserved.

Scoped development trials demonstrate real multipath network traffic, verified peer-content retrieval, encrypted storage recovery, adapter training and public tasks on peer workers. The Drizz.li and Overmorrow web clients display and refresh real weather and particulate forecasts delivered through protected peers; their first retrieval currently precedes opening the UI.

The installed Overmorrow Android app also retrieves real forecasts on demand through the core in an emulator. The joined Android trial checks initial data, user-triggered refresh and return from the background while the products remain fresh. Expiry with real products, physical phones and iOS remain to be demonstrated.

VOLPAROSSA Code now uses OpenCode on its main branch, and the native CPU backend is now on core main. A real model-driven coding trial reads and edits a code fixture, runs an approved test and passes an independent check through the core's local CPU backend. That bounded coding task takes about 37 minutes and remains tied to its original pinned core revision. The newly integrated core has passed source checks, but that model trial has not been repeated on it. The trial demonstrates an executable workflow, not competitive performance, general coding reliability or confidential processing on other people's devices.

A separate core trial runs signed TEST-unit transfers across four validators, rejecting conflicting spends and testing partitions, restart and replay after a committed transfer without a second debit. Bank currently connects to the owner-local transaction API. Citizen has an executable referendum-procedure simulation with fictional people. Neither project provides a live financial service, verified real-person voting or recognized public authority.

The immediate integration work focuses on shared private-storage maintenance and confidential peer-compute prerequisites, while preserving the demonstrated coding workflow. The complete Image/Cloud repair-and-restore lifecycle remains unverified; failures during publication are still being investigated. Android expiry and broader device support also remain open.

These milestones do not complete every application or make development builds suitable as a sole backup. See the core development summary and detailed evidence.

Technical capability is not enough. We also want fair, responsible use of digital services: generosity without exploitation, freedom with responsibility, and cooperation without surrendering personal dignity.

Ancient ethical writings and philosophical traditions inspire this purpose. We seek principles that can serve people across cultures and beliefs—not a religious membership test, a claim that every tradition agrees, or an AI appointed as an unquestionable moral authority.

The project's seven-virtue framework gives that ambition a practical vocabulary:

The intended shared immune system applies these principles through mutual review across all five layers, their applications and software maintenance: agents examine work, compare evidence and help correct harmful or unreliable behavior. Consequential decisions should have a clear scope, be explainable and remain open to correction. Privacy must not become a pretext for abuse, and safety must not become a pretext for silencing disagreement.

This oversight is still being developed. No automated system can be assumed infallible, and a signature does not make a judgment true. The project is not a promise of unrestricted access or exemption from applicable law. Current principles and policy boundaries are documented openly.

You do not have to wait for a finished product to help shape it.

Developers, designers, researchers, translators, educators and prospective users can all contribute: improve an explanation, challenge an assumption, discuss access on modest devices, reproduce a bounded test or help complete one useful integration. Honest questions and careful criticism are welcome alongside code.

Working components and scoped trials already exist, but there is no supported end-user release. Complete applications, dependable shared AI, confidential computation on other people's devices and automatic resource maintenance remain in development. Do not use development builds as your only backup or rely on them to protect sensitive activity.

Explore the core · Read the development status · Find your starting point

Our aim: more people able to connect, more freedom to build, and more of the benefits shared.