5 ms·

"Self-hosting is only available with the Pulumi Enterprise Edition. Contact us if you would like to evaluate the Self-Hosted Enterprise Edition." [0] [0] https

"Self-hosting is only available with the Pulumi Enterprise Edition. Contact us if you would like to evaluate the Self-Hosted Enterprise Edition." [0] [0] https://www.pulumi.com/docs/guides/self-hosted/ https://www.pulumi.com/docs/guides/self-hosted/

Jgrubb 5y ago
Just curious, why'd you post that bit?
- all2 5y ago
  A big appeal of "open source" is control. Not allowing self-hosting for non-paid tiers is cutting control off from the user and moving it to the producer.
  - xyzzy123 5y ago
    This is just the state storage backend. You can use Pulumi cloud or keep your state in a bucket, or write your own backend. Terraform cloud is a similar deal.
- nine_k 5y ago
  Because it says: «the next major version of the Pulumi open source project». Apparently, either not very complete, or not very open-source, if self-hosting requires a license.
  - jacques_chester 5y ago
    I suspect the key words are "Enterprise Edition". There will be features that matter to larger customers that matter less to others.
spooneybarger 5y ago
You don't need to use the service, although it solves a lot of problems. You can use only the Pulumi SDK and then solve the various state management issues that their service provides in another fashion. I think its a reasonable business model. The SDK is completely open and free. The service is how they make money .
- delnaught 5y ago
  In my quick read, I didn't see a way not to use the service. "If this is your first time running pulumi new or most other pulumi commands, you will be prompted to log in to the Pulumi service. The Pulumi CLI works in tandem with the Pulumi service in order to deliver a reliable experience."[0] [0] https://www.pulumi.com/docs/get-started/kubernetes/create-project/ https://www.pulumi.com/docs/get-started/kubernetes/create-pr...
  - spooneybarger 5y ago
    https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/faq/#can-i-use-pulumi-without-the-pulumicom-service https://www.pulumi.com/docs/intro/cloud-providers/kubernetes...
  - thearrow 5y ago
    I think Pulimi is similar to terraform in that you can use multiple backends for state management, of which their "service" is one[0]. Meaning you could use the CLI backed by an S3 bucket for free. [0]: https://www.pulumi.com/docs/intro/concepts/state/#backends https://www.pulumi.com/docs/intro/concepts/state/#backends
    - marcinzm 5y ago
      Looks like Pulimi, unlike terraform, doesn't provide a means of locking for concurrent access if you use the self-managed state.
      - delnaught 5y ago
        On its way? [0] Not sure how to tell if / when this PR makes it into 3.0 [0] https://github.com/pulumi/pulumi/pull/2697 https://github.com/pulumi/pulumi/pull/2697
        thearrow 5y ago
        Looks like this feature may have made it into v2.23.0, behind an env var: https://github.com/pulumi/pulumi/blob/v2.23.0/CHANGELOG.md#improvements https://github.com/pulumi/pulumi/blob/v2.23.0/CHANGELOG.md#i... Nice!
antoncohen 5y ago
> Open Source SDK > The SDK is a CLI and collection of libraries for defining and deploying cloud apps and infrastructure in code. https://www.pulumi.com/pricing/ https://www.pulumi.com/pricing/ With Terraform the open source CLI and libraries for defining and deploying infrastructure are fully usable, even for large systems. What I would like to know is, how usable Pulumi is without a paid subscription? I thought when I first looked at Pulumi, the only non-local state backend was the paid Pulumi Service. But looking at it now, they seem to support the normal object store backends that Terraform does (https://www.pulumi.com/docs/intro/concepts/state/ https://www.pulumi.com/docs/intro/concepts/state/). Though the talk at lack of concurrency control seems to imply they don't support locking like Terraform does.
- joeduffy 5y ago
  [caveat, Pulumi co-founder here] Pulumi is fully functional in open source form. The analogy I like to draw is Git and GitHub. You can use Git fully independent of GitHub, or you can choose to use them together, for a seamless experience within a team. (Not a perfect analogy since we built both Pulumi open source and the Pulumi SaaS, which causes this very confusion!) We don't hold anything back, if it's in the SDK, it's open. We recently added concurrency control to the alternative backends. I'm sorry the docs are confusing on this matter -- we will get that fixed up. We also have many large customers in production on the open source alone. It's easier with the SaaS just because we handle security, reliability, and sharing with your team along with access controls, auditing, etc. But if you prefer to roll your own there we are entirely happy to have you in the community and help out. Admittedly our marketing materials aren't super clear here and we are working to fix this. Hope this helps to clear things up and again apologies for the confusion.

