Documentation

menu
HostingIntroductionBranch HostingPull-request DeploymentsSecretsPersistenceDebuggingMultiple ServersCustom DomainsExample: Typescript & GoExample: JitsiExample: RSS BridgeExample: Tiny Tiny RSSExample: SearxActionsInstalling Nixyaml configNix FlakesWhat Garnix CI doesIncremental BuildsUsing Private InputsCachingEnterprise installationsGitHub Actions IntegrationBadgesGarnModulesNodejsHaskellRustPostgreSQLUseropen source
HostingIntroductionBranch HostingPull-request DeploymentsSecretsPersistenceDebuggingMultiple ServersCustom DomainsExample: Typescript & GoExample: JitsiExample: RSS BridgeExample: Tiny Tiny RSSExample: SearxActionsInstalling Nixyaml configNix FlakesWhat Garnix CI doesIncremental BuildsUsing Private InputsCachingEnterprise installationsGitHub Actions IntegrationBadgesGarnModulesNodejsHaskellRustPostgreSQLUseropen source

garnix can host your NixOS configurations automatically, keeping them always up to date with the latest commits in your git repo. We provision the servers on our own infrastructure, so there is no need to connect garnix to your cloud: hosting is just two or three lines of configuration.

This can be used for two things:

  • Deploying machines from branches for public consumption, e.g. for production or staging environments. These are known as branch deployments.
  • Deploying ephemeral environments from pull-requests, for reviewing and QA. These are known as pull-request deployments.
Blog
Docs
Pricing
Discord
Matrix
Report an issue
Privacy Policy
Imprint