graylog.org Open in urlscan Pro
2606:4700:3108::ac42:2bb4  Public Scan

Form analysis
1 forms found in the DOM

GET https://graylog.org/

<form role="search" method="get" class="ekit-search-group" action="https://graylog.org/"> <input type="search" aria-label="search-form" placeholder="Search..." value="" name="s" class="ekit_search-field nitro-lazy"> <button type="submit"
    class="ekit_search-button" aria-label="search-button"> <svg aria-hidden="true" class="e-font-icon-svg e-fas-search" viewBox="0 0 512 512" xmlns="http://www.w3.org/2000/svg">
      <path
        d="M505 442.7L405.3 343c-4.5-4.5-10.6-7-17-7H372c27.6-35.3 44-79.7 44-128C416 93.1 322.9 0 208 0S0 93.1 0 208s93.1 208 208 208c48.3 0 92.7-16.4 128-44v16.3c0 6.4 2.5 12.5 7 17l99.7 99.7c9.4 9.4 24.6 9.4 33.9 0l28.3-28.3c9.4-9.4 9.4-24.6.1-34zM208 336c-70.7 0-128-57.2-128-128 0-70.7 57.2-128 128-128 70.7 0 128 57.2 128 128 0 70.7-57.2 128-128 128z">
      </path>
    </svg> </button> </form>

Text Content

This website stores cookies on your computer. These cookies are used to collect
information about how you interact with our website and allow us to remember
you. We use this information in order to improve and customize your browsing
experience and for analytics and metrics about our visitors both on this website
and other media. To find out more about the cookies we use, see our Privacy
Policy

If you decline, your information won’t be tracked when you visit this website. A
single cookie will be used in your browser to remember your preference not to be
tracked.

Accept Decline

Calling All Speakers | Submit Your Topic >>>


 * Products
   * GRAYLOG SECURITY
   * Graylog Enterprise
   * GRAYLOG OPEN
   * GRAYLOG CLOUD
   * Graylog API Security
   
   
   GRAYLOG SECURITY
   
   
   GRAYLOG ENTERPRISE
   
   
   GRAYLOG OPEN
   
   
   GRAYLOG API SECURITY
   
   
   Graylog Illuminate
   Graylog Cloud
 * Solutions
   * GOVERNMENT
   * FINTECH
   * EDUCATION
   * TELECOM
   * Healthcare
   * Audit & Regulatory Compliance
   * Centralized Log Management
   * Security Operations
   * Threat Hunting
   * Threat Detection and Incident Response
   
   
   INDUSTRY
   
   
   
   
   BANKING & INSURANCE
   
   
   EDUCATION
   
   
   HEALTHCARE
   
   
   MSSPS
   
   
   PUBLIC SECTOR
   
   
   SAAS
   
   
   SUPPLY CHAIN
   
   
   USE CASE
   
   
   
   
   AUDIT & REGULATORY COMPLIANCE
   
   
   CENTRALIZED LOG MANAGEMENT
   
   
   SECURITY OPERATIONS
   
   
   THREAT DETECTION & INCIDENT RESPONSE
   
   
   THREAT HUNTING

 * Learn
   * Resource Library
   * Webinars & Events
   * Blog
   * Documentation
   
   
   ABOUT
   
   
   RESOURCE LIBRARY
   
   
   WEBINARS & EVENTS
   
   
   BLOG

 * Support
   * Customer Support
   * Documentation
   * Academy
   * Open Community
   
   
   CUSTOMER SUPPORT
   
   
   DOCUMENTATION
   
   
   ACADEMY
   
   
   OPEN COMMUNITY

 * Pricing
 * Contact Us


X

Free Tools
See Demo


GRAYLOG V4.0 LICENSING SSPL

 * February 4, 2021
 * The Graylog Team


WHY ARE WE CHANGING THE LICENSE FOR GRAYLOG?

MongoDB issued its Server Side Public License (SSPL) license in 2018. While this
initially drew negative feedback from the open source community, after some
clarifications it was well received as a way to address the community’s
concerns, and lack of licensing, around open source Software as a Service
offerings. This change was designed to make sure that companies who do run
publicly available open source software as a service, are giving back to the
community.

The SSPL is designed to protect open source projects from international cloud
providers that were testing the boundaries of the GPL, potentially harming the
open source community. As a part of that community, we want to do our part to
make sure those that benefit from open source tools like Graylog also give back.

It should be noted that the new license maintains all of the same freedoms the
community has always had with Graylog under GPL – they are free to use, review,
modify, and redistribute the source code. The only changes are additional terms
that make explicit the conditions for offering a publicly available Graylog as a
service.


