Fact-checked by Grok 2 weeks ago

Berkeley Open Infrastructure for Network Computing

The Berkeley Open Infrastructure for Network Computing (BOINC) is an open-source platform that enables by harnessing volunteered idle resources from personal computers and other devices worldwide to support scientific research projects. Developed at the , BOINC allows volunteers to contribute computing power to diverse fields such as disease research, climate modeling, and , running computational tasks invisibly in the background without interfering with normal device use. BOINC originated from the need to generalize beyond single-purpose applications like , which launched in 1999 and demonstrated the potential of public participation in science. In 2002, with funding from the , computer scientist David P. Anderson initiated the BOINC project at UC Berkeley to create a flexible, cross-platform framework for multiple research initiatives. The platform's server and client software were first released in 2004, supporting initial projects and evolving over more than two decades through open-source contributions, with the latest client version (8.2.4) incorporating features like application support as of July 2025. Key features of BOINC include heterogeneous , which accommodates CPUs, GPUs, and other ; result validation through redundant to ensure accuracy; and user-friendly account managers like Science United for selecting and participating in projects. It supports approximately 30 active projects, enabling seamless job downloading, execution, and uploading of results via a client application available for Windows, macOS, , Android, and other platforms. Volunteers can join through direct installation or aggregated portals, fostering community-driven without dedicated costs. As of November 2025, BOINC delivers an average of 18.569 petaFLOPS of computing power daily from 18,775 active volunteers operating 89,411 computers, making it one of the largest sources of public computational resources for and significantly outperforming equivalent infrastructure in cost-efficiency. Notable projects include for global health challenges, for gravitational wave detection, and for , collectively advancing research while engaging millions in over the platform's history.

Overview

Definition and Purpose

The Berkeley Open Infrastructure for Network Computing (BOINC) is an open-source middleware platform designed to coordinate large-scale efforts across personal devices worldwide. It serves as a non-intrusive software layer that enables volunteers to donate their idle resources—such as CPU, GPU, and from desktops, laptops, and devices—to support scientific endeavors without requiring specialized hardware. The primary purpose of BOINC is to empower scientific by aggregating distributed computational power for computationally intensive tasks, including , simulations, and modeling. This model harnesses unused cycles from millions of participants to tackle complex problems in diverse fields, such as (e.g., searching for extraterrestrial signals), (e.g., protein folding for ), and climate science (e.g., predicting environmental changes). By running scientific jobs in the background during periods of device idleness, BOINC democratizes access to , allowing researchers to scale operations globally at minimal cost. At its core, BOINC operates on the principle of distributing discrete "work units"—small, independent computational tasks—to volunteers' devices, which process them locally and return results to central servers for aggregation and validation. This approach transforms a of consumer-grade into a powerful, resource, effectively providing researchers with petaFLOPS-level capacity comparable to leading supercomputers without the need for expensive data centers or infrastructure. For example, as of 2018, individual BOINC projects delivered around 2 petaFLOPS of sustained performance at an annual operational cost of approximately $100,000, far below equivalent commercial pricing.

Key Features and Benefits

BOINC's cross-platform compatibility enables widespread adoption by supporting major operating systems including Windows, macOS, , and , while integrating with both central processing units (CPUs) and graphics processing units (GPUs) such as coprocessors for efficient computation. This versatility allows volunteers to contribute from diverse devices without compatibility barriers, maximizing the platform's reach across personal computers and mobile hardware. A core feature is its multi-project support, which permits users to attach a single BOINC client to multiple scientific endeavors simultaneously, allocating configurable resource shares—such as percentages of or disk space—to each project as preferred. This flexibility ensures continuous utilization of resources even if one project experiences downtime, enhancing efficiency for participants. Resource management in BOINC is designed for seamless, non-intrusive operation, automatically detecting and harnessing CPU and GPU cycles while honoring user-defined preferences for usage, , work schedules, disk space limits, and network constraints. For instance, users can set a "duty cycle" to throttle intensive tasks during peak hours, balancing computational contributions with device performance and . The platform's open-source nature, distributed under the GNU Lesser General Public License (LGPL), fosters , -driven improvements, and customization, allowing developers to modify and extend the software for specific needs. Volunteers benefit from BOINC by directly aiding cutting-edge scientific across disciplines, while earning verifiable credits that quantify their contributions and enable participation in leaderboards and recognition systems. For projects, BOINC delivers scalable, low-cost power—for example, circa 2015, a medium-scale BOINC project providing 100 teraFLOPS was estimated to cost around $200,000 annually, compared to millions for equivalent resources—by from donated hardware. On a global scale, as of November 2025, BOINC aggregates immense computational resources from approximately 18,800 active volunteers operating over 89,400 computers, achieving a 24-hour average of 18.6 petaFLOPS, with a significant portion derived from GPU acceleration. This distributed network rivals top supercomputers, democratizing access to for resource-limited researchers and amplifying collective impact on global challenges.

History

Origins and Development

The Berkeley Open Infrastructure for Network Computing (BOINC) originated in 2002 at the , Berkeley's Space Sciences Laboratory (SSL), where it was developed as a successor to the client software used by the project. Led by David P. Anderson, a researcher at SSL and director of , the initiative aimed to create a non-project-specific platform that could harness idle computing resources from volunteers worldwide. This effort built directly on the success of , which had demonstrated the potential of distributed but was constrained by its custom-built infrastructure. The primary motivation for BOINC was to address the limitations of project-specific software, which required each scientific initiative to develop and maintain its own client and server systems, leading to high costs, lack of , and for new projects. By designing a generalized, open-source framework, developers sought to enable multiple projects to share the same infrastructure, allowing participants to contribute to diverse scientific efforts such as astronomy, climate modeling, and biomolecular simulations without needing separate installations. This approach was envisioned to scale the model beyond SETI@home's focus on extraterrestrial , fostering broader adoption in scientific research. Initial development was supported by grants from the (NSF), secured starting in summer 2002, along with collaborations involving and early partners like Predictor@home, a project. These resources enabled the core team at SSL to prototype the system, emphasizing modularity to accommodate varying application needs. Early challenges centered on creating a secure and scalable architecture suitable for distributed environments with untrusted volunteer hosts, including mechanisms to detect and mitigate erroneous computations, handle server loads from potentially millions of clients, and support cross-platform compatibility while preventing fraud in resource allocation. The first public release, BOINC 3.0, occurred in 2003 and targeted desktop platforms, marking the transition from internal testing to broader availability.

