#Dagger Cloud free plan?

1 messages · Page 1 of 1 (latest)

wicked prism
#

We're still fine-tuning pricing, so note that everything I say here can still change.

  • At the moment we're not planning a free plan. Since there is infrastructure involved, those can be tricky to get right in a way that limits abuse and support costs.

  • We are planning a very cheap entry plan, $5/month or less, specifically for power users in the community

  • We will probably have a program to give special deals to open-source projects, students etc. But those are tricky to get right also. For example some open source projects are part of well funded corporations with serious business needs. It doesn't make sense for them to not pay. Etc.

We welcome all thoughts and feedback 🙂

sinful isle
#

If the only tier with SSO is enterprise you're going to kill any desire I have to use Dagger Cloud as a team tool... Too many SaaS development products that don't offer SSO until enterprise tiers 🙁

#

Glad to hear there's a low-cost single-user plan though!

wicked prism
#

fyi @shy juniper @last bough @lyric thorn

sinful isle
#

Yeah, that's a 'consider the small teams' angle. Getting an enterprise license approved at 3x+ the 'pro' tier is just hard work, especially when most of the enterprise features otherwise aren't useful. No idea how easy it is to flexibly offer features but if it is possible it solves a problem I hit recently: Gitlab stick compliance framework pipelines behind enterprise tier at 3x the cost, but that would be immensely useful... And there's zero chance of selling more than 3x the Gitlab cost for it

wicked prism
#

@sinful isle you’re thinking of SSO in the context of a saas version, correct? Not specifically an onprem version?

sinful isle
#

Yep

shy juniper
#

@sinful isle - is that SSO using your company's identity provider or a third-party's like Auth0?

sinful isle
#

Third party typically, last two I've used at client engagements were Okta and that's been seamless and simple

opal jasper
#

Keycloak integration would be nice too

#

it would be nice to have IAM on who can submit requests to the engine, cloud or self-hosted

#

for example, I'd like Dagger to use permissions tied to a service account (so it has limited access to cloud resources), but allow certain users / triggers to start pipelines