WHAT IS THE LICENSE CALLED AND WHAT WILL BE LICENSED UNDER IT?

The new license is called the Server Side Public License (SSPL). All Graylog
Open Source patch releases and versions released on or after the general
availability of v4.0 (Graylog v4.0), will be subject to this new license.


IS THE SSPL ON AN OSI-RECOGNIZED OPEN SOURCE LICENSE?

The SSPL is based on the GNU General Public License, but it is a new license
introduced by MongoDB, not the Free Software Foundation. The SSPL has not been
approved by the OSI.


WHAT SPECIFICALLY IS THE DIFFERENCE BETWEEN THE GPL AND THE SSPL?

The only substantive modification is section 13, which makes clear the condition
to offering Graylog as a service. A company that offers a publicly available
Graylog as a service must release the software it uses to offer such service
under the terms of the SSPL, including the management software, user interfaces,
application program interfaces, automation software, monitoring software, backup
software, storage software and hosting software, all such that a user could run
an instance of the service using the source code made available.

Section 13 of the SSPL reads as follows:

a. “If you make the functionality of the Program or a modified version available
to third parties as a service, you must make the Service Source Code available
via network download to everyone at no charge, under the terms of this License.
Making the functionality of the Program or modified version available to third
parties as a service includes, without limitation, enabling third parties to
interact with the functionality of the Program or modified version remotely
through a computer network, offering a service the value of which entirely or
primarily derives from the value of the Program or modified version, or offering
a service that accomplishes for users the primary purpose of the Software or
modified version.”

b. “Service Source Code” means the Corresponding Source for the Program or the
modified version, and the Corresponding Source for all programs that you use to
make the Program or modified version available as a service, including, without
limitation, management software, user interfaces, application program
interfaces, automation software, monitoring software, backup software, storage
software and hosting software, all such that a user could run an instance of the
service using the Service Source Code you make available.” A full copy of the
SSPL is here.


WHY IS THE SSPL BASED ON GPLV3 INSTEAD OF AGPLV3?

The AGPL is a modified version of GPL v3. The only additional requirement of
AGPL is in section 13: if you run a modified program on a server and let other
users communicate with it there, you must open source the source code
corresponding to your modified version, known as the “Remote Network
Interaction” provision of AGPL.

There is some confusion in the marketplace about the trigger and scope of the
Remote Network Interaction provision of AGPL.

As a result, MongoDB decided to base the SSPL on GPL v3 and to add a new section
13 which clearly and explicitly sets forth the conditions to offering the
licensed program as a third-party service. As we are in agreement with this
approach, we have opted to use MongoDB’s SSPL in place of AGPLv3.


IS THERE ANY DIFFERENCE BETWEEN GRAYLOG’S SSPL AND MONGODB’S?

No. The license is identical and MongoDB is encouraging other open source
vendors to use the SSPL.


DOES SECTION 13 OF THE SSPL APPLY IF I’M OFFERING GRAYLOG AS A SERVICE FOR
INTERNAL-ONLY USE?

No. We do not consider providing Graylog as a service internally or to
subsidiary companies to be making it available to a third party.


WILL GRAYLOG CONTINUE TO PROVIDE OPEN SOURCE SOFTWARE?

Yes, Graylog will continue to support and enhance our open source centralized
log management offering.

Although the SSPL is not OSI approved, it maintains all of the same freedoms the
community has always had with Graylog under AGPL. Users are free to review,
modify, and distribute the software or redistribute modifications to the
software. However, the Open Source Initiative (OSI) has its own process for
approving what it considers to be an open source license, and the SSPL has not
received OSI approval. Graylog software licensed under the SSPL is not
considered open source by the OSI.

In addition, all versions of Graylog released prior to the general availability
of v4.0 will continue to be licensed under GPL v3.0.


HOW DOES THE LICENSE CHANGE THE CURRENT USAGE OF GRAYLOG? ARE THOSE USERS
GRANDFATHERED IN?

All versions of Graylog released on or after the general availability of v4.0
will be licensed under the SSPL. Prior versions of Graylog released before the
general availability of v4.0 will remain under GPLv3; therefore, any use of
those versions is governed by GPLv3.


WHAT ARE THE IMPLICATIONS OF THIS NEW LICENSE ON APPLICATIONS BUILT USING
GRAYLOG AND MADE AVAILABLE AS A SERVICE (SAAS)?

There will be no impact to anyone in the community building an application with
Graylog as a component. The copyleft condition of Section 13 of the SSPL does
not apply to companies building other applications or for internal-only use. It
is limited to those that build and offer publicly a Graylog as a Service
offering. You are not prohibited from doing so, but must also make the source
code of any modifications to Graylog freely available to the public under the
terms of this license


