Skip to main content
CI/CD

Reproducible, cache-accelerated CI

Run the exact same Nix in CI that your developers run locally. With FlakeHub Cache, your pipelines pull prebuilt artifacts instead of rebuilding them, and authentication with JSON Web Tokens (JWTs) means there are no static secrets to rotate.

Sign up: FlakeHub Cache

FlakeHub Cache

Share cached binary artifacts across developer machines, CI, and production. Never rebuild what has already been built.
Sign up (opens in a new tab)
Repo: One action to set up Nix

One action to set up Nix

The Determinate Nix Action installs Nix and wires up caching in a single CI step.
Repo (opens in a new tab)
Docs: JWT-based authentication

JWT-based authentication

No static credentials, no rotation schedules. FlakeHub uses JWTs from GitHub, GitLab, Buildkite, Amazon Web Services (AWS), Google Cloud, and others.
Docs (opens in a new tab)

Reproducible pipelines

Same inputs, same outputs, every run. Flaky, environment-dependent builds become a thing of the past.

Checks and builds in one command

Run nix flake check to build and validate your whole project, locally and in CI alike.
Nix for CI/CD: Works with your CI

Works with your CI

Publish flakes and pull from FlakeHub Cache natively on GitHub Actions, Buildkite, Semaphore, and GitLab CI, authenticating with JWTs your provider already issues.
Nix for CI/CD

Natively supported CI platforms

Flake publishing and FlakeHub Cache work out of the box on all of these platforms. Minimal configuration and no static credentials to manage or rotate.

Built on the platform

The products behind your pipelines

Determinate Nix runs your builds on packages vetted by Determinate Secure Packages; FlakeHub caches the results so CI never rebuilds what already exists.

  • FlakeHub Cache

    FlakeHub Cache (opens in a new tab)

    Cache Nix artifacts once and share them across every machine in your pipeline.

  • Determinate Nix Action

    Determinate Nix Action (opens in a new tab)

    Install Determinate Nix and enable caching in your GitHub Actions workflows.

Explore more environments