Simple pricing that works at any scale
Developer
Get started with easy-to-use feature flags.
$0
Up to 10 seats
Developer includes:
- Client and server side feature flags
- Slack, Jira Cloud, Azure DevOps integrations and more
- Rich API
- Up to 50,000 monthly tracked keys
Team
Manage your release process with security and governance.
$33
per seat
per month
Everything in Developer, PLUS:
- Rollout dashboard
- SSO / SAML authentication
- Role-based access controls
- Self-guided learning program via Split Arcade
Business
Move faster with data-driven decisions.
$60
per seat
per month
Everything in Team, PLUS:
- Dynamic configurations
- Data import and export integrations
- Monitor and experiment add on available
- Customer success manager
Enterprise
Scale to the unique needs of a global enterprise.
Custom
Unlimited seats
Everything in Business, PLUS:
- Workspace and API restrictions
- Change management via approval workflows
- SCIM support
Compare Plans
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| Access to all SDKs | Support for multiple SDKs for both client-side and server-side languages. | x | x | x | x |
| Access to polling & streaming delivery | Streaming enables updates to be sent to the SDK in milliseconds. Polling sends updates to the SDK using configurable intervals. | x | x | x | x |
| Workspaces | Allows scaling customers to manage feature flags and experiments separately across your different teams and products. | 1 | 1 | Unlimited | Unlimited |
| Environments | Set-up different environments (staging, production, etc.) to manage the various stages of the development lifecycle. Targeting rules and permissions for changing them can be different between environments. | 2 | Unlimited | Unlimited | Unlimited |
| Traffic types | Different types of unique keys (i.e. user, device, account or other key) upon which flag decisions can be made. | 2 | 2 | Unlimited | Unlimited |
| Feature flags | A software development tool used to safely activate or deactivate features for testing in production, gradual release, experimentation, and operations. | Unlimited | Unlimited | Unlimited | Unlimited |
| Treatments per feature flag | Treatments are variations of a feature. Most basic case is “on” and “off”. | 2 | 2 | Unlimited | Unlimited |
| Access to admin API | Can be used to push data in and out of Split, build custom integrations, or build on top of the Split platform. | x | x | x | x |
| Data export | Query and export all impression and event data. | x | x | ||
| Standard MTKs | Monthly Tracked Keys (“traffic keys”) correspond to a unique user, device, account or other key upon which feature flag decisions are based. | 50,000 | 50,000 | 50,000 | 50,000 |
| Additional MTKs | Support for additional Monthly Tracked Keys (“traffic keys”) that surpass the 50,000 limit. | Not available | Not available | Custom | Custom |
| Experimentation & monitoring events | Event data from your application (i.e. clicks, page load time, etc) that has been received through the Split SDK track calls, events API calls, or inbound integrations. | Not available | Not available | Custom | Custom |
Target Your Users
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| Target individually | Use to target a particular user. Overrides other targeting rules to ensure user receives the specified treatment. | x | x | x | x |
| Target by custom attribute | Use to target based on any attribute your application has available to pass to the Split SDK at runtime. | x | x | x | x |
| Reusable segments | A segment is a named list of keys (user ids, employee ids, account ids). You create and manage these in Split and use for additional targeting options. | 10,000 key limit | 10,000 key limit | 100,000 key limit | 100,000 key limit |
| Flag traffic allocation | Use to increase or decrease the amount of traffic that is evaluated against the targeting and default rules without moving customers across treatments. | x | x | ||
| Dependent flags | Use Split’s dependency matcher when you want one feature flag to depend on the evaluation of another feature flag. | x | x |
Manage Your Flags
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| Live tail (debugger) | View impressions and events in real-time. Use query criteria to filter which impressions or events are shown. Drill into entries to see raw JSON payload with full detail. Useful for debugging/validating data flow from your application and 3rd party integrations with Split. | x | x | x | x |
| Rollout board (flag dashboard) | For managing feature flags at scale. Teams can visualize the status of different features in the release process and answer questions like, “Which features are ready for clean up?”. | x | x | x | |
| Dynamic configurations | Attach configurations (name:value pairs or JSON objects) to any of a feature flag’s treatments in order to dynamically control components of your features. Requires no code changes or re-deployments. | x | x | ||
| Essential scheduling* | Schedule a change in flag targeting to take effect at a later time and date. Eliminates the urgency to log into the Split console (or send an API request) when the change needs to occur. | x | x | ||
| Data retention for impressions | An impression is a record of which user encountered which feature flag, what treatment they were exposed to and which targeting rule drove that decision. | 90 days | 90 days |
Monitor Impact & Experiment
(Included with purchase of monitoring and experimentation events)
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| A/B/n testing | Combine feature flags with data to run full-stack experiments with two or more treatments. | x | x | ||
| Near real-time results calculation | Split will quickly calculate results for experimentation and monitoring within minutes. | x | x | ||
| Dimensional analysis | Pivot your experiment results to extract deeper insights and inform future experiments. | x | x | ||
| Multiple comparison correction | Controls the false discovery rate to ensure that the chance of a false positive is within your significance threshold. | x | x | ||
| Monitoring and alerts | Combine feature flags with data to support monitored feature rollouts. Receive alerts when metric degradations are detected. | x | x | ||
| Custom metrics | Create your own metrics based on events you are tracking and sending to Split. | x | x | ||
| Experiment window: data retention for events | Events enable you to measure customer behavior and application experience. They can be aggregated to create metrics. | 90 days | 90 days |
Secure & Govern Access
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| Multi-factor authentication | Ability to add two-factor authentication (2FA) for your Split account. With 2FA enabled, Split asks you to enter a verification code after authentication. | x | x | x | x |
| SSO / SAML authentication | Supports SSO as an option, SSO as mandatory (strict mode) and either invite-based or just-in-time provisioning of accounts. | x | x | x | |
| Edit restrictions | Control which users and/or groups have edit (write) permissions by default in an environment. Override those permissions at the individual flag, segment or metric level. | x | x | x | |
| Audit log for flag & segment changes | Audit logs are captured every time an account member changes a split, segment, or metric. These provide detailed records of every change and who made them. | x | x | x | |
| User groups | A group is a convenient way to manage a collection of users in your organization. You can use groups to grant administrative controls and grant environment, flag, segment, or metric-level controls. | x | x | ||
| SCIM support * | SCIM allows group membership in SSO to automatically determine group membership in Split saving administrators time adding and removing users from Split. | x | |||
| Workspace view restrictions | You can set view permissions to your workspaces to control which users, groups, and API keys can see whether a certain workspace exists and to access the objects in each workspace. | x | |||
| Require comments for flag and segment changes | Title and comments for changes are optional by default, but can be made mandatory. | x | |||
| Approval flows for flag and segment changes | Approval flows support peer review and/or mandatory sign-off of changes made to flag settings or segment membership. | x | |||
| Data export restrictions | Restrict which groups and users can export data from an environment. | x | |||
| Admin API environment restrictions | Supports scoping Admin API keys to have access only to specific environments within a single workspace. | x | |||
| Audit log for administrative changes | These logs provide detailed records of every admin change that took place and who made them. | x |
Integrate with Your Stack
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| [Developer Productivity] | |||||
| Slack | Send Split audit logs to Slack. | x | x | x | x |
| Azure DevOps | Access Split feature flags within Azure Boards and configure flag definitions via Azure Pipelines. | x | x | x | x |
| Jira | Create or connect feature flags to a Jira issue. View rollout status, flag configurations or any issues tied to a feature flag. | x | x | x | x |
| VSCode* | Bring feature flag information directly into developers’ IDE. View available flags, definitions, rollout statues and more. | x | x | x | x |
| [Developer Monitoring] | |||||
| AppDynamics | Send Split audit logs to AppDynamics. | x | x | x | |
| Datadog | Send Split audit logs to Datadog. | x | x | x | |
| NewRelic | Send Split audit logs to NewRelic. | x | x | x | |
| Papertrail | Send Split audit logs to Papertrail. | x | x | x | |
| Librato | Send Split audit logs to Librato. | x | x | x | |
| Rollbar | Send Split audit logs to Rollbar. | x | x | x | |
| Sumologic | Send Split audit logs to Sumologic. | x | x | x | |
| Webhook – audit logs | Outgoing webhook to integrate Split changes into external tools. | x | x | x | |
| [Data Import Export] | |||||
| Amplitude | Send Split impressions to Amplitude. | x | x | ||
| Amazon S3 | Send customer data from S3 to Split. Send Split impressions to S3. | x | x | ||
| Segment | Send Segment customer data to Split. Send Split impressions to Segment. | x | x | ||
| mParticle | Send mParticle customer to Split. Send Split impressions to mParticle. | x | x | ||
| Sentry | Send Sentry performance data to Split. | x | x | ||
| Webhook – impressions | Outgoing webhook to integrate Split impressions into external tools. | x | x | ||
| [Change Management] | |||||
| ServiceNow * | Send Split change requests to ServiceNow for approvals. | x | |||
| [Admin Logging] | |||||
| Webhook – admin audit logs | Outgoing webhook to integrate Admin changes into external tools. | x |
Support
| Tooltip | Developer | Team | Business | Enterprise | |
|---|---|---|---|---|---|
| Support package | Technical support packages can be customized to your team’s needs; select plans based on communication forms, hours of availability, and average response time. | Basic | Standard | Standard; Gold available | Standard; Gold or Platinum available |
| In-app tickets | Create support tickets directly within the Split app to reach out for help when you need us. | x | x | x | |
| In-app chat | Real-time chat accessible directly within the Split app. Available during ‘Business Hours’ to help your teams get unblocked quickly! | With Platinum support | |||
| Emergency escalation | On-call engineering for emergency ticket support; Split team member will respond promptly. | With Platinum support | |||
| Slack community | Split’s Slack Community is a respectful, open space to connect with both Split team members and other users. Perfect to ask questions, get help from the community, and share collaborative ideas. | x | x | x | x |
| Split Arcade | Split’s retro-themed, gamified customer education and onboarding program offers certifications in DevOps, feature flagging, experimentation and admin. | x | x | x | |
| Customer Success Manager | Our customer success managers help ensure your business objectives are fulfilled as a proactive, main point of contact. | Access to Customer Success Manager | Designated Customer Success Manager | ||
| Enterprise success plan | Built with your Customer Success Manager, this custom success plan is designed to help drive you towards the business objectives that matter most. | x | |||
| Experimentation Advisor | Our Experimentation Advisors are world-class leaders who both partner and guide you towards prioritizing experiments and making more data-driven decisions. | Available | Available | ||
| Integration Advisor | Our Integration Advisors guide you on how to implement Split into your DevOps practice. | Available | Available |
Proven ROI
Increase in Deploy Frequency
MTTR
Increase in Engineering Efficiency
Trusted by
Have a question?
Seats are the number of users you have provisioned in Split. A user is defined as one named login using an email address.
These are typically your software developers, operations team members, and product managers who add new feature flags, set targeting rules, and report on performance to measure impact. Price per seat, as well as seat limits, are based on tiered packages.
Monthly Tracked Key (MTKs) are the number of unique traffic keys (identifiers) evaluated by our SDKs within a calendar month. This is typically a combination of unique users, accounts, devices, or other custom identifiers that you define – and upon which feature flag decisions are based. One key seen many times in one month is just one MTK. Five keys seen many times in one month is five MTKs, etc.
For all packages, as a standard limit, we give away 50k free MTKs.
‘Monitor & Experiment’ can be accessed within both our Business and Enterprise tiered packages. This is purchased based on Event volumes. Within these packages, there are no Event data purchase limits.
Experimentation & Monitoring Events are any events occurring in your application that have been received through Split.
Events are data based on the actions users take and the experiences they encounter across your app. These can be any events that measure user behavior, experience, or engineering performance across your application, such as clicks, views, checkout events, or page load time. Used to power ‘Monitor & Experiment,’ you need to send Event data to Split for attribution at a feature-level.
Event data can be sent to Split in one of three ways:
- Call Split’s SDK track method
- Post a JSON body to Split’s events API
- Split integrations with Segment, mParticle, Sentry, Amazon S3, or Google Analytics
Split’s Integration Advisors are also here to help and assist you with standing up your events integration pipelines.
No, Event volumes are based only on what comes into Split. We do not charge on the export of event data. Data export is a feature included in our Enterprise package.
Not to worry! Our packages are designed to avoid unexpected charges, and we’ll also keep an eye out for you. If you consistently consume more than in your contract, we will reach out to you to develop a new contract that meets your needs.
Yes! You can create a Developer account here to get started with easy-to-use feature flags with up to 10 seats. Additionally, you can try out all of our paid features during your first 30 days.
If you are a current Split customer and have any questions about our new pricing and packaging, please reach out to your Split representative or support@split.io.
Please feel free to contact us at sales@split.io. We would be more than happy to chat!
Split Arcade is an interactive, gamified experience that provides teams with technical training, tutorials, and guidance from industry experts. This industry-leading self-guided learning is designed to ensure successful onboarding and upleveling at scale.
With knowledge checks along the way, team members earn badges, professional certifications and Linkedin badges to validate their progress. And, this all happens in a safe personal practice environment.
Yes. Onboarding, training, and access to our advisory services are determined by tier. However, technical support plans (which include communication channels, hours of availability, and initial response times) are selected separately. Learn more about our support levels here.