WHAT ARE THE IMPLICATIONS OF THIS NEW LICENSE TO CUSTOMERS AND PARTNERS?

This SSPL will apply to Graylog Open Source. For the vast majority of the
community, there is absolutely no impact from the licensing change. The SSPL
maintains all of the same freedoms the community has always had with Graylog
under GPL – users are free to use, review, modify, distribute the software or
redistribute modifications to the software.

Customers and OEM partners using Graylog under a commercial license will not be
affected by this change.


HOW CAN COMMUNITY MEMBERS CONTRIBUTE TO GRAYLOG REPOSITORIES UNDER THE NEW
LICENSE?

There will be no change to how users contribute to Graylog repositories under
the new license.


WHAT WILL HAPPEN IF SOMEONE IN THE COMMUNITY IS CURRENTLY BUILDING SOMETHING ON
GRAYLOG?

Those currently building something on Graylog are not impacted if they continue
to use a version released prior to the general availability of v4.0, are
building it for internal use only, or are incorporating Graylog as a component
in a larger application. The SSPL license only affects those that are building a
Graylog as a Service public offering and wish to use a version of Graylog
published on or after the general availability of v4.0.


HOW DOES THIS AFFECT CUSTOMERS WHO USE GRAYLOG AS A SERVICE FROM CLOUD PROVIDERS
TODAY?

Graylog will work with existing cloud providers to ensure compliance with the
new license, if applicable, or move to a commercial license. This will not
directly affect customers of those cloud providers.

link to text file of
SSPL https://www.mongodb.com/licensing/server-side-public-license


GRAYLOG INCLUDES 3RD PARTY COMPONENTS THAT ARE ALSO LICENSED UNDER SSPL, HOW
DOES THIS IMPACT GRAYLOG USERS AND CUSTOMERS?

As mentioned above, SSPL is substantively the same as the Free Software
Foundation’s GPL except for Section 13 where it concerns open source products
being offered to the public “as a Service”. In that case, if the Cloud provider
is offering the SSPL product as the primary value of what they are delivering,
then they are required to contribute back to the community by making source code
free and open for all the components necessary to deliver that service.

For Graylog Open users, as long as you are running Graylog or any of its
components for internal use only, you will not trigger the share clause
requiring the publication of source code. If you currently offer, or are
considering offering Graylog Open as a Service, and have questions or concerns,
please contact us to discuss.

Graylog Enterprise customers who utilize third-party components for free
licensed under SSPL are compliant as long as they do not offer direct access to
those components to the public in a Cloud or Hosted environment.

Have questions? Contact us

 

THE GRAYLOG TEAM

The Graylog Experts offering useful tips, tricks, and other important
information whenever they can.
View More Posts By The Graylog Team

Categories

 * API Security
 * Audit & Compliance
 * Detection and Response
 * Graylog Labs
 * ITOPS – DevOPS
 * Log Management & Analytics
 * Release Notices
 * Security Operations & Analytics
 * SIEM
 * Threat Hunting


GET THE MONTHLY TECH BLOG ROUNDUP

Subscribe to the latest in log management, security, and all things Graylog blog
delivered to your inbox once a month.


Read Now


Products

Graylog Security
Graylog Enterprise
Graylog Open
Graylog API Security
Graylog Cloud
Graylog Illuminate
Graylog Small Business
Pricing


FEATURES

Access Control
Anomaly Detection
Audit Logs & Archiving
Data Enrichment
Data Management
Events & Alerts
Fleet Management
Integrations
Investigations
Reports & Dashboards
Risk Management
Scalable Architecture
Search


LEARN

Resource Hub
Blog
Videos
Webinars
Events
Community

SUPPORT

Customer Support
Documentation
Graylog Academy
Open Community


COMPANY

About
Leadership
Partners
Careers
News & Awards
Contact

info@graylog.com

Follow Us:

Facebook-f Linkedin Github Youtube Reddit-alien

GRAYLOG HEADQUARTERS

1301 FANNIN ST, STE. 2000
HOUSTON, TX 77002

GRAYLOG COLORADO

1919 14TH STREET, SUITE 700, OFFICE 18
BOULDER, CO 80302

GRAYLOG UNITED KINGDOM

34-37 LIVERPOOL STREET, 7TH FLOOR
LONDON, EC2M 1PP
UNITED KINGDOM

GRAYLOG GERMANY GMBH

POOLSTRASSE 21
20355 HAMBURG, GERMANY

© 2024 Graylog, Inc. All rights reserved

Privacy Policy | Legal | Sitemap