Your slipway org runs on a plan. The plan controls default resource limits for every deployment, retention windows, how many concurrent builds you can run, and which features are available to your team.Documentation Index
Fetch the complete documentation index at: https://docs.slipway.sh/llms.txt
Use this file to discover all available pages before exploring further.
Plan tiers and pricing are evolving. The numbers below are placeholders — for current pricing, see the pricing page on slipway.sh or open Settings → Billing in your org.
You must pick a plan to deploy
When you first install the GitHub App, your slipway org lands on the plan picker. Until you pick a plan, the org is in read-only mode: you can browse repos, view past deployments, and read settings, butDeploy now and webhook-triggered builds will return a “no plan assigned” error.
Paid plans include a 14-day free trial configured at the Stripe price level. Picking a paid plan takes you through Stripe Checkout, after which your org’s subscription status reads trialing for the trial window — deployments are unlocked immediately. No card is charged until the trial ends.
If you add a second GitHub account (Sidebar → Add an organization) and don’t want to commit to a plan yet, use Maybe later on the plan picker to return to your existing org. The new org persists in your sidebar and shows a paywall banner until you pick a plan for it.
What changes between plans
The dimensions below mirror the rows you’ll see on the Settings → Billing page. Numbers are placeholders.| Dimension | Free | Team | Business | Enterprise |
|---|---|---|---|---|
| Members | TBD | TBD | TBD | Custom |
| Repositories | TBD | TBD | TBD | Unlimited |
| Concurrent deployments | 1 | TBD | TBD | Custom |
| Pod CPU (per container) | 250m | TBD | TBD | Custom |
| Pod memory (per container) | 256 MiB | TBD | TBD | Custom |
| Log retention | TBD days | TBD days | TBD days | Custom |
| Custom domains | — | TBD | TBD | Unlimited |
| Preview auth methods | Shared token | All methods | All methods | All methods |
| Convoys (multi-repo environments) | — | TBD | TBD | TBD |
| Database addons | — | TBD | TBD | TBD |
| Object storage | — | TBD | TBD | TBD |
| API keys | — | TBD | TBD | TBD |
| SSO | — | — | — | yes |
| Support | Community | Priority | Dedicated |
Where you’ll feel your plan
A few places in the product surface plan-derived numbers directly:- Sidebar usage tile. Your current plan and one headline usage number (typically “deployments this month”) are pinned at the bottom of the left rail on every page.
- Settings → Billing. Full plan details, your current usage against each limit, and the upgrade/downgrade controls.
- Settings → Usage. Detailed breakdowns by repo, deployment, and component over the last 30 days.
- Deployment detail. If a build or deploy fails because it tried to ask for more CPU, memory, or disk than your plan allows, the failure event spells out the cap that was exceeded.
Changing plans
Open Settings → Billing. Upgrades take effect immediately and you’re prorated for the rest of the billing period. Downgrades take effect at the end of the current period — if your usage on the lower plan would exceed its limits at that point, slipway warns you in the billing UI so you can decide what to remove first.
Related
- Members & roles — who in your org can change the plan
- Limits & defaults — the platform-wide numbers that don’t depend on plan