Pulumi ESC FAQs
Why did Pulumi launch ESC?
We launched Pulumi ESC in response to customer feedback about their difficulties in managing config and secrets, causing sprawl and duplications across stacks. Pulumi ESC brings the same Pulumi IaC-like software engineering approach to secrets and configuration, allowing hierarchical configurations that eliminate copy/paste. It can be used for all applications and infrastructure - with or without Pulumi IaC.
What is the pricing of Pulumi ESC?
See our pricing page for details.
What counts as a secret towards pricing?
Secrets include static secrets, dynamic login credentials and dynamic secrets.
In other words, when using Pulumi ESC’s document editor, each definition of fn::secret
and fn::open::*
(except with the pulumi-stacks provider) is counted as a secret.
Only the secrets from the latest environment revision are counted towards your bill.
What is the roadmap for Pulumi ESC?
Check out our public roadmap page.
If you are interested in a particular feature, we encourage you to create a feature request or upvote an existing request.
Can I self-host Pulumi ESC?
Yes. Contact sales for a demo or trial of self-hosted Pulumi ESC.
More FAQ
Thank you for your feedback!
If you have a question about how to use Pulumi, reach out in Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.