Major Milestones and Evolution

In 2004, the (WCG) was launched on November 16 as a major BOINC-based initiative, funded and operated by to harness for humanitarian research in areas such as and . This integration provided BOINC with significant computational resources from 's infrastructure, enabling large-scale projects and marking an early expansion beyond academic origins. By 2009, the BOINC 6.x series introduced support for GPU computing, initially through NVIDIA CUDA integration in version 6.6.32, which allowed projects like to leverage graphics processors for accelerated workloads, significantly boosting performance for certain scientific applications. The period from 2008 to 2015 saw the debut of the BOINC app in 2013, extending to mobile devices and broadening accessibility for users on the go. 7.x, starting with 7.0 in 2012, incorporated CPU throttling mechanisms to enhance , reducing power consumption during idle or low-priority tasks while maintaining computational output. During this era, BOINC's ecosystem expanded to support over 100 projects cumulatively, spanning diverse fields like , , and modeling. From 2016 to 2020, BOINC advanced compatibility with processors, building on support to include broader low-power architectures suitable for embedded systems. Enhancements for virtual machines, such as improved integration, allowed projects to run isolated Linux-based applications on diverse host operating systems, facilitating cross-platform development. In response to the , BOINC-powered projects like OpenPandemics on WCG launched in 2020 to accelerate by simulating protein structures from and related viruses. Between 2021 and 2025, the 8.x series progressed with incremental releases focused on stability and modern hardware, culminating in version 8.2.4 on July 10, 2025, which added native support for containerized applications to simplify deployment of complex scientific workloads. Ongoing maintenance via the project's repository ensured regular security patches and compatibility updates, including support for and the latest versions, without major architectural overhauls. Over its evolution, BOINC has shifted from a desktop-centric platform to one inclusive of and devices, enabling volunteer contributions from smartphones and low-energy systems to democratize access to resources. This progression, highlighted by the 2025 Docker integration, underscores BOINC's sustained relevance in as of November 2025.

Architecture and Design

Core Components

BOINC employs a client-server model in which centralized project servers distribute computational tasks, known as , to volunteer clients installed on participants' devices. Each consists of an application executable along with input data, which the client downloads, processes locally, and returns the results to the server via HTTP-based remote procedure calls (RPCs). This architecture enables scalable distribution of scientific computations across heterogeneous volunteer resources worldwide. The core server-side components manage task assignment, data handling, and result processing. The scheduler, implemented as a program within an web server, assigns work units to incoming client requests by querying a shared-memory for available tasks. The daemon maintains this by periodically populating it with unsent work units from the database, optimizing database access and reducing load during high-traffic periods. The server, typically part of the web server infrastructure, facilitates the transfer of application files, input , and output results between clients and the project storage. The transitioner daemon monitors and updates the states of work units and results in the database, handling transitions such as marking computations as complete or initiating validation. These components collectively ensure efficient operation, with the scheduler and focusing on distribution while the transitioner coordinates post-computation workflows. The lifecycle of a begins with its creation on the , where project-specific software generates the unit along with associated input files and registers it in the database. The unit is then made available for distribution: a client requests work via the scheduler, downloads the application and data files from the data , and executes the in a local process. Upon completion, the client uploads the output files and result back to the . Finally, the transitioner and subsequent components validated results for scientific , completing the cycle. This flow supports fault-tolerant computing, as unfinished or erroneous units can be reassigned to other clients. BOINC accommodates heterogeneous computing environments by providing platform-specific application versions and flexible wrappers that allow legacy or diverse applications—written in languages such as C or Python—to run uniformly across operating systems like Windows, Linux, and macOS. These wrappers interface with the BOINC client API to handle resource allocation, checkpointing, and file I/O, enabling support for both CPU and GPU tasks without requiring modifications to the core application code. Security in BOINC's core architecture relies on sandboxing mechanisms to isolate computations and prevent unauthorized access or malicious execution on volunteer machines. Clients run applications under unprivileged user accounts with strict limits on , memory, disk usage, and network access; exceeding these triggers task termination. Additional protections include for application files to verify integrity and optional wrappers for enhanced isolation. These features collectively mitigate risks from untrusted code while maintaining volunteer participation.

Credit and Validation System

