What Facets doesn't do

What Facets works alongside instead of replacing, and where it stops.

Facets builds and runs the infrastructure your applications need, alongside your cloud, your Kubernetes clusters and your tools.

It doesn't replace your cloud, Kubernetes or Terraform

You keep each of them, and Facets takes over part of the work.

You keepFacets takes over
Cloud accountsYour AWS, GCP or Azure accounts. Resources and bills stay in themCreating and changing resources in them, through releases
KubernetesYour clusters, in your cloud accountCreating clusters for your environments, or connecting ones you have, and deploying your services to them
TerraformYour modules stay Terraform, with a small facets.yaml file that describes their inputs and outputsWriting each project's Terraform from those modules, running plan and apply, and keeping the state
Terraform automation toolsTerraform Enterprise, env0 or Atlantis keep running what you haven't movedRunning the Terraform for what you move to Facets

Where Facets stops

Some work stays with your team or your other tools. Facets doesn't:

  • Hold or roll back your application data. It stays in your cloud account, and a rollback restores settings, not data (Rolling back).
  • Watch for drift all the time. Changes made outside Facets show up when a release runs with Refresh (Drift).
  • Manage what it didn't create, or take over your Terraform state file. You import running resources into Facets' own state instead, one by one (Importing existing infrastructure).
  • Replace your CI. Facets deploys the images your CI builds (CI/CD and container images).
  • Run your failover. DNS cutover, failover tests and runbooks stay with you (Backups and disaster recovery).