1
- Choosing Between Our Two Sites
2
- ==============================
1
+ Choosing Between Our Two Platforms
2
+ ==================================
3
3
4
- A question our users often have is what the difference is between |org_brand | and |com_brand |.
5
- This page will lay out the functional and philosophical differences between the two sites,
6
- which should help you choose which is a better fit for your organization.
4
+ Users often ask what the differences are between |org_brand | and |com_brand |.
7
5
8
- The features available on both platforms are the same.
9
- The primary difference is the audience and use cases that are supported .
6
+ While many of our features are available on both of these platforms, there
7
+ are some key differences between our two platforms .
10
8
11
9
Read the Docs Community
12
10
-----------------------
13
11
14
- |org_brand | is meant for open source projects to use for documentation hosting.
15
- This is great for user and developer documentation for your project.
12
+ |org_brand | is exclusively for hosting open source documentation. We support
13
+ open source communities by providing free documentation building and hosting
14
+ services, for projects of all sizes.
16
15
17
16
Important points:
18
17
19
- * All documentation sites have advertising
18
+ * Open source project hosting is always free
19
+ * All documentation sites include advertising
20
20
* Only supports public VCS repositories
21
21
* All documentation is publicly accessible to the world
22
22
* Less build time and fewer build resources (memory & CPU)
23
+ * Email support included only for issues with our platform
23
24
* Documentation is organized by projects
24
25
25
26
You can sign up for an account at https://readthedocs.org.
26
27
27
28
Read the Docs for Business
28
29
--------------------------
29
30
30
- |com_brand | is meant for companies and users who have private documentation.
31
- It works well for product documentation as well as internal docs for your developers.
31
+ |com_brand | is meant for companies and users who have more complex requirements
32
+ for their documentation project. This can include commercial projects with
33
+ private source code, projects that can only be viewed with authentication, and
34
+ even large scale projects that are publicly available.
32
35
33
36
Important points:
34
37
35
- * No advertising
38
+ * Hosting plans require a paid subscription plan
39
+ * There is no advertising on documentation sites
36
40
* Allows importing private and public repositories from VCS
37
- * Supports private versions that only your organization or people you give access to can see
41
+ * Supports private versions that require authentication to view
42
+ * Supports team authentication, including SSO with Google, GitHub, GitLab, and Bitbucket
38
43
* More build time and more build resources (memory & CPU)
44
+ * Includes 24x5 email support, with 24x7 SLA support available
39
45
* Documentation is organized by organization, giving more control over permissions
40
46
41
47
You can sign up for an account at https://readthedocs.com.
@@ -44,4 +50,4 @@ Questions?
44
50
----------
45
51
46
52
If you have a question about which platform would be best,
47
- you can email us at
[email protected] .
53
+
0 commit comments