Support Plans
Every SeaweedFS user gets the open-source project, the documentation, and GitHub — free, forever. A support plan adds a private channel, a committed response time, and advisory hours with the engineers who build SeaweedFS.
Support is purchased separately from the capacity license. The license is what covers production use of SeaweedFS Enterprise; the support plan is what puts a name behind your cluster. Production support starts at $2,000/year — small clusters are not priced out of it.
Community
- GitHub issues & discussions
- Public documentation & wiki
- No guaranteed response time
Essential
- Private email support
- 5-business-day response
- 1 advisory hour / month
Small Production
- Private email support
- 3-business-day response
- 2 advisory hours / month
- Annual configuration review
Growth
- Private email support
- 2–3-business-day response
- 4 advisory hours / month
- Upgrade guidance
- Configuration & deployment assistance
Standard
- Email & private Slack support
- 1-business-day response
- 8 advisory hours / month
- Upgrade guidance
- Configuration review
- Architecture & deployment assistance
Critical
- 1-hour response for P1 incidents
- Private Slack, email & Zoom support
- Direct engineering escalation
- Priority troubleshooting & investigation
- Architecture & configuration reviews
- Upgrade planning & guidance
- Up to 12 advisory hours / month
Compare all plans
| Plan | Annual fee | Advisory hours | Response target | Channels & scope |
|---|---|---|---|---|
| Community Any cluster size |
$0 | — | None guaranteed | GitHub issues and discussions, public documentation. No private support. |
| Essential Production Clusters up to 100 TB |
$2,000 | 1 hour / month | 5 business days | Email. One open case at a time. Triage and investigation of product issues. No emergency support, no scheduled meetings. |
| Small Production Clusters up to 250 TB |
$5,000 | 2 hours / month | 3 business days | Email. Troubleshooting, upgrade guidance, and one configuration review per year. |
| Growth Production Clusters up to 1 PB |
$15,000 | 4 hours / month | 2–3 business days | Email. Upgrade guidance, configuration and deployment assistance. |
| Standard Production Multi-petabyte deployments |
$40,000 | 8 hours / month | 1 business day | Private Slack channel and email. Upgrade guidance, configuration review, and architecture and deployment assistance. |
| Critical Production Revenue-bearing workloads |
$85,000 | Up to 12 / month | 1 hour for P1 | Private Slack, email, and Zoom. Direct engineering escalation, priority troubleshooting and investigation, architecture and configuration reviews, upgrade planning. |
| Mission Critical 24/7 production |
Contact sales | 32 hours / month | 24/7 P1 escalation | Phone, Slack, and email. Priority CVE handling, a dedicated escalation path, and regular architecture reviews. |
| OEM / MSP / Reseller You support your own customers |
Custom | Custom | Custom | License provisioning, partner enablement, downstream customer escalation, release coordination, and product integration support. |
Response targets are measured from the time a case is received, during business hours Monday–Friday, excluding public holidays. Mission Critical P1 escalation is available 24/7. Cluster sizes above are guidance for choosing a plan, not a hard cap — talk to us if your shape doesn’t fit.
Ticket support vs. advisory hours
Every paid plan separates two different kinds of help. Knowing which is which is the fastest way to understand what you are buying.
Ticket support — not metered
Private technical support includes reasonable ticket triage and investigation of SeaweedFS product issues. You open a case, we work it within your plan's response target. This does not draw down advisory hours.
Advisory hours — metered
Advisory hours apply to meetings, architecture reviews, configuration reviews, performance tuning, upgrade planning, customer-specific testing, and extended troubleshooting — the work that goes beyond diagnosing a product issue.
How advisory time is counted:
- Time is tracked in 15-minute increments.
- Unused hours expire monthly and do not roll over.
- Work beyond the included hours requires your approval in advance and may be billed separately.
Which plan fits
| If this sounds like you | Start here |
|---|---|
| Evaluating SeaweedFS, or running it below the 25 TB free threshold | Community |
| In production, small cluster, need someone to answer when something is wrong | Essential |
| In production and planning upgrades; want your config sanity-checked once a year | Small Production |
| Approaching a petabyte; want upgrade guidance and hands-on deployment help | Growth Production |
| Multi-petabyte or multi-cluster; want a shared Slack channel and next-business-day answers | Standard Production |
| SeaweedFS carries revenue-bearing traffic and a P1 needs an engineer within the hour | Critical Production |
| An outage is a business event at any hour, and you need a named escalation path | Mission Critical |
| You embed or resell SeaweedFS and support your own customers on top of it | OEM / MSP / Reseller |
Frequently asked
Do I need a support plan to use SeaweedFS Enterprise? No. The capacity license is what production use requires. A support plan is optional and priced separately.
Does a support plan include the license? No. They are billed independently — you can hold a license with Community support, or scale support up without changing your licensed capacity.
What counts as P1? A production outage or data-availability incident with no workaround. P1 response targets apply to Critical Production and Mission Critical plans.
Can I change plans mid-term? Yes. Upgrades take effect immediately and are pro-rated against your current term.
Get started
Tell us your cluster size, what it runs, and how quickly you need answers — we will recommend a plan rather than upsell one.