Jgrubb 5y ago

Just curious, why'd you post that bit?

all2 5y ago
A big appeal of "open source" is control. Not allowing self-hosting for non-paid tiers is cutting control off from the user and moving it to the producer.
- xyzzy123 5y ago
  This is just the state storage backend. You can use Pulumi cloud or keep your state in a bucket, or write your own backend. Terraform cloud is a similar deal.
nine_k 5y ago
Because it says: «the next major version of the Pulumi open source project». Apparently, either not very complete, or not very open-source, if self-hosting requires a license.
- jacques_chester 5y ago
  I suspect the key words are "Enterprise Edition". There will be features that matter to larger customers that matter less to others.

spooneybarger 5y ago

You don't need to use the service, although it solves a lot of problems. You can use only the Pulumi SDK and then solve the various state management issues that their service provides in another fashion. I think its a reasonable business model. The SDK is completely open and free. The service is how they make money .

delnaught 5y ago
In my quick read, I didn't see a way not to use the service. "If this is your first time running pulumi new or most other pulumi commands, you will be prompted to log in to the Pulumi service. The Pulumi CLI works in tandem with the Pulumi service in order to deliver a reliable experience."[0] [0] https://www.pulumi.com/docs/get-started/kubernetes/create-project/ https://www.pulumi.com/docs/get-started/kubernetes/create-pr...
- spooneybarger 5y ago
  https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/faq/#can-i-use-pulumi-without-the-pulumicom-service https://www.pulumi.com/docs/intro/cloud-providers/kubernetes...
- thearrow 5y ago
  I think Pulimi is similar to terraform in that you can use multiple backends for state management, of which their "service" is one[0]. Meaning you could use the CLI backed by an S3 bucket for free. [0]: https://www.pulumi.com/docs/intro/concepts/state/#backends https://www.pulumi.com/docs/intro/concepts/state/#backends
  - marcinzm 5y ago
    Looks like Pulimi, unlike terraform, doesn't provide a means of locking for concurrent access if you use the self-managed state.
    - delnaught 5y ago
      On its way? [0] Not sure how to tell if / when this PR makes it into 3.0 [0] https://github.com/pulumi/pulumi/pull/2697 https://github.com/pulumi/pulumi/pull/2697
      - thearrow 5y ago
        Looks like this feature may have made it into v2.23.0, behind an env var: https://github.com/pulumi/pulumi/blob/v2.23.0/CHANGELOG.md#improvements https://github.com/pulumi/pulumi/blob/v2.23.0/CHANGELOG.md#i... Nice!

antoncohen 5y ago

> Open Source SDK > The SDK is a CLI and collection of libraries for defining and deploying cloud apps and infrastructure in code. https://www.pulumi.com/pricing/ https://www.pulumi.com/pricing/ With Terraform the open source CLI and libraries for defining and deploying infrastructure are fully usable, even for large systems. What I would like to know is, how usable Pulumi is without a paid subscription? I thought when I first looked at Pulumi, the only non-local state backend was the paid Pulumi Service. But looking at it now, they seem to support the normal object store backends that Terraform does (https://www.pulumi.com/docs/intro/concepts/state/ https://www.pulumi.com/docs/intro/concepts/state/). Though the talk at lack of concurrency control seems to imply they don't support locking like Terraform does.

joeduffy 5y ago
[caveat, Pulumi co-founder here] Pulumi is fully functional in open source form. The analogy I like to draw is Git and GitHub. You can use Git fully independent of GitHub, or you can choose to use them together, for a seamless experience within a team. (Not a perfect analogy since we built both Pulumi open source and the Pulumi SaaS, which causes this very confusion!) We don't hold anything back, if it's in the SDK, it's open. We recently added concurrency control to the alternative backends. I'm sorry the docs are confusing on this matter -- we will get that fixed up. We also have many large customers in production on the open source alone. It's easier with the SaaS just because we handle security, reliability, and sharing with your team along with access controls, auditing, etc. But if you prefer to roll your own there we are entirely happy to have you in the community and help out. Admittedly our marketing materials aren't super clear here and we are working to fix this. Hope this helps to clear things up and again apologies for the confusion.