BOINC ensures computational accuracy through a validation process that relies on redundant , where each —a discrete task requiring identical —is assigned to multiple volunteer clients for independent execution. The server-side then compares the output files from these replicas, performing a syntax check to confirm their presence and format before assessing equivalence, typically using checksums for exact matches or thresholds for floating-point results. This replication mitigates errors from hardware faults, software bugs, or malicious activity by requiring agreement among instances. Central to validation is the quorum system, which mandates a minimum number of consistent results—often three—to declare a valid, with additional replicas scheduled if initial outputs disagree until a strict is achieved or a maximum threshold is reached. The result, serving as the authoritative output for scientific analysis, is selected from this consensus, while dissenting results are discarded. For long-running tasks prone to interruptions, applications can employ trickle-up messages to report partial progress or to the asynchronously, enabling early detection of issues and potential partial validation without awaiting full completion. Error rates are managed through adaptive replication, which reduces redundancy for reliable hosts, and punitive mechanisms that limit task assignments to flaky exhibiting repeated failures. To motivate volunteer participation, BOINC's credit system awards units—termed cobblestones—proportional to validated computational effort, estimated via the hardware's benchmarked . Each host's peak is determined through initial benchmarks like for CPUs, with claimed credit calculated as the product of elapsed time and peak , scaled to cobblestones where 200 cobblestones represent the daily output of a 1 GFLOPS ($8.64 \times 10^{13} operations). The precise is: \text{Claimed Credit } C = \left( T \times \text{Peak FLOPS} \right) \times \frac{200}{86400 \times 10^9} where T is elapsed time in seconds; however, granted credit is adjusted for validation success to prevent inflation: for two replicas, the lower claim is awarded, while for larger quorums, it averages the middle values excluding extremes. This ties rewards directly to verified contributions, ensuring fairness across diverse hardware. Incentives extend beyond raw credits through community features like project-specific leaderboards ranking users by total output, achievement badges for milestones such as consecutive computation days, and a cross-project identification system that aggregates credits across BOINC initiatives for a unified volunteer profile. These elements cultivate competition and recognition, sustaining long-term engagement without monetary value.

Software Components

Client and Server Software

