Choosing a Basker plan

Basker plans and add-ons determine which capabilities are enabled for a site and the allowances attached to them. Packaging can change, so use basker.io/pricing for the live plan names, prices, and inclusion matrix rather than relying on a saved copy.

What to compare

Start with the workflow your organisation needs, then check these areas on the live pricing matrix:

• Team capacity: how many staff accounts the site needs.
• Languages: how many site languages you plan to publish.
• Themes and developer tools: whether you need a custom theme, custom Liquid, or API access.
• Custom data: whether editors need custom attributes or entirely new content types.
• Ticketing and planning integrations: which external systems need to connect and whether an add-on is required.
• Multiple sites: whether one organisation needs several related sites and shared content.
• Storage and usage allowances: media storage, AI credits, and other limits shown for the plan.
• Support and onboarding: the level of implementation and ongoing support your team needs.

Check your site's enabled features

Your site is linked to a plan record that controls feature access and limits. If a guide describes a control that you cannot see, it may be disabled for your plan, unavailable to your role, or dependent on an app or theme.

Check your site's plan information in Basker, then compare it with the live pricing page. Contact sales or support when you need to confirm an add-on or a capability that is not listed clearly.

Before choosing

Write down the non-negotiable parts of your launch:

1. Required staff count and languages.
2. Ticketing, planning, analytics, and asset-library integrations.
3. Custom content fields or content types.
4. Custom-theme and API requirements.
5. Whether content must be shared across several sites.

This list gives sales a concrete specification and helps prevent choosing from headline labels alone.

Where to go next