Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pricing page redesign #878

Merged
merged 5 commits into from
Jan 17, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion blog/_includes/nav/header.html
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
<div class="border-b ml-7 pl-[18px] mr-8 hover:bg-[#f1fbff]"><a href="https://cloud.earthly.dev/login" class="py-3 flex items-center text-sm xl:text-base">Login</a></div>
<div class="border-b ml-7 pl-[18px] mr-8 hover:bg-[#f1fbff]"><a href="https://docs.earthly.dev" class="py-3 flex items-center text-sm xl:text-base">Earthfile Docs</a></div>
<div class="border-b ml-7 pl-[18px] mr-8 hover:bg-[#f1fbff]"><a href="/earthly-satellites" class="py-3 flex items-center text-sm xl:text-base">Earthly Satellites</a></div>
<div class="ml-7 pl-[18px] mr-8 hover:bg-[#f1fbff]"><a href="/pricing" class="py-3 flex items-center text-sm xl:text-base">Satellites Pricing</a></div>
<div class="ml-7 pl-[18px] mr-8 hover:bg-[#f1fbff]"><a href="/earthfile/satellites/pricing" class="py-3 flex items-center text-sm xl:text-base">Satellites Pricing</a></div>
</div>
</div>
</div>
Expand Down
2 changes: 1 addition & 1 deletion blog/_includes/nav/mobile-menu.html
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@
<a href="https://cloud.earthly.dev/login" class="border-b ml-4 pl-4 py-4 flex items-center hover:bg-[#f1fbff]">Login</a>
<a href="https://docs.earthly.dev" class="border-b ml-4 pl-4 py-4 flex items-center hover:bg-[#f1fbff]">Earthfile Docs</a>
<a href="/earthly-satellites" class="border-b ml-4 pl-4 py-4 flex items-center hover:bg-[#f1fbff]">Earthly Satellites</a>
<a href="/pricing" class="ml-4 pl-4 py-4 flex items-center hover:bg-[#f1fbff]">Satellites Pricing</a>
<a href="/earthfile/satellites/pricing" class="ml-4 pl-4 py-4 flex items-center hover:bg-[#f1fbff]">Satellites Pricing</a>
</div>

<a href="{{site.blogurl}}" class="border-b w-full pl-2 text-xl py-4 flex items-center hover:bg-[#f1fbff]">
Expand Down
2 changes: 1 addition & 1 deletion blog/_posts/2023-07-14-build-transpose.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,6 @@ As a newcomer to working with large language models, I found the experience of b

