Beta and experimental features

Beta and Experimental Sourcegraph features give you an opportunity to try newer features and shape their development, before they become generally available.

Your feedback helps us make sure that our new features are reliable and useful, and we appreciate any and all feedback you want to provide. You can email us directly to [email protected].

For both features labeled Beta or Experimental, Sourcegraph wants to be transparent that:

  • The feature is undergoing active development and your feedback is especially appreciated
  • The feature may have bugs, and is excluded from our support SLAs
  • The feature may change, be deprecated, be removed, or be disabled at any time
  • The feature may have temporary usage limits during the beta and experimental period.
  • The feature may require admin enablement or other intentional setup
  • The feature may become billable with credits once they become generally available

Feature lifecycle

Features generally move through the following stages:

StageLabelCredit impact
ExperimentalExperimentalNo credits consumed
BetaBetaNo credits consumed
General availabilityNo special labelCredits may apply according to the published rate card

Experimental features

If a feature is labeled Experimental, this specifically means:

  • The feature is intended for early evaluation and will generally require deliberate enablement
  • There may be no fixed timeline for moving the feature to Beta or general availability
  • Some Experimental features may have credit costs associated with them when they exit Beta into general availability; see credits and billing
  • Admins can disable Experimental features globally

General points about both beta and experimental features also apply.

Beta features

If a feature is labeled Beta, this specifically means:

  • The feature may be widely available to all customers by default
  • There may be no fixed timeline for moving the feature to general availability
  • Some Beta features may have credit costs associated with them when they graduate to general availability; see credits and billing
  • Admins can disable Beta features globally

General points about both beta and experimental features also apply.

Credits and billing

Billing depends on the feature.

  • Experimental and Beta features do not consume credits
  • Some Beta or Experimental features, when they graduate to general availability, may be billable with credits.
    • Such features will have a Beta stage with messaging that identifies, if applicable, the upcoming credit cost and start date. Sourcegraph will provide at least 30 days notice before credits consumption begins.
  • Admins can configure limits on the use of credit-consuming features

To learn more about credits and billing, please reach out to your account manager or [email protected].

Previous
Changelog