Is Fleet MIT licensed?

We have different licenses for portions of our software which are noted in the LICENSE file in our docs. The majority of Fleet is MIT licensed. Paid features require a license key.

What is your commitment to open source stewardship?

1. When a feature is free and open source we won't move that feature to a paid tier. Features might be removed from the open source codebase in other cases, for example when combining features from multiple tiers into one new feature.
2. The majority of new capabilities added to Fleet will benefit all users, not just customers.
3. We won't introduce features into the open source codebase with a fixed delay; if a feature is planned to land in both it will be released simultaneously in both.
4. We will always release and open source all tests that we have for any open source feature.
5. The free version of Fleet is enterprise ready.
6. The open source codebase will not contain any artificial limits on the number of hosts, users, size, or performance.
7. The majority of new features contributed by Fleet Device Management Inc will be open source.
8. The product will be available for download without leaving an email address or logging in.
9. We will always allow you to benchmark the performance of Fleet.

What if we choose not to renew?

If you opt not to renew Fleet Premium, you can continue using Fleet Free (same code base, just unconfigure the license key.)

Can we buy a licence to access premium features with reduced support for a reduced cost?

We aren’t able to sell licenses and support separately.

Do you offer pricing for ephemeral hosts which may scale up or down?

For now, the number of hosts is the maximum cap of distinct agents enrolled at any given time.

When run locally, what resources does the Fleet app typically consume on an individual instance, and when run in HA, at high volume? And how is latency on an individual instance vs clustered deployment?

Like any modern application, Fleet scales horizontally. The biggest potential bottleneck for Fleet is the number of hosts being monitored, so that's where we've devoted the most attention when testing. The largest number of hosts we've had a customer ask about was 350,000, for all of the production servers and employee laptops of a publicly traded company.

Where's the data stored?

Since Fleet is self-managed, some metadata is stored wherever it is deployed (e.g. Amazon, Azure, Google, your own data center, hybrid cloud, anywhere). That's done using a MySQL database, but the bulk of the data is not stored there — instead, it flows directly into a tool like Splunk or ElasticSearch. You can send that information to any of Fleet's supported log destinations.

Can I fork Fleet's source code and build upon it myself to create my own features?

Anyone is free to fork the project. We are always interested to hear feedback, and we are happy to take pull requests and ideas upstream any time we can.

Can I buy support or services separate from Fleet Premium?

The only way we are able to partner as a business to provide support and build new open source and paid features is through customers purchasing Fleet Premium.