Why Facets
What changes when your team moves to Facets, results from teams using it, and where it fits best.
Facets removes the infrastructure work every project repeats, so a small platform team can support many teams.
What changes when you move to Facets
No Terraform per project
Your platform team writes modules once. Every project after that is built from them, wiring included.
A platform you don't have to build
Blueprints, ordered releases with approval and rollback, roles and single sign-on come with it.
Developers serve themselves
New environments, databases and deploys without a ticket, within the permissions you set.
Ask for the outcome
Praxis drafts the change for you to review, instead of you working out every step.
Teams already on Terraform, Terraform Enterprise, env0 or Atlantis keep their work: modules become Facets modules, and running resources are imported instead of rebuilt.
Facets customers typically cut DevOps toil by 80%, so the team you have goes further before you need to grow it.
Teams using Facets, and their results
Facets customers ship 8-25x faster, from MPL's 8X deployment frequency to Purplle and GGX at 25x. Here are results from some of them:
Purplle
E-commerce (beauty). Purplle achieved 25x faster go-live for new initiatives.
Capillary Technologies
Retail CRM and loyalty. Capillary Technologies cut ops tickets by 95% with Facets.
Niyo
Fintech, digital banking. 80% of Niyo deployments are fully self-serve; the remaining 20% need only InfoSec approval.
Aster DM Healthcare
Healthcare. Aster ships 21 self-serve releases a day (about 8,000 in 12 months).
Treebo Hotels
Hospitality technology. 80% of Treebo's DevOps time now goes to strategic work instead of firefighting.
GGX
Gaming. GGX increased release velocity 25x, from weekly releases to 5-6 a day.
When Facets is a good fit
Facets is built for platform teams and the developers they support, and you don't need existing Terraform or a platform team to start: it builds environments in your cloud account from ready-made modules. It fits best with:
- Many environments, per region, customer or test cycle
- More than one cloud, or a move between clouds
- Infrastructure still set up by hand
- Several teams, each doing it their own way
- No DevOps team yet