These techniques were invaluable in helping me understand how to apply LLMs to [real-world problems](https://github.com/earthly/build-transpose/). The potential of these technologies, combined with thoughtful instructional approaches to overcome their limitations, is fantastic.

If you're building things with LLMs, I'd love to hear about any tricks you've learned. Also, if you are using GitHub actions, you should [give Earthly a try](https://earthly.dev/earthly-github-actions). Earthly can improve the consistency of your build, so you never get a build failure you can't reproduce locally. It works great with GitHub actions. And want your GitHub Actions to be even faster? [Our satellites can make that happen](https://earthly.dev/pricing).
If you're building things with LLMs, I'd love to hear about any tricks you've learned. Also, if you are using GitHub actions, you should [give Earthly a try](https://earthly.dev/earthly-github-actions). Earthly can improve the consistency of your build, so you never get a build failure you can't reproduce locally. It works great with GitHub actions. And want your GitHub Actions to be even faster? [Our satellites can make that happen](https://earthly.dev/earthfile/satellites/pricing).

{% include_html cta/bottom-cta.html %}
2 changes: 1 addition & 1 deletion blog/_posts/2023-10-19-the-roi-of-fast.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ There is, however, an upfront cost of integrating Earthly into your existing set

At Earthly, we believe that billing CI/CD by the build minute is fundamentally broken, because the slower the build gets, the more the vendor profits. It creates misaligned incentives. CI/CD tooling should be aligned to developer productivity (not to the opposite of it!).

For this reason, our pricing model uses the number of active users for the profit-generating component of our pricing, and charges a zero-margin fee on compute. Plus, because we don't want our customers to even think about build minutes, our plans come with a very [generous amount of included build minutes that scale with the team size](https://earthly.dev/pricing) - something very unique in the realm of CI/CD tooling.
For this reason, our pricing model uses the number of active users for the profit-generating component of our pricing, and charges a zero-margin fee on compute. Plus, because we don't want our customers to even think about build minutes, our plans come with a very [generous amount of included build minutes that scale with the team size](https://earthly.dev/earthfile/satellites/pricing) - something very unique in the realm of CI/CD tooling.

In our running example, we showed how a 2.5X build speed improvement can save you $23k in CI infrastructure, and $300k in developer time (conservative estimate) in a team of 30 people. For this setup, Earthly Cloud costs $19.7k per year. So in this case, you're covering the cost of Earthly without even asking for more budget (you just shift from existing CI infrastructure) - yet the benefits are 16X greater than that.

Expand Down
2 changes: 1 addition & 1 deletion blog/_posts/2024-01-23-earthly-v0-8.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ Outputting images from a remote runner, such as Earthly Satellites, has improved

## New Earthly Satellites Instance Sizes

In response to growing scalability needs, we're introducing larger Earthly Satellites instance sizes. We previously offered x-small, small, medium, large, and x-large instances. We are now adding 2x-large, 3x-large, and 4x-large instances. These new options offer more powerful resources for your builds. You can find more details about compute sizing and pricing on our [Pricing page](https://earthly.dev/pricing).
In response to growing scalability needs, we're introducing larger Earthly Satellites instance sizes. We previously offered x-small, small, medium, large, and x-large instances. We are now adding 2x-large, 3x-large, and 4x-large instances. These new options offer more powerful resources for your builds. You can find more details about compute sizing and pricing on our [Pricing page](https://earthly.dev/earthfile/satellites/pricing).

## Renaming COMMAND to FUNCTION

Expand Down
2 changes: 1 addition & 1 deletion blog/_posts/2024-02-13-larger-satellite-sizes.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ At Earthly, we're constantly trying to make builds more consistent, faster, and
- **3xlarge:** 32 vCPUs, 128 GB of RAM, and a 1TB cache disk. x86 & arm64 available.
- **4xlarge:** 64 vCPUs, 256 GB of RAM, and a 2TB cache disk. x86 & arm64 available.

_[Visit our Pricing page](https://earthly.dev/pricing#compute-pricing) for more details about the Satellites instance sizes we offer._
_[Visit our Pricing page](https://earthly.dev/earthfile/satellites/pricing) for more details about the Satellites instance sizes we offer._

## From Feedback to Features

Expand Down
2 changes: 1 addition & 1 deletion blog/_posts/2024-02-27-self-hosted-satellites.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,6 @@ _For the complete guide, visit [the Self-Hosted Satellites page in our documenta

![today]({{site.images}}{{page.slug}}/today.png)\

[Sign up for Earthly Cloud](https://cloud.earthly.dev/login) to start self-hosting your own Earthly Satellites. They are even available on our free tier, so you can start with self-hosted Satellites now at no cost ([visit our Pricing page](https://earthly.dev/pricing#compute-pricing) for more details about pricing for self-hosted Satellites). Try out self-hosted Earthly Satellites, and let us know how they work for you.
[Sign up for Earthly Cloud](https://cloud.earthly.dev/login) to start self-hosting your own Earthly Satellites. They are even available on our free tier, so you can start with self-hosted Satellites now at no cost ([visit our Pricing page](https://earthly.dev/earthfile/satellites/pricing) for more details about pricing for self-hosted Satellites). Try out self-hosted Earthly Satellites, and let us know how they work for you.

{% include_html cta/bottom-cta.html %}
17 changes: 17 additions & 0 deletions website/_data/byoc-enterprise-features.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
- points:
- point: Unlimited users
- point: Fully-managed, single-tenant satellite fleet
- point: Auto-sleep cost-saving features
- point: x86 and arm64
- points:
- point: xsmall to 3xlarge size instances
- point: Custom satellite specs
- point: Managed TLS with automatic key rotation
- point: <a class="underline" href="https://docs.earthly.dev/earthly-cloud/satellites/gha-runners" target="_blank">Integrated Github Actions runner</a>
- points:
- point: Unlimited log retention
- point: Third-Party Secrets Integration
comingSoon: true
- point: Export build analytics
comingSoon: true
- point: 24/7 support and a dedicated Slack channel
28 changes: 13 additions & 15 deletions website/_data/pricing-faqs.yml
Original file line number Diff line number Diff line change
@@ -1,16 +1,14 @@
- question: How are users tracked?
answer: The number of users is tracked by monitoring who triggered a Satellite build at least three times during a month. Builds may be triggered either directly by the user in their terminal, or indirectly by pushing code to a repository, and that push being picked up by a CI that uses Earthly Satellites to perform the build. In the latter case, the triggering user is inferred via commit metadata. The triggering user does not have to be a user registered with Earthly. In some cases, if the triggering user cannot be inferred from commit metadata, then the user logged into Earthly CLI in the CI run is used as the triggering user. At the end of a billing cycle, if the number of paid users is greater than the number of actual users, the difference is refunded to the customer in the form of a statement credit. If you would like to estimate the number of users that a project has according to how we track users, please check out the <a class="underline" href="https://github.com/earthly/lib/tree/main/billing#active-users">github.com/earthly/lib/billing+active-users</a> target.
- question: What is zero-margin compute?
answer: Zero-margin compute is a pricing model where the cost of compute is passed on directly to the user, without any profit-generating margin. This allows us, the vendor, to better align our incentives with the end user. Slow builds should not mean more profit for us.
- question: How much does compute cost
answer: The cost of compute is based on the AWS rack price for the instances that are used underneath, plus the cost of cache storage and the cost of network ingress/egress incurred. All of these costs are packaged as an all-inclusive per-minute cost and is then passed on directly to the user, without any profit-generating margin.
- question: What is a standard Earthly build minute?
answer: A standard Earthly Build Minute is defined as one (1) minute of build execution on an xsmall x86 or arm64 instance. The multiplier is 2x, 4x, 8x, and 16x for small, medium, large, and xlarge instances respectively – e.g. one (1) minute of build execution on a medium instance is equal to four (4) Earthly Build Minutes.
- question: What are Satellites?
answer: "Satellites are single-tenant remote build runners managed by the Earthly team. Satellites are used as remote executors in development workflows and with other CI tools. Common use cases for using Satellites include:<ul><li>Using satellites on top of a traditional CI, in order to take advantage of the Earthly caching and parallelization capabilities.</li><li>Using satellites in local development workflows in order to share compute and cache with colleagues.</li><li>Using satellites in order to execute x86 builds on ARM (or Apple Silicon) machines, or vice-versa.</li></ul>"
- question: How is my usage of Satellites tracked?
answer: The usage of Satellites is tracked by monitoring each satellite for active builds. If there are no active builds, the satellite goes to sleep automatically. When a satellite is asleep, it is not billed for compute. When a build is started, the satellite is woken up automatically, and billing for compute resumes.
- question: How many satellites do I need?
answer: The number of satellites you need depends on the workload they need to handle. For maximum performance, you can create a different satellite for each CI pipeline. This may be overkill for some setups though, where CI pipelines are small. The best method to determine the number of satellites you need is to start with one or two and add more as needed. Earthly prints information on build startup about how loaded the Satellite is currently. This can be used as a guide to determine if more Satellites are needed.
- question: Can I use the Pro or Team tiers if I have a small team?
answer: Yes, you can use the Pro and Team tiers for teams of any size.
answer: "Satellites are remote build runners that speed up builds with Earthly’s caching and parallelization. Available via BYOC or Self-Hosted, they integrate with CI systems and local workflows to:<ul><li>Enhance CI with caching and parallelism.</li><li>Share compute and cache across the team.</li><li>Enable cross-platform builds (e.g., x86 on ARM).</li></ul>"
- question: What is BYOC?
answer: BYOC stands for “Bring Your Own Cloud,” a service model that combines the benefits of on-premises deployment with the convenience of vendor management for a cloud-like experience. With our BYOC plan, you provide Earthly with access to your AWS account using a strict IAM role that you own.
- question: Is BYOC as secure as Self-Hosted?
answer: The IAM role you grant us allows Earthly to create and manage EC2 instances within a specific VPC. However, this role does not grant Earthly connection access to the instances themselves or to their internal cache data. For more details, refer to our <a class="underline" href="https://docs.earthly.dev/earthly-cloud/satellites/byoc" target="_blank">BYOC documentation</a>. That said, organizations with strict compliance requirements may prefer the Self-Hosted option, which ensures that satellites are fully controlled by your team alone.
- question: How are users tracked?
answer: The number of users is tracked by monitoring who triggered a Satellite build at least three times during a month. Builds may be triggered either directly by the user in their terminal, or indirectly by pushing code to a repository, and that push being picked up by a CI that uses Earthly Satellites to perform the build. In the latter case, the triggering user is inferred via commit metadata. The triggering user does not have to be a user registered with Earthly. In some cases, if the triggering user cannot be inferred from commit metadata, then the user logged into Earthly CLI in the CI run is used as the triggering user. If you would like to estimate the number of users that a project has according to how we track users, please check out the github.com/earthly/lib/billing+active-users target.
- question: How does the Auto-Sleep feature save costs?
answer: In the BYOC plan, Satellites will automatically enter a sleep state when they have been inactive for at least 30 minutes. This state is shown in the Earthly CLI when you list or connect to your satellites. If a build is started while a Satellite is in a sleep state, the Earthly backend will automatically wake the instance back up before allowing the build to start. Note that this feature is unavailable in the Self-Hosted plans.
- question: How many Satellites do I need?
answer: The number of satellites you need depends on the workload they need to handle. For maximum performance, you can create a different satellite for each CI pipeline. This may be overkill for some setups though, where CI pipelines are small. The best method to determine the number of satellites you need is to start with one or two and add more as needed. Earthly prints information on build startup about how loaded the Satellite is currently. This can be used as a guide to determine if more Satellites are needed. You can read more about tuning your satellites in our <a class="underline" href="https://docs.earthly.dev/earthly-cloud/satellites/best-practices" target="_blank">best-practices guide</a>.
- question: How do I deploy a Self-Hosted Satellite?
answer: Self-Hosted satellites are deployed using our <a class="underline" href="https://hub.docker.com/r/earthly/satellite" target="_blank">official Docker image</a>. You can run this image as a container in your own infrastructure, such as on a dedicated VM or as a Pod in a Kubernetes cluster. See our <a class="underline" href="https://docs.earthly.dev/earthly-cloud/satellites/self-hosted" target="_blank">Self-Hosted Satellites documentation</a> for more details.
24 changes: 12 additions & 12 deletions website/_data/pricing-features.yml
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
- title: No profit from slow builds
description: We charge zero-margin on compute. Compute costs are passed directly to the customer. That means we invest heavily in making your builds faster, because that makes users happy.
image: assets/svg/percentage.svg
- title: More effective build minutes
description: Earthly Cloud's automatic caching and parallelism makes builds 2-20X faster than on traditional CI/CD platforms. You don’t need as many build minutes for the same work.
image: assets/svg/clock-fast.svg
- title: Build minutes for everyone
description: Unlike other vendors, our included minutes scale with team size. They are designed to handle most workloads so customers don’t even have to think about additional build minutes.
image: assets/svg/community.svg
- title: Productivity is our value-add
description: Earthly Cloud's value-add is developer productivity. In a team of 30, a 2.8X speed boost to CI/CD means 2 FTEs worth of time saved.
image: assets/svg/fastapi.svg
- title: Ship Code<br />Faster
description: Leverage automatic caching and parallelism to accelerate builds by 2-20x compared to traditional CI/CD platforms.
image: /assets/svg/shipping-fast.svg
- title: Effortless<br />Configuration
description: Earthly Satellites automatically cache every step in your Earthfile—no need for custom configurations, special build tooling, or costly cache downloads from container registries.
image: /assets/svg/effortless-config.svg
- title: Secure,<br />In Your Environment
description: Choose Self-Hosted or BYOC (Bring Your Own Cloud) plans to ensure your builds remain secure, with all data staying within your infrastructure.
image: /assets/svg/secure.svg
- title: Maximize<br />Productivity
description: Earthly Satellites focus on developer efficiency. For a 30-person team, a 2.8x speed boost in CI/CD delivers productivity gains equivalent to adding two full-time engineers—without the overhead.
image: /assets/svg/graph-bar-increase.svg
8 changes: 8 additions & 0 deletions website/_data/self-hosted-enterprise-features.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
- point: Unlimited users
- point: Managed TLS with automatic key rotation
- point: Unlimited log retention
- point: Third-Party Secrets Integrations
comingSoon: true
- point: Export build analytics
comingSoon: true
- point: 24/7 support and a dedicated Slack channel
7 changes: 7 additions & 0 deletions website/_data/self-hosted-free-features.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
- point: Up to 5 users
- point: <a class="underline" href="/earthfile/satellites">Satellites</a>
- point: x86 and arm64
- point: Managed TLS
- point: Log Sharing
- point: <a class="underline" href="https://docs.earthly.dev/earthly-cloud/cloud-secrets" target="_blank">Earthly Cloud Secrets</a>
- point: <a class="underline" href="https://docs.earthly.dev/earthly-cloud/satellites/gha-runners" target="_blank">Integrated Github Actions runner</a>
7 changes: 0 additions & 7 deletions website/_data/tier-1-pricing-cloud.yml

This file was deleted.

5 changes: 0 additions & 5 deletions website/_data/tier-1-pricing-self-hosted.yml

This file was deleted.

2 changes: 0 additions & 2 deletions website/_data/tier-2-pricing.yml

This file was deleted.

5 changes: 0 additions & 5 deletions website/_data/tier-3-pricing-cloud.yml

This file was deleted.

3 changes: 0 additions & 3 deletions website/_data/tier-3-pricing-self-hosted.yml

This file was deleted.

3 changes: 0 additions & 3 deletions website/_data/tier-4-pricing-cloud.yml

This file was deleted.

4 changes: 0 additions & 4 deletions website/_data/tier-4-pricing-self-hosted.yml

This file was deleted.

Loading
Loading