The BOINC client software is available for download from the official website at boinc.berkeley.edu, supporting major operating systems including Windows, macOS, and Linux distributions. For Windows, users download platform-specific executables such as boinc_8.2.4_windows_x86_64.exe for Intel 64-bit systems (Vista through 11), which includes the core daemon boinc.exe that runs as a background process to manage task downloads, execution, and uploads without user intervention. Installation involves running the executable, which sets up the client in the default directory (typically C:\Program Files\BOINC) and prompts for initial configuration, including project selection; the daemon operates silently thereafter, utilizing idle resources. On macOS, the universal package boinc_8.2.5_macOSX_universal.zip supports both Intel and Apple Silicon architectures; users unzip the file, mount the DMG, and run the installer, with the core client functioning as a background service via launchd. For Linux, packages are provided for x64 and ARM64 via distribution repositories or scripts like boinc_8.2.4_x86_64-pc-linux-gnu.sh, installed by running the script as root (e.g., sh boinc_*.sh), placing binaries in /usr/local/bin and enabling the daemon through systemd for persistent background operation. Client is primarily handled through the cc_config.xml file, located in the BOINC data directory (e.g., %APPDATA%\BOINC on Windows or ~/.boinc on /macOS), which allows advanced global customization beyond the graphical manager, such as and options. For - or app-specific settings like CPU usage limits, users can use app_config.xml files with options such as <cpu_usage> (e.g., setting 0.5 for 50% utilization to balance performance and responsiveness); global CPU throttling is managed through the BOINC Manager or preferences. bandwidth can be limited using tags like <max_file_xfers> (default 8, for total simultaneous transfers) and <max_file_xfers_per_project> (default 2, per ), preventing excessive data usage on metered connections. settings are configured in a <proxy_info> section, specifying <http_server_name>, <http_server_port>, <http_user_name>, and <http_user_passwd> for HTTP proxies or SOCKS versions (e.g., 5), ensuring connectivity in restricted environments; changes require restarting the client or using the boinccmd --read_cc tool. The BOINC server software consists of open-source tools designed for project administrators to host custom distributed computing initiatives, built on a stack including Apache web server, PHP for dynamic content, and MySQL (or MariaDB) for database management. Setup begins with cloning the repository from GitHub (git clone https://github.com/BOINC/boinc.git), installing dependencies like apache2, php-mysql, libapache2-mod-php, and mysql-server on Ubuntu-based systems via apt-get, then configuring the database with a dedicated user (e.g., boincadm with password foobar99). Administrators use the make_project script to initialize a project (e.g., ./make_project --url_base http://example.com myproject), creating directories, databases, and initial files in ~/projects/myproject; this automates schema setup in MySQL and generates PHP scripts for user registration and workunit distribution. Additional tools like xadd for adding applications and update_versions for deploying binaries complete the stack, with the server running daemons (e.g., transitioner, feeder) via bin/start for ongoing operation. BOINC supports automatic updates for project applications and results reporting, but client updates require manual downloads from the official site, with notifications via project messages or the event log. The version history includes incremental releases addressing compatibility; for instance, version 8.2.4, released on July 10, 2025, introduced native support for Docker-based applications, enabling containerized workloads on volunteer hosts without altering the core client. Maintenance involves periodic checks for updates using the BOINC Manager's "Update" button for projects and manual reinstalls for the client to resolve deprecated features, such as older 32-bit support phased out after 7.4.22. Common troubleshooting for the client includes firewall blocks, which often prevent task downloads or uploads; users should allow boinc.exe (Windows) or the boinc daemon (Linux/macOS) through ports 80, 443, and 31416 in rules, as well as disabling interfering antivirus scans on the BOINC directory. Driver incompatibilities, particularly for GPUs, arise from outdated or mismatched graphics drivers (e.g., /); verifying compatibility via project forums and updating to the latest certified drivers resolves detection issues, with the event log providing clues like "No usable GPUs found." Proxy misconfigurations trigger "can't access " errors, fixable by editing cc_config.xml or testing direct connections; restarting the client after changes applies fixes.

User Interfaces and Managers

The BOINC Manager serves as the primary graphical user interface (GUI) for end-users, providing a centralized control panel to monitor and manage the BOINC client software. It features a dashboard in both Simple and Advanced views, allowing users to track computational task progress, view accumulated credits from completed work, and receive project messages or notices about updates. Users can adjust settings such as , network usage, and temporary pauses (e.g., via the "Snooze" option, which halts computations for one hour), with the interface displaying real-time status through notification area icons on Windows or menu bar indicators on macOS and . Account managers are third-party web services that streamline user participation across multiple BOINC projects by handling account creation, attachment, and team affiliations in a unified manner. Notable examples include BOINC Account Manager (BAM!), GridRepublic (which offers a virtual currency called GridCoin), and Science United (which allows selection by science areas with anonymous pooled accounts). These tools present a curated list of available projects for users to select via checkboxes, automatically generating project-specific accounts linked to a single email and password for the manager service. They facilitate easier multi-project management and team joining without navigating individual project sites repeatedly. Web-based interfaces are integral to BOINC's user onboarding, primarily through individual project websites where volunteers create accounts using an email address and password before attaching to the software. This process involves visiting a project's homepage, completing the registration form to receive an account ID via email, and then using the BOINC Manager's "Attach Project" wizard to input the project's URL and credentials, enabling seamless volunteering and progress tracking online. Customization options enhance within the BOINC , including skins that allow modification of the Manager's visual appearance in Simple, Advanced, and wizard views to match personal preferences or themes. Notifications are configurable through the interface's message system and status balloons, alerting users to task completions or errors, while with widgets is supported via third-party add-ons for quick glances at activity without opening the full Manager. Privacy controls in BOINC emphasize user discretion, with options to participate by selecting non-identifying usernames during creation and limiting shared through project-specific preferences. Services like Science United further support by pooling users under shared on projects, confining personal details such as to the manager level and restricting or visibility in public statistics.

Mobile and Specialized Applications

BOINC extended its platform to mobile devices with the release of an official application in July 2013, designed to leverage idle time on smartphones and tablets running 4.1 or later. The app supports , , x86, and x86_64 architectures, enabling computation on a wide range of devices including tablets. Key features include -aware scheduling, which suspends tasks when battery levels drop below user-defined thresholds to prevent excessive drain, and offline computation queuing, allowing downloaded work units to process without constant connectivity. These adaptations address the resource limitations of mobile hardware while maximizing volunteer contributions during charging periods or availability. In contrast, BOINC lacks a native application due to Apple's strict guidelines, which prohibit apps from downloading and executing arbitrary code—a core requirement for BOINC's dynamic task handling. Developers have explored alternatives, but no official solution exists; users may access BOINC projects via interfaces or unofficial jailbreak methods, though the latter is not recommended due to risks and voids. For specialized environments, BOINC introduced Docker container support in client version 8.2.4, released on July 10, 2025, enabling volunteers to run containerized science applications on Windows, macOS, and hosts in a manner akin to workflows. This wrapper facilitates portable, isolated tasks without modifying host systems, broadening participation to server-grade or virtualized setups. Additionally, BOINC supports deployment on low-power IoT devices like through its client, which compiles and runs on ARM-based single-board computers, allowing integration into scenarios for distributed tasks. Mobile and specialized integrations face inherent challenges, particularly power constraints that limit computation to brief sessions on battery-powered devices, often resulting in shorter run times compared to desktops. over cellular networks adds further complexity, as intermittent can delay task uploads or downloads, requiring robust queuing mechanisms to maintain progress. Adoption of mobile BOINC has grown steadily since the Android app's launch, with volunteers contributing device cycles to scientific efforts, including climate modeling simulations that benefit from aggregated mobile processing power. This expansion has enabled broader participation in resource-intensive projects, though uptake remains tempered by device limitations.

Projects

Active Projects

As of 2025, the BOINC ecosystem hosts approximately 30 active projects spanning diverse scientific fields, including , physics, earth sciences, , and astronomy, each leveraging resources to advance goals. These projects distribute computational tasks as discrete work units, allowing volunteers worldwide to contribute idle processing power from desktops, laptops, and even mobile devices. Participation is facilitated through the BOINC client software, where users attach to a project by entering its URL in the manager interface, selecting preferred resource shares, and running tasks in the background without interrupting normal computer use. In , focuses on predicting protein structures and designing novel proteins to support and development, with ongoing applications in modeling variants for treatments like the SKYCovione vaccine. Work units consist of simulations for and , which often utilize GPU acceleration for efficiency in exploring conformational spaces. The project engages over 1.3 million registered users, processing over 8,000 jobs daily as of November 2025 to contribute to biomedical breakthroughs. World Community Grid addresses multiple humanitarian challenges, particularly for diseases like through the OpenPandemics initiative and climate-related efforts such as improving rainfall predictions for in vulnerable regions. Its work units involve large-scale molecular docking and simulations run on volunteer devices during periods, enabling rapid screening of potential therapies and environmental models. With contributions from around 818,000 volunteers, the project has expanded in 2024-2025 to include AI-assisted mapping of cancer markers from patient data. In physics, searches for and signals using data from observatories like and , aiming to detect weak astrophysical emissions from neutron stars. Work units process radio, gamma-ray, and interferometer datasets through signal correlation algorithms, compatible with CPU and GPU hardware across Windows, Linux, and Mac platforms. The project draws from over 500,000 volunteers, sustaining continuous analysis of vast astronomical archives. Climateprediction.net models long-term climate patterns, including temperature, precipitation, and probabilities, to inform resilience and . Volunteers execute work units as full climate simulations using the UK Met Office's model variants, which run for days on standard home computers to generate ensemble data for global comparisons. Other projects like LHC@home continue to support at by simulating accelerator experiments, while mathematics-focused efforts such as PrimeGrid hunt for large primes using probabilistic tests on volunteer . Collectively, these active projects maintain a vibrant volunteer base exceeding 18,000 daily active participants across the platform.

Completed and Archived Projects

Completed and archived projects in the Berkeley Open Infrastructure for Network Computing (BOINC) refer to those that have ceased active operations after fulfilling their primary objectives, exhausting , or transitioning to alternative computational resources. These projects typically conclude when scientific goals are met, such as data collection targets, or when maintenance becomes unsustainable due to outdated infrastructure. Unlike ongoing efforts, archived projects no longer distribute new work units to volunteers but preserve their outputs for further research and analysis. One prominent example is Predictor@home, launched in June 2004 as the first public BOINC-based project focused on using volunteer resources to simulate with the CHARMM software. It operated until approximately 2007, contributing to advancements in understanding relevant to the CASP6 competition. The project ended primarily due to shifts in research priorities and the need for more specialized computing environments beyond volunteer contributions. Another notable case is SIMAP (Similarity Matrix of Proteins), which ran from 2005 to the end of 2014 and utilized BOINC to compute all-against-all protein sequence similarities, building a comprehensive database covering major public protein repositories. The project achieved its goal of generating a pre-computed similarity matrix but terminated BOINC involvement to adopt new algorithms on dedicated server infrastructure, citing the limitations of for updated scoring methods. Results from SIMAP remain accessible via its archived database, supporting ongoing bioinformatics research. LHC@home, initiated in 2004 to support CERN's simulations for the , saw several phases conclude in the 2010s, including early applications like SixTrack for beam dynamics modeling. Specific phases ended as simulations integrated into professional or as hardware demands outpaced volunteer capabilities, though the project continues in evolved forms. Outputs from completed phases, such as simulation datasets, are preserved in CERN's repositories and cited in high-energy physics publications. SETI@home classic, a flagship project analyzing data for extraterrestrial signals from 1999 to 2020 (with BOINC integration from 2004), exemplifies a long-running effort that achieved extensive data collection over 21 years. It ceased on March 31, 2020, to prioritize data analysis and update its aging software infrastructure, which had become challenging to maintain. The amassed dataset is archived at UC for scientific review, with key findings published in literature. Common reasons for project termination include the fulfillment of core scientific aims, such as sufficient accumulation, alongside practical challenges like funding constraints or the migration to institutional for more complex tasks. Low volunteer participation in niche areas can also contribute, prompting teams to consolidate resources. Archival access to completed projects' results is ensured through public databases, peer-reviewed publications, and project websites, allowing researchers to build on volunteer-generated outputs without ongoing . For instance, volunteers' account and credits are often migrated or preserved for historical records, facilitating transitions to successor initiatives. Lessons from these completions have informed BOINC's evolution, particularly in enhancing algorithms to better support variable volunteer availability and in developing tools for smoother project handovers to systems. These experiences underscored the platform's flexibility, leading to improvements in software for handling diverse workloads and integrating with infrastructures.

Impact and Community

Usage Statistics and Growth

BOINC experienced rapid initial growth following its public release in 2004, when it transitioned users and reached approximately 300,000 volunteers, building on the project's earlier peak of over 1 million participants. By , BOINC-based projects collectively had 80,721 participants across 188 countries, supplying about 106 teraFLOPS of computing power. The platform peaked around 2007 with over 700,000 active computers, reflecting widespread adoption among science enthusiasts. Subsequent years saw a gradual decline in participation, dropping to around 60,000 active computers by 2022, attributed to factors such as limited efforts, complexities, and concerns over energy costs and . As of 2025, BOINC maintains approximately 18,430 active volunteers and 89,177 computers, contributing a 24-hour average of 20.759 petaFLOPS, with daily changes showing modest volunteer gains but host losses. This stabilization follows a post-2010 downturn influenced by the rise of alternatives, offset by enhancements like mobile app support and integration for easier deployment. In terms of computational scale, BOINC's peak performance reached about peta in 2018, supported by roughly 4 million CPU cores and 560,000 GPUs across devices. The current daily average of around 21 peta underscores sustained but reduced capacity compared to its height, with total historical contributions enabling significant scientific workloads, though exact cumulative FLOPS figures are not centrally aggregated. User demographics remain dominated by participants from the and , with top contributors often from these regions based on multi-project rankings. Device usage is heavily weighted toward desktops and laptops, comprising the majority of active hosts, while mobile participation via apps constitutes a smaller share, with surveys indicating low adoption rates for smartphones and tablets. Growth was bolstered by strategic partnerships, notably IBM's launch of World Community Grid in 2004, which leveraged BOINC to mobilize volunteer resources for humanitarian research and attracted corporate and individual participants. Improvements in ease of use, such as the intuitive BOINC Manager interface and cross-platform support, have also helped retain dedicated users amid broader trends toward accessible distributed computing.

Scientific Contributions and Challenges

BOINC has facilitated significant scientific discoveries across multiple disciplines through its distributed computing framework. In , the project has identified numerous pulsars, including the gamma-ray millisecond pulsar PSR J2039+5617 in 2020, by analyzing data from radio telescopes and detectors to detect continuous from spinning stars. In , has advanced , enabling the design of novel proteins for therapeutic applications, such as miniprotein inhibitors targeting the to block viral entry into human cells. Additionally, climateprediction.net and related projects like weather@home have produced high-resolution models that attribute events to human-induced , such as linking the 2000 floods to anthropogenic warming, thereby informing adaptation policies. These contributions have led to substantial academic and practical impacts. BOINC projects have resulted in over 1,000 peer-reviewed publications, with dozens appearing annually in high-impact journals like and , demonstrating the platform's role in enabling large-scale simulations unattainable on traditional supercomputers. Real-world applications include the identification of COVID-19 drug candidates through and SiDock@home, where volunteer computing screened potential inhibitors and repurposed drugs like against in 2020-2021 efforts. Despite these successes, BOINC faces challenges inherent to volunteer resources. Volunteer is common due to the costs of running computations on personal devices and concerns over to servers, leading to fluctuating participation and resource unreliability. Validation overhead, where results from multiple volunteers are cross-checked to ensure accuracy amid heterogeneous hardware and potential malicious submissions, reduces overall efficiency by requiring redundant computations. Furthermore, competition from scalable services and AI-driven platforms has diminished volunteer computing's appeal for some areas, as centralized resources offer more predictable without volunteer . Criticisms of BOINC often center on its energy consumption, with debates highlighting the environmental footprint of distributed computing on idle devices compared to optimized data centers. Improvements have addressed some issues, such as enhanced privacy modes that allow anonymous participation and limit data sharing, alongside optimizations for low-power devices to mitigate energy use. Looking ahead, BOINC's potential integration with edge computing could leverage mobile and IoT devices for real-time, localized simulations, expanding its scope beyond traditional desktops. The BOINC community plays a vital role in sustaining and evolving the platform through active forums where volunteers discuss issues and propose features, driving updates like improved scheduling algorithms based on user feedback. Teams, ranked by total credits earned—such as top performers like "Team China" or "Gridcoin"—foster competition and collaboration, with over 100,000 registered teams contributing to project momentum and scientific progress.

References

  1. [1]
    BOINC - University of California, Berkeley
    BOINC is an open-source software platform for computing using volunteered resources.Install BOINCChoosing BOINC projects
  2. [2]
    [PDF] Volunteer computing: the ultimate cloud - BOINC
    In 2002, with funding from the National Science Foundation, the BOINC project was established to develop general-purpose middleware for volunteer computing, ...
  3. [3]
    BOINC computing power
    BOINC computing power. Totals. 24-hour average: 20.759 PetaFLOPS. Active: 18,430 volunteers, 89,177 computers. Daily change: +28 volunteers, -738 computers.Missing: current | Show results with:current
  4. [4]
    [PDF] A Platform for Volunteer Computing - BOINC
    Dec 21, 2018 · BOINC, a widely-used open- source middleware system for volunteer computing, addresses these challenges. We describe BOINC's fea- tures, ...
  5. [5]
    [PDF] BOINC: A System for Public-Resource Computing and Storage
    BOINC is a software system and platform for public-resource distributed computing, making it easy for scientists to create and operate projects.
  6. [6]
    Install BOINC
    BOINC is a program that lets you donate your idle computer time to science projects like Climateprediction.net, Rosetta@home, GPUGrid, and many others.
  7. [7]
    Help maintain and develop BOINC
    Overview. BOINC is open-source; it's distributed under the LGPL open source license. The BOINC source code is stored in a GitHub repository.Missing: features cross-
  8. [8]
    A Conversation with David Anderson - ACM Queue
    Aug 18, 2005 · In 2002 we started the BOINC project to create an infrastructure that could be used by existing projects such as SETI@home and Climateprediction ...Missing: origins | Show results with:origins
  9. [9]
    David P. Anderson - BOINC
    I am Principal Investigator or co-PI on six National Science Foundation grants supporting BOINC. From 1997 to 2016 I directed SETI@home, a research project that ...Missing: first Predictor@
  10. [10]
    [PDF] BOINC: A System for Public-Resource Computing and Storage
    BOINC (Berkeley Open Infrastructure for Network. Computing) is an platform for public-resource distributed computing. BOINC is being developed at U.C. Berkeley.<|control11|><|separator|>
  11. [11]
  12. [12]
    World Community Grid | IBM
    World Community Grid went online in 2004 with a mission to tackle society's challenges by harnessing the world's spare computing power.Missing: BOINC | Show results with:BOINC
  13. [13]
    Client release notes · BOINC/boinc Wiki - GitHub
    Support containerized tasks with Docker. This requires installing Docker or Podman. Grey out projects in the 'Add Project' wizard that are already added ...
  14. [14]
    Thread 'BOINC for Android launched'
    Aug 21, 2013 · I downloaded the app yesterday and was able to create a profile for my android at the World Community Grid so my desktop continues to be ...Thread 'New BOINC Android client released'Thread 'Android client version 7.18.1 released.' - BOINCMore results from boinc.berkeley.eduMissing: 2011 evolution
  15. [15]
    Active BOINC Projects
    Active BOINC Projects Table by BOINC Synergy.<|control11|><|separator|>
  16. [16]
    VersionHistory · BOINC/boinc Wiki - GitHub
    BOINC version history. Changes in 7.14.2 released: 11 October 2018. Changes in 7.12.1 released: 15 July 2018. Changes in 7.12.0 released: 15 July
  17. [17]
    VirtualBox · BOINC/boinc Wiki - GitHub
    BOINC uses virtualization to allow scientists to develop applications on their preferred operating system (usually Linux) and then run them on volunteered ...
  18. [18]
    OpenPandemics - COVID-19 | Research - World Community Grid
    The research team wants not only to help find treatments for COVID-19, but also to create a fast-response, open source toolkit that will help all scientists ...Missing: 2020 | Show results with:2020
  19. [19]
    Thread 'BOINC client 8.2.4 released'
    Jul 10, 2025 · The 8.2.4 version of the BOINC client has been released for all platforms. Download it here. Release notes are here. The new version supports Docker apps.Thread 'BOINC 8.2.4'Thread 'Docker install is a feasco' - BOINCMore results from boinc.berkeley.edu
  20. [20]
    Releases · BOINC/boinc - GitHub
    BOINC Client/Manager Release 8.2.2 Pre-release. Pre-release. Linux only ... [drupal] added Apple GPU support to project preferences by @brevilo in #5569 ...
  21. [21]
    [PDF] BOINC: A Platform for Volunteer Computing 1. Introduction - arXiv
    Dec 9, 2018 · BOINC runs on Android but not Apple iOS, because Apple's rules bar apps from dynamically downloading executable code. It also is not ...
  22. [22]
    Software and data architecture · BOINC/boinc Wiki - GitHub
    Apr 7, 2025 · This is due in large part to BOINC's architecture. This has three aspects: software, components, and data. Software. This is discussed here.Missing: core | Show results with:core
  23. [23]
    Creating and Configuring a BOINC Project - Spy Hill .net
    The basic components of a BOINC server are: a database server (MySQL); the BOINC daemons (called the 'scheduler', 'feeder', 'transitioner', 'validator' ...
  24. [24]
    API paper - BOINC
    BOINC (Berkeley Open Infrastructure for Network Computing) is a middleware system for volunteer computing [2]. BOINC is being used by a number of projects, ...
  25. [25]
    Validators · BOINC/boinc Wiki - GitHub
    A validator is a program that decides whether completed jobs are valid. You must specify a validator for each application in your project.Missing: system | Show results with:system
  26. [26]
    TrickleImpl · BOINC/boinc Wiki - GitHub
    Open-source software for volunteer computing and grid computing. - TrickleImpl · BOINC/boinc Wiki.
  27. [27]
    CreditNew · BOINC/boinc Wiki - GitHub
    A new system for runtime estimation and credit. Terminology: BOINC estimates the peak FLOPS of each processor. For CPUs, this is the Whetstone benchmark score.Missing: validation | Show results with:validation
  28. [28]
    An Incentive System for Volunteer Computing - BOINC
    Volunteer computing is a computing paradigm that uses large numbers of computers, volunteered by members of the general public, to provide computing and storage ...
  29. [29]
    Download BOINC client software
    Download BOINC client software ; 6.12.22, Recommended version, Download (1.69 MB) ; Android Android version 4.1 and later for ARM, AArch64, x86, and x86_64Missing: support | Show results with:support
  30. [30]
    Client configuration · BOINC/boinc Wiki - GitHub
    Nov 8, 2024 · There are several XML-format configuration files: cc_config.xml , nvc_config.xml , and (for each project) app_config.xml .
  31. [31]
    Create a BOINC server (cookbook) - GitHub
    Mar 26, 2025 · This is a cookbook for creating a BOINC server on Ubuntu 22.04. You can use Xubuntu (which uses less memory) instead of Ubuntu; everything should work.
  32. [32]
    News archive - BOINC
    The 7.24.1 version of the BOINC client software has been released for Windows, Mac, and Android. Download it here. Release notes are here.<|control11|><|separator|>
  33. [33]
    Thread 'BOINC in Windows 10'
    When BOINC loads I get an error "Notice from BOINC - BOINC can't access Internet - check network connection or proxy configuration.Missing: bandwidth | Show results with:bandwidth
  34. [34]
    Thread 'No usable GPUs found. AMD Radeon HD6750' - BOINC
    I have always had this message, but I recently upgraded my video card to a Radeon HD6750 and according to documentation on this site, this GPU is usable.Missing: troubleshooting common issues incompatibilities
  35. [35]
    BOINC Manager - GitHub
    Jun 23, 2024 · The BOINC Manager is a 'control panel' for BOINC. It provides a graphical interface for monitoring and controlling the BOINC Client.
  36. [36]
    Account managers · BOINC/boinc Wiki - GitHub
    Jun 15, 2024 · BOINC Account Manager (BAM!) and GridRepublic. These AMs show you a list of BOINC projects and let you choose projects by checking boxes.
  37. [37]
    Getting started - BOINC
    To create a BOINC account, go to the Create account page, fill out the form, and save the email with your account ID. Then, download and install BOINC.Missing: web- interfaces
  38. [38]
    Choosing and joining projects · BOINC/boinc Wiki - GitHub
    Apr 9, 2025 · Visit the project's web site and create an account. In the BOINC manager's Simple view click ''Add Project'' or, in the manager's Advanced view, ...Missing: websites | Show results with:websites
  39. [39]
    Creating a skin for the BOINC Manager - GitHub
    Jun 15, 2024 · Skins allow you to customize how the BOINC Manager looks in the simple view, the advanced view, and wizard dialogues.Missing: widgets | Show results with:widgets
  40. [40]
    BOINC add-on software
    BOINC add-on software enhances BOINC, but is not developed by the BOINC project. Examples include Windows, Linux, Mac, mobile, browser tools, and web ...Missing: customization skins notifications
  41. [41]
    Rules and policies - BOINC
    If you want to be anonymous, choose a name that doesn't reveal your identity. If you participate in BOINC message boards, information about your computer ...
  42. [42]
    New app puts idle smartphones to work for science - Berkeley News
    Jul 22, 2013 · The new Android app, also called BOINC, will be available Monday, July 22, from the Google Play Store and works on Android versions 2.3 or later ...
  43. [43]
    Download BOINC client software for Android
    Download BOINC client software for Android. Android Android version 4.1 and later for ARM, AArch64, x86, and x86_64. Amazon Fire tablets: install from the ...Missing: support | Show results with:support
  44. [44]
    Problems with suspension of computation and network - BOINC
    Aug 17, 2023 · BOINC client thinks the battery charge level is 0% - and suspends computation - but the OS and BOINC GUI both say battery level is 100%.Missing: features ARM scheduling offline<|separator|>
  45. [45]
    Is it allowed for an iOS app to run volunteer computing projects?
    Aug 10, 2017 · Whether Apple would allow such an app on the iOS App Store though is another matter. BOINC has an Android app, but no iOS app, and their FAQ ...
  46. [46]
    Thread 'What happened to the iOS client?' - BOINC
    May 30, 2017 · I've seen some discussions on building an iOS app, but the discussion seems to have stopped some years ago. Is this still in the works?Thread 'Petition for IoS Boinc app'Thread 'Is it possible to run boinc on iPhone/iPad?'More results from boinc.berkeley.eduMissing: restrictions | Show results with:restrictions
  47. [47]
    Raspberry Pi BOINC Tutorial - Pi My Life Up
    Oct 28, 2022 · In this Raspberry Pi BOINC tutorial, I take you through the steps to getting BOINC setup and processing tasks correctly.Missing: IoT | Show results with:IoT<|separator|>
  48. [48]
  49. [49]
    Android BOINC 7.18.1 pauses when run on DC power with battery ...
    Aug 7, 2022 · When reactivating the display on the MediaPad, the app occasionally crash. At next startup, all the running tasks have restarted from the ...Missing: data | Show results with:data
  50. [50]
    Volunteer your Computer - Climateprediction.net
    We run climate modelling experiments using the home computers of thousands of volunteers. ... The main setting you might want to change is when BOINC runs models ...Missing: mobile adoption
  51. [51]
    [PDF] Volunteer Computing on Mobile Devices: State of the Art and Future ...
    Jan 3, 2015 · ... BOINC projects to mobile devices. In February 2014, the integration of Android devices into the BOINC system has been extensively promoted ...
  52. [52]
    Choosing BOINC projects - University of California, Berkeley
    BOINC is used by many projects. You can participate in any number of these projects. To decide whether to participate in a project, read its web site and ...
  53. [53]
    Rosetta@home
    ### Summary of Rosetta@home (as of 10 Nov 2025)
  54. [54]
  55. [55]
    World Community Grid: Home
    Volunteers have donated their spare computing power towards research initiatives. 7.7M. Computers and Android devices have contributed to the vast network that ...Log in · Global Statistics · Projects · Research OverviewMissing: counts | Show results with:counts
  56. [56]
    Einstein@Home
    ### Summary of Einstein@Home (as of 2025)
  57. [57]
    climateprediction.net | University of Oxford
    ### Summary of climateprediction.net (as of 2025)
  58. [58]
    cpdnboinc
    A new multicore configuration of the OpenIFS application, known as Tl319, is being released by CPDN. This is the first time CPDN has deployed a multicore app ...
  59. [59]
    BOINC in Retrospect - David P. Anderson
    BOINC is a software system for volunteer computing: it lets people donate time on their home computers and smartphones to science research projects.
  60. [60]
    SIMAP—the database of all-against-all protein sequence similarities ...
    SIMAP covers all major public protein databases as well as many consistently re-annotated metagenomes from different repositories.
  61. [61]
    [PDF] LHC@Home: a BOINC-based volunteer computing infrastructure for ...
    Oct 26, 2017 · The LHC@Home BOINC project has provided computing capacity for numerical simulations to researchers at CERN since 2004, and has since. 2011 been ...
  62. [62]
    Final update [not actually] - SETI@home
    Mar 3, 2023 · The @setiathome project effectively closed on 19th November 2020, following two lots of severe damage to the Arecibo telescope in August and ...SETI@home hibernationOK, it's time to say "good bye" to SETI@home. :( Which (BOINC or ...More results from setiathome.berkeley.edu
  63. [63]
    SETI at home Going into Hibernation - SETI Institute
    UC Berkeley has announced that the volunteer computing part of SETI@home will stop distributing work and go into hibernation on March 31.
  64. [64]
    Publications by BOINC Projects
    This is a list papers containing scientific results arising, directly or indirectly, from BOINC-based computing.Missing: NSF | Show results with:NSF
  65. [65]
    BOINC in Retrospect - David P. Anderson
    BOINC is a software system for "volunteer computing": it lets people donate time on their home computers and smartphones to science research projects. It has ...<|separator|>
  66. [66]
    BOINC-based projects projects now have 80721 participants in 188 ...
    Jan 19, 2005 · BOINC-based projects projects now have 80,721 participants in 188 countries. Based on current credit statistics, together they supply 106 ...Missing: 2003 | Show results with:2003
  67. [67]
    Top 100 multi-project BOINC participants
    Feb 15, 2025 · Updated 10 Nov 2025. 1. Ian&Steve C. is contributing 898,029 GFLOPS. pie chart. 2. stoneageman is contributing 519,183 GFLOPS.Missing: total hosts FLOPS
  68. [68]
    Results of the BOINC Census 2022 - The Science Commons Initiative
    Firstly we have computing devices. We find that generally people have 1-5 computers running BOINC and that the use of mobile devices is heavily skewed to no use ...
  69. [69]
  70. [70]
  71. [71]
    [1903.01699] BOINC: A Platform for Volunteer Computing - arXiv
    Mar 5, 2019 · BOINC, a widely-used open-source middleware system for volunteer computing, addresses these challenges. We describe its features, architecture, and ...Missing: energy attrition validation overhead
  72. [72]
    Volunteer computing: Requirements, challenges, and solutions
    Aug 6, 2025 · Existing solutions for harnessing this power, such as volunteer computing (e.g., BOINC) ... This work describes different validation strategies ...
  73. [73]
    [PDF] VOLUNTEER COMPUTING: - CERN Indico
    Developers and users. Improve the energy efficiency of their own codes, making use of algorithmic, programming, and hardware tools. Design and implement.
  74. [74]
    Message boards - BOINC
    These messages boards are for discussion of BOINC, not projects (such as Einstein@home, World Community Grid, and so on). To discuss a project, please use its ...Missing: feedback | Show results with:feedback