Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Plane.so #473

Open
BazlTech opened this issue Apr 24, 2024 · 4 comments
Open

Add Plane.so #473

BazlTech opened this issue Apr 24, 2024 · 4 comments

Comments

@BazlTech
Copy link

What is the vendor's name?
Plane.so

What is the vendor's pricing site?
https://plane.so/pricing

What is the base pricing? Use the lowest tier that looks sane for a small business customer, not free or personal tiers.
$5/usr/yr

What is the minimum pricing for SSO support?
Must call for "Custom pricing"

Does this pricing info come from a quote or other non-public source?
Probably not

Are there any caveats we should list in the footnotes?
Not that I'm aware of.

@theparthacus
Copy link

i am a consultant for Plane, so i can confirm the issue description above is inaccurate.

  1. Google and GitHub SSO are free for everyone.
  2. $5 per user per month is a higher-tier plan than One, which offers custom SSO for self-hosted instances.
  3. One is $699 when pre-ordered and $799 post-launch. It offers in addition to custom SSO features,
    • 100 users
    • Unlimited projects and issues
    • Other plan-specific features
    • SSO pricing as a function of the net price for this plan is way, way below 10%.
  4. When other plans kick in, our SSO pricing as a function of overall pricing of any plan will be well below 10%.

@BazlTech
Copy link
Author

BazlTech commented Apr 26, 2024

i am a consultant for Plane, so i can confirm the issue description above is inaccurate.

1. Google and GitHub SSO are free for everyone.

2. $5 per user per month is a higher-tier plan than [One](https://plane.so/one), which offers custom SSO for self-hosted instances.

3. One is $699 when pre-ordered and $799 post-launch. It offers in addition to custom SSO features,
   
   * 100 users
   * Unlimited projects and issues
   * [Other plan-specific features](https://x.com/planepowers/status/1779886212674998650)
   * SSO pricing as a function of the net price for this plan is way, way below 10%.

4. When other plans kick in, our SSO pricing as a function of overall pricing of any plan will be well below 10%.

So, for anyone NOT wanting to use Google or GitHub Auth, you paywall their ability to use SSO within their own infrastructure.

The fact remains, running your own SSO from within your own environment COSTS THE DEVELOPER NOTHING. This is a very dangerous trend of hiding security features already built in to a product behind a paywall.

@projx
Copy link

projx commented Jul 2, 2024

Perhaps relevant to this, some kind soul did implement SSO for Plane, but it was rejected, Justification and reasoning was etc was documented - see makeplane/plane#3341

so is any further justfication needed?

@theparthacus
Copy link

The fact remains, running your own SSO from within your own environment COSTS THE DEVELOPER NOTHING. This is a very dangerous trend of hiding security features already built in to a product behind a paywall.

barring everything else and speaking generally in the strictest sense of the word, i would like to clarify a couple points very strongly. for context, i come from Cybersec and founded a company whose products were successfully adopted by more than 50% of the Fortune 1,000.

the trend that any SSO or authentication shouldn't be charged and costs the developer nothing, that the developer should be put on a wall of shame for nominal fees is, indeed, dangerous. fact of the matter is like any other feature, security features have their own vision, roadmap, and resource allocation. they cost development time, engineer salaries, and one would argue, more checks and balances than regular day-in-the-life-of features. something breaks with the latter, you are inconvenienced. something breaks with the former, you have a data breach. by your logic, no feature costs anything to run in your own infra. so, why should anyone charge for those either?

the idea that security should be free to offer is as ridiculous as the idea that it should cost an arm and a leg. users and customers have to meet the developer in the middle, pay a nominal fee, a resonable delta for enhanced security, and hold the developer responsible to implement security perimeters and controls that ensure reasonable safety from bad actors. to me, the SSO Wall Of Shame gets it right with the 10% threshold. the call to be put on the Wall Of Shame for that price or lesser is just demanding in several ways the developer ship sub-par product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants