The free edition of Pandora FMS, maintained by the community

Open monitoring. UNIX in spirit: small, clear, modifiable

Install Pandora OPEN easily

Choose your preferred method: Docker for immediate startup or installation from source for Linux and Ubuntu environments. In both cases, you will have a fully open, flexible monitoring platform ready to integrate into your infrastructure.


mkdir $HOME/pandorafms; cd $HOME/pandorafms
wget http://pfms.me/centos8-docker-compose
docker-compose -f centos8-docker-compose up
  


curl -SsL https://raw.githubusercontent.com/pandorafms/pandorafms/develop/extras/deploy-scripts/pandora_deploy_community_el8_gh.sh | bash
  


curl -SsL https://raw.githubusercontent.com/pandorafms/pandorafms/develop/extras/deploy-scripts/pandora_deploy_community_el9_gh.sh | bash
  


curl -SsL https://raw.githubusercontent.com/pandorafms/pandorafms/develop/extras/deploy-scripts/
  
Pandora Open Login
Pandora Open Main dashboard
Pandora Open agent view
Pandora Open Login
Pandora Open Main dashboard
Pandora Open agent view

What is Pandora Open?

Pandora Open is the fully free edition of Pandora FMS. Its purpose is to provide a stable, understandable, and modifiable monitoring foundation for administrators and teams who prefer to work with open, auditable software without dependencies on commercial services.

The project is entirely community-maintained: reviews, patches, technical decisions, and the roadmap are public and recorded in the repository. There are no proprietary components, no reserved features, and no modules subject to external licenses.

All code has been released under GPLv2 since 2004. The repository contains the complete development history, including active branches, legacy changes, design decisions, and third-party contributions. The development cycle is transparent: what gets merged, what is rejected, and why is publicly documented.

Pandora Open does not provide commercial support, warranties, or associated services. What is distributed is code that anyone can study, modify, or adapt to their needs, in accordance with the GPLv2 and the project’s community governance.

What does Pandora Open include?

Observability and monitoring

Pandora Open delivers a complete observability layer for any infrastructure, combining remote monitoring, advanced network testing, and local agents for Windows, Linux, and Mac. Its unified approach enables asset discovery and supervision of critical services.

  • Remote monitoring (SNMP, TCP, HTTP, ICMP, WMI, SSH)
  • Customizable plugins
  • Native agents
  • Network discovery
  • Network mapping
  • SNMP explorer
  • SNMP traps console
  • Historical graphs

Visual dashboards and data visualization

Pandora Open enables the creation of visual dashboards, custom views, and GIS maps that transform telemetry into actionable information. Its visualization engine supports trend analysis, scheduled reporting, and a clear overview of the entire infrastructure status.

  • Customizable visual screens
  • Dashboards and scorecards
  • Real-time geographic maps (GIS)
  • Scheduled reports

Customization and flexibility

Pandora Open guarantees a fully open, adaptable, and community-oriented environment. It runs on Linux or BSD, supports visual customization through CSS, and offers multilingual capabilities, preserving the essence of free software.

  • Server on Linux or BSD
  • Multilingual support
  • Visual customization with CSS
  • Open architecture

Management, automation and integrations

With a flexible and open approach, Pandora Open integrates intelligent alerts, automation workflows, and a REST API to extend its capabilities. The platform supports inventory management, multitenant environments, and operates on an open database designed to scale without restrictions.

  • Alerts and notifications
  • REST API
  • Open database (MariaDB)
  • Internal auditing
  • Asset inventory
  • Multitenant support

Move to monitoring without lock-in: Pandora OPEN gives you real control, open code and the freedom to evolve at your own pace

Project principles

Pandora Open Manifesto

The Pandora Open Manifesto defines the project’s values and commitments: full code openness, transparent collaboration, and technical meritocracy, fostering a responsible community that contributes and shares without commercial pressure, protecting software freedom and the overall integrity.

Read the manifesto

Governance guidelines

Governance in an Open Source project defines how changes are decided, who maintains the code, and how disagreements are managed, ensuring transparency, open participation, and technical rigor through agreed rules that preserve continuity, development stability, and the project vision.

Read the guidelines

Community as support

Technical support is provided exclusively through community channels: GitHub tracker, forums, contributions, and collaborative documentation. The community sets the development pace, reports issues, and proposes improvements.

Flexible and transparent deployment

Official packages, scripts, and containers are published in open repositories. Any user can review, adapt, or automate deployment according to their needs.

General and license

What is the difference between Pandora OPEN and Pandora FMS?

Pandora OPEN is the 100% free branch of Pandora FMS starting from version 777. It shares the same origin but is separated from the commercial version and follows a purely open source development path.

Are there functional differences?

Yes. However, if you previously used Pandora FMS Community, you do not lose functionality: Pandora OPEN maintains all open capabilities and even includes some former Enterprise features, such as remote editing of agent configuration files.

Will there be updates to the Open version?

Yes. New versions and fixes are published in the GitHub code repository, from where you can update your environment whenever needed.

Can I offer services to third parties with Pandora OPEN?

Yes. You may provide managed services, consulting, or support based on Pandora OPEN without restrictions from the project.

Can I purchase official support for Pandora OPEN?

Any company may offer support for Pandora OPEN, but there is no “official” provider certified by the project. Support is always contracted privately.

Is there a company behind Pandora OPEN?

The company that owns the Pandora FMS trademark contributes code and retains intellectual property of the brand, but it does not provide support, warranties, or commercial services associated with Pandora OPEN.

Can I use Pandora OPEN in critical or production environments?

Yes. GPLv2 does not restrict production use. However, Pandora OPEN provides no warranties, so responsibility lies with the deploying organization or the support provider.

Can I monetize services based on Pandora OPEN?

Yes. GPLv2 allows selling services, support, or integrations as long as any redistributed code remains under GPLv2 and its terms are respected.

What is the relationship between Pandora OPEN and the former Community version?

Pandora OPEN is the natural continuation of Pandora FMS Community. It maintains the same functional base and free spirit, but with even more open development and no direct dependency on commercial decisions.

Community and governance

Who maintains Pandora OPEN?

The project is maintained by the community through the public repository. Each change undergoes technical review. Some developers linked to Pandora FMS contribute, but maintenance does not follow a commercial agenda.

How are integrations decided?

Contributions are submitted via pull request on GitHub. They are reviewed for technical coherence, stability impact, and compliance with project rules. The community may debate each proposal.

How are vulnerabilities or security patches handled?

Any user can report issues on GitHub. Fixes are published openly when ready. There is no SLA or guaranteed timeline; the pace is set by the community.

Is there a public roadmap?

Development is open, and priorities are reflected in repository issues, discussions, and active branches. There is no closed roadmap controlled by a commercial entity.

Where can I get technical help?

Primarily from the community, through the forum and technical threads where users share experiences, solutions, and patches. Participation is voluntary.

What if something does not work as expected?

Check logs, enable debug mode, and gather relevant information. Then publish it on the forum or open a GitHub issue so the community can analyze and guide you.

Deployment and requirements

Is Pandora OPEN compatible with Pandora FMS Enterprise?

At the agent and basic architecture level, yes: remote plugins, agents, scripts, and SQL queries will continue to work. Proprietary Enterprise features are not included and are not interchangeable.

Does Pandora OPEN have official installers or packages?

Source code is available on GitHub. Binary packages may be generated by the community or third parties. An automatic installation script exists, but there are no “official” commercial builds with support.

Does Pandora OPEN require a specific database?

It is designed to work with MySQL or MariaDB. Other databases may function with adaptations but are not officially supported or tested by the project.

Can I deploy Pandora OPEN in containers?

Yes. The project does not distribute official images, but the community may create Docker or Podman containers. As long as GPLv2 is respected, any image is valid.

Do I need advanced knowledge to use Pandora OPEN?

No. With basic Linux knowledge, configuration file editing, and terminal usage, you can perform an initial deployment. Complexity depends on what you intend to monitor.

How do I get started with monitoring?

Install the server, deploy an agent on a test machine, and verify data flow in the console. The repository includes minimal examples and basic documentation to help you build your environment.

Security, data and integrations

Does Pandora OPEN include telemetry or proprietary components?

No. All code is open, auditable, and available in the public repository. No closed binaries or hidden telemetry mechanisms are included.

What about plugins or extensions?

Free plugins remain available in public repositories. Commercial or proprietary plugins are not part of Pandora OPEN and cannot be distributed with the project due to licensing constraints.

Does Pandora OPEN collect user data?

No. The system does not send information to external services by default. Any operation is visible and can be reviewed directly in the code.

Can I integrate Pandora OPEN with other tools?

Yes. You can integrate it with any solution that does not depend on proprietary code. The community may contribute connectors, scripts, and API usage within the repository.

