Skip to content

Rallly is an open-source scheduling and collaboration tool designed to make organizing events and meetings easier.

📝 Keep self-hosting out of the cloud docs

Luke Vella94af9b2162b8
diff --git a/apps/docs/api-reference/introduction.mdx b/apps/docs/api-reference/introduction.mdx
index 3b6495129..09f5d5065 100644
--- a/apps/docs/api-reference/introduction.mdx
+++ b/apps/docs/api-reference/introduction.mdx
@@ -18,8 +18,6 @@ Only the space owner can create API keys, from **Settings → API keys**. See [A
https://api.rallly.co/v1
```
-The API is served by the cloud hosted version only; self-hosted instances do not have it.
-
`v1` is stable. Additive changes such as new endpoints or new optional fields may land at any time; breaking changes only arrive under a new version prefix. The [changelog](/api-reference/changelog) records both.
## Conventions
diff --git a/apps/docs/api-reference/webhooks/guides/n8n.mdx b/apps/docs/api-reference/webhooks/guides/n8n.mdx
index ea994dca3..2e999de3a 100644
--- a/apps/docs/api-reference/webhooks/guides/n8n.mdx
+++ b/apps/docs/api-reference/webhooks/guides/n8n.mdx
@@ -56,7 +56,7 @@ This guide builds a workflow that receives a Rallly event, checks that it really
A request that fails any check stops the workflow with an error, and the node outputs the verified event body as the item. Everything after this node can trust `$json.type` and `$json.data`.
- On self-hosted n8n, `require("crypto")` needs the built-in module allowed: set `NODE_FUNCTION_ALLOW_BUILTIN=crypto` in n8n's environment. n8n Cloud allows it already.
+ If you run n8n on your own server, `require("crypto")` needs the built-in module allowed: set `NODE_FUNCTION_ALLOW_BUILTIN=crypto` in n8n's environment. n8n Cloud allows it already.
</Step>
<Step title="Branch on the event type">
diff --git a/apps/docs/faq.mdx b/apps/docs/faq.mdx
index ba574b1f6..61fc93f1a 100644
--- a/apps/docs/faq.mdx
+++ b/apps/docs/faq.mdx
@@ -28,7 +28,7 @@ description: "Frequently asked questions about Rallly."
Finalize or close a poll to make room for another. There are also technical
limits in place to prevent misuse but these are very generous and should not
- affect normal usage. Self-hosted instances have no open poll limit.
+ affect normal usage.
</Accordion>
<Accordion title="What counts as an open poll?">
diff --git a/apps/docs/self-hosting/introduction.mdx b/apps/docs/self-hosting/introduction.mdx
index 850a0dc11..c400450c5 100644
--- a/apps/docs/self-hosting/introduction.mdx
+++ b/apps/docs/self-hosting/introduction.mdx
@@ -18,6 +18,14 @@ Rallly comes in two flavours built from the same codebase.
Some Cloud features (billing, metered quotas) are compiled out of the self-hosted image. Licensing for multi-user self-hosted instances is covered on the [Licensing page](/self-hosting/licensing).
</Note>
+## Differences from Rallly Cloud
+
+The user guides describe Rallly Cloud. On a self-hosted instance, these work differently:
+
+- **Open polls**: there is no [open poll limit](/faq). Every account can have any number of polls collecting votes at once.
+- **API**: the [Rallly API](/api-reference/introduction) is only served by Rallly Cloud. Self-hosted instances do not have it.
+- **Spaces**: [collaboration](/spaces/collaboration) is always on and the setting is not shown. The instance is already the boundary of your organization, so adding someone to a space is how you work together.
+
## What's included
A self-hosted install is a batteries-included stack. You do not need to provision these services separately.
diff --git a/apps/docs/spaces/collaboration.mdx b/apps/docs/spaces/collaboration.mdx
index 1639a8790..30022b4ab 100644
--- a/apps/docs/spaces/collaboration.mdx
+++ b/apps/docs/spaces/collaboration.mdx
@@ -36,10 +36,6 @@ Turning collaboration on gives members access to everything already in the space
Collaboration is a Pro feature. You can turn it off at any time, but turning it on requires an active Pro subscription.
-<Note>
-On self-hosted instances collaboration is always on and the setting is not shown. The instance is already the boundary of your organization, so adding someone to a space is how you work together.
-</Note>
-
## What it affects
Collaboration controls visibility between members inside the space: polls, events, and anything else created in it.
diff --git a/apps/docs/spaces/introduction.mdx b/apps/docs/spaces/introduction.mdx
index 5609d6828..21dc23735 100644
--- a/apps/docs/spaces/introduction.mdx
+++ b/apps/docs/spaces/introduction.mdx
@@ -10,7 +10,7 @@ Spaces are Rallly's solution for team and organizational collaboration. Instead
<Card title="Key Benefits" icon="rocket">
- **Centralized Billing**: One subscription covers all team members
- - **Optional Collaboration**: Choose whether members work together or keep their scheduling private (on Rallly Cloud; self-hosted spaces always work together)
+ - **Optional Collaboration**: Choose whether members work together or keep their scheduling private
- **Member Management**: Invite and manage team members from one place
- **Seat-Based Pricing**: Pay only for the seats you need and scale as you grow
</Card>