You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/Open_Source_vs_Enterprise.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,10 +10,10 @@ Our business model is based on:
10
10
11
11
All the features and functionality are available on Open Source, and no features are exclusive. Here's how our development cycle looks:
12
12
- Everything new comes to [shuffler.io](shuffler.io) first, and then onprem after thorough onprem scale testing.
13
-
- New features come through `nightly`releases almost nightly, with `latest` being well tested releases.
13
+
- New features come through 'nightly' branch releases almost nightly, with 'latest' branch being well tested releases.
14
14
15
15
**What you get:**
16
-
- You simply get all features and use Shuffle as truly Open Source.
16
+
- You simply get all the features and use Shuffle as truly Open Source.
17
17
- When you scale, is when you pay.
18
18
- Even when you scale and pay, Shuffle will still be cheaper than any other solution on the market.
19
19
- This is possible due to being available in a wider market, and focus on self-service.
@@ -34,7 +34,7 @@ The major differences are below:
34
34
-**Scale License:** As you grow beyond a point (refer to image above), you get an Enterprise license so that your Shuffle instance scales smoothly without any hiccups.
35
35
- This is done so we set the right expectations for scaling, as our inbox is full of people wanting to scale.
36
36
- Scaling with high availability is hard, especially if you are onprem.
37
-
- Hence, we have put a lot of money and resources on R&D for a scalable disteributed[runtime architecture](https://shuffler.io/docs/architecture), which is what you get with an Enterprise License.
37
+
- Hence, we have put a lot of money and resources on R&D for a scalable distributed[runtime architecture](https://shuffler.io/docs/architecture), which is what you get with an Enterprise License.
38
38
-**Support:** Shuffle is a powerful and versatile platform, and it comes with the challenge of too many options and possibilities. When you want our help or want to make the most of Shuffle, you get a support package from Shuffle that covers:
@@ -56,7 +56,7 @@ The simple and fair solution is to enforce the trust:
56
56
57
57
**This helps us:**
58
58
- Keep Shuffle Open Source
59
-
- To pay our great employees
59
+
- To pay our GREAT employees
60
60
- Reinvest in community building
61
61
- Spend resources on R&D
62
62
- Maintain Shuffle's technical superiority in the market
@@ -69,18 +69,16 @@ Let's be frank:
69
69
- Many have hidden blockers, evil business practices, or create their own licenses.
70
70
- We don't do that. We are truly Open Source.
71
71
- We do not hide any feature whatsoever, are built on the AGPLv3 license, and are completely transparent about our business model.
72
-
72
+
73
73
By being lean and open source first, it has even made us able to make interesting models for top contributors to get licenses and support cheaper.
74
74
75
75
This means comparison of Shuffle-to-Others is an Apple-to-Oranges comparison at best.
76
76
77
77
## Shuffle's Commitment
78
78
79
-
* We have no plans to close-source Shuffle.
80
-
81
-
* We went hard on the first iteration of scale licensing, so that we can open up more in the future as we find the right balance between growth and friction.
82
-
83
-
* We aim to build a fair and sustainable future for Shuffle and the Open Source community.
79
+
- We have no plans to close-source Shuffle.
80
+
- We went hard on the first iteration of scale licensing, so that we can open up more in the future as we find the right balance between growth and friction.
81
+
- We aim to build a fair and sustainable future for Shuffle and the Open Source community.
84
82
85
83
As we are in the early phase, we appreciate any and all feedback on the approach at [email protected]
0 commit comments