What happens if I stop updating Pandora OPEN?

Nothing in the short term: the system will continue running. However, using outdated versions implies assuming security and compatibility risks on the part of the organization managing the platform.

Pandora Open Manifesto (pandoraopen.io)

Pandora Open is an Open Source project committed to knowledge freedom, transparency, and technological sovereignty. This manifesto defines the principles that guide its development and how the community makes decisions and maintains the code.

1. Independence without affiliations

Pandora Open is an autonomous project, with no ties to corporate, state, or geopolitical agendas. Its commitment is to knowledge freedom and to the right of everyone to use, understand, and improve the software they rely on.

2. Radical code freedom

Pandora Open is not a “community edition” nor a limited version. It is fully free software, published under an open license and maintained so that anyone can audit, modify, and redistribute the code without artificial restrictions.

3. Absolute independence

Pandora Open and Pandora FMS are different projects. Although they share part of the codebase and diverged starting from version 777, they will not share further code nor align their roadmaps. Pandora Open follows its own path, guided by the community and by those who defend technological sovereignty.

4. Acknowledged origin, free destination

The common origin with Pandora FMS is acknowledged, but control and direction of Pandora Open belong to the community. It is published so others can take it further, with full freedom to evolve.

5. Self-management and horizontality

Project governance is open, without imposed hierarchies. Decisions are made publicly, by consensus, and contributions are valued for their technical merit, not their origin.

6. Transparency as a principle

Every decision, every line of code, and every contribution will be visible. There are no reserved features, no backdoors, and no hidden dependencies. Transparency is not an added value; it is the foundation of the project.

7. Free code to reclaim freedom

In a world where software is used as a tool of control, defending free code means defending the ability to decide. As Emma Goldman said: “If I can’t dance, it’s not my revolution.” Here, if we cannot read and write the code, it is not our software.

8. Technological sovereignty in infrastructure and oversight

The concentration of digital infrastructure and technological oversight in the hands of a few power blocs turns blind dependency into a direct threat to the autonomy of countries, companies, and individuals. Pandora Open holds that security cannot rely solely on open code, but also on the transparency of intentions and practices of those who lead it. A system is truly secure when its foundations — both technical and human — are free of hidden interests and accountable only to the community that uses and maintains it.

Pandora Open is not just a fork: it is a commitment to independence, transparency, and community. A project born free to remain free.

Code is knowledge. Knowledge is power. Power must be free.

Pandora Open Governance Guidelines

These guidelines define how Pandora Open is managed from its inception, ensuring that the project preserves its independence, its openness, and its radically free spirit over time.

1. Structural independence

Pandora Open and the commercial version of Pandora FMS will always remain separate projects, with no exchange of code, features, or strategic resources. No decision within Pandora Open may be subordinated to commercial, political, or state interests.

2. Community governance

The project will be led by an Open Steering Committee composed of active community members. Membership on the committee will be based on merit, including the quality of contributions, sustained involvement, and commitment to the manifesto’s values. The committee may be periodically renewed through public voting among contributors with a verified track record.

3. Full transparency

All strategic decisions, directional changes, and technical debates must take place in public spaces accessible to any user. Committee meetings will generate public minutes that are archived, and the code change history will be fully open, with no private development branches.

4. License and code openness

All code of Pandora Open will be published under the GPLv2 license, without additional restrictive clauses. Proprietary modules or closed features will not be allowed within the project’s core.

5. Technical decision-making

Technical decisions will be made by consensus whenever possible and, if not, by committee vote. Technical proposals (RFCs) must be published in advance, include a review period, and receive public feedback before approval.

6. Protection against capture

No company, organization, or government may exercise majority control over the committee. Representation limits per entity will be established to prevent conflicts of interest and safeguard the project’s independence.

7. Funding and resources

Project funding, if any, must come from transparent and diversified sources. All income and expenses related to Pandora Open will be public and accessible to the community.

8. Relationship with the project’s origin

Pandora Open acknowledges that its code derives from the initial work of Pandora FMS, but it will have no operational, strategic, or commercial subordination to this or any other company. The Pandora FMS company may participate in the community under the same conditions as any other contributor.

9. Continuity guarantee

The official repository will have at least two independent mirrors controlled by different committee members to prevent loss or takeover of the code. In the event of committee dissolution, the community may call open elections to reconstitute it.

10. Review and evolution of the guidelines

These guidelines may only be amended through an open process, with public consultation and approval by a qualified majority of the active community.