- Docs »
- pfSense® software »
- Introduction
- Give Feedback
Next
Releases
Previous
Can pfSense software meet regulatory requirements
Many consulting companies offer solutions based on pfSense® software to theircustomers. A business or individual can load pfSense software for themselves,friends, relatives, employers, and, yes, even customers, so long as theTrademark Guidelines and Apache 2.0 license requirements as detailed on the website areobeyed by all parties involved.
What can not be offered is a commercial redistribution of pfSense® software, forexample the guidelines do not permit someone to offer “Installation of pfSense®software” as a service or to sell a device pre-loaded with pfSense® software tocustomers without the prior express written permission of ESF pursuant to thetrademark policy.
- Example 1
A consultant may offer firewall services (e.g. “Fred’s Firewalls”), withoutmentioning pfSense® software or using the logo in their advertising, marketingmaterial, and so on. They can install pfSense® software and manage it fortheir customers.
- Example 2
Fred’s Firewalls may make a customized distribution pfSense® software withtheir own name and logo used in place of the pfSense marks. They can use thepfSense marks to truthfully describe the origin of the software, such as“Fred’s Firewall software is derived from the pfSense CE source code.” Eventhough Fred’s Firewall is based on pfSense® software, it cannot bereferred to as “pfSense® software” since it has been modified.
- Example 3
Fred’s Firewalls may sell their customized firewall distribution pre-loaded onsystems to customers, so long as the relationship to pfSense software isclearly stated.
The Apache 2.0 license only applies to the software and not the pfSense name andlogo, which are trademarks and may not be used without a license. Reading andunderstanding the trademark policy document is required before oneconsiders selling pfSense software.
Contributing Back to the Project¶
We ask anyone profiting by using pfSense software to contribute to the projectin some fashion. Ideally with the level of contributions from a business orindividual corresponding to the amount of financial gain received from use ofpfSense software. Many paths exist for resellers and consultants to contribute.For the long term success of the project this support is critically important.
Purchase hardware and merchandise from the Netgate Store.
Become a Netgate Partner to resell Netgate hardware pre-loaded with pfSensesoftware.
Development contributions - Dedicate a portion of internal developers’ time toopen source development.
Help with support and documentation - Assisting users on the forum and mailinglist, or contributing documentation changes, aides the overall project.
Support subscription via Netgate TAC Having direct access to our team forany questions or deployment assistance helps ensure success.
Using the pfSense Name and Logo¶
The “pfSense” name and logo are trademarks of Electric Sheep Fencing, LLC.
The pfSense software source code is open source and covered by the Apache 2.0 license.That license only covers the source code and not our name and trademarks,which have restricted usage.
We think it is great that people want to promote and support the pfSenseproject. At the same time, we also need to verify that what is referred to as“pfSense” is a genuine instance of pfSense software and not modified in anyway.
The pfSense name and logo MAY NOT be used physically on a hardware device.
For example: A sticker, badge, etching, or similar rendering of the pfSensename or logo is NOT allowed.
The pfSense logo MAY NOT be used on marketing materials or in other wayswithout a license, including references on websites.
The pfSense name MAY be used to describe the case that a product is basedon a pfSense distribution, but the designated product name may not includepfSense or a derivative. Basically stating facts regarding product origin isacceptable. Anything that implies that a product is endorsed by or made by ESFor the pfSense project is not allowed.
Examples:
“Blahsoft Fireblah based on pfSense software” – Acceptable
“Blahsoft pfSense Firewall” – NOT Allowed
ONLY an UNMODIFIED version of pfSense software can still be called“pfSense software”.
If the source code has been changed, compiled/rebuilt separately, includedextra file installations such as themes or add-on scripts, or any othercustomizations, it can not be called “pfSense software”, it must becalled something else.
Trademark protection aside, this requirement preserves the integrity andreputation of the pfSense project. It also prevents unverified changes thatmay be questionably implemented from being attributed to pfSense.
If a pfSense distribution is modified, the resulting software CANNOT becalled “pfSense” or anything similar. The new name must be distinct frompfSense. Trademark law does not allow use of names or trademarks that areconfusingly similar to the pfSense Marks. This means, among other things, thatlaw forbids using a variation of the pfSense Marks, their phoneticequivalents, mimicry, wordplay, or abbreviation with respect to similar orrelated projects, products, or services (for example, “pfSense Lifestyle,”“PFsense Community,” “pf-Sense Sensibility,” “pfSensor”, etc., allinfringe on ESF’s rights).
Examples:
“pfSomething”, or “somethingSense” – INFRINGING references
“ExampleWall”, “FireWidget” – NON-Infringing references
The “pfSense” name MAY NOT be used in a company name or similar. A companyCANNOT be named “pfSense Support, Ltd” or “pfSense Experts, LLC”, or useit in a domain name or subdomain reference. However, the company can statesupport for pfSense software, offer training for pfSense software, etc.
There MUST be a distinction between a company name and pfSense or ElectricSheep Fencing, LLC. No relationship or endorsem*nt can be stated or impliedbetween the two companies, unless we have explicitly licensed and agreed tosuch a statement.
