Previous-generation Bytesafe reaches end of life on December 31, 2026
Moving to the new Dependency Firewall
If you use the previous-generation Bytesafe, this page is for you. The new Dependency Firewall is open for evaluation, and we are starting to move customers across.
Plan your move before the end-of-life date. Everything you need to evaluate and migrate is on this page.
End of life, previous generation
December 31, 2026
Migrate to the new Dependency Firewall before this date.
- Applies to
- Previous-generation customers
- Get started
- Sign up
- Evaluation and migration
- No additional cost
- Existing customer offer
- 50% off for 3 months
What changes in the new generation
The previous generation combines dependency security with a hosted package repository. The new generation separates them: Bytesafe enforces policy on every package request, and your packages are stored by your repository manager or the upstream registry. That separation is what makes the new capabilities possible.
Previous generation
Packages are stored in Bytesafe. Policies and plugins control what can be used.
New generation
The firewall checks every request against your firewall rules and exceptions. Private packages are stored in your repository manager.
How much work the migration is
It depends on where your packages live today.
- Only public packages
- Nothing to move. Set up your firewalls and rules, then point your package managers at them.
- A repository manager you already run
- It keeps storing your packages while Bytesafe enforces policy. JFrog Artifactory, Sonatype Nexus, GitHub Packages, GitLab, Azure Artifacts and AWS CodeArtifact all work.
- Private packages stored in Bytesafe
- Those packages need to be moved to a dedicated package repository.
What the new generation adds
A redesigned policy and enforcement model, plus capabilities the previous-generation firewall does not have.
- More flexible rules
- Build rules on package name, version range, age, license, vulnerability score (CVSS and EPSS), upstream and other package properties. Conditions combine.
- Malware protection
- Block known malicious packages before they reach a developer machine or a CI/CD pipeline.
- Clear decision logs
- Every request is logged: the package, the version, the rule that made the decision and who asked for it.
- Time-limited exceptions
- Let a blocked package through with a documented exception. Set an expiry and the exception lifts itself.
- Policy as code
- Configure everything in the dashboard, or take the same configuration as JSON through the API and CLI, keep it in version control and review policy changes like code.
- Publish scanning
- Packages are inspected for malware, secrets and sensitive data before they are published to an upstream registry.
Pricing after migration
Every existing customer gets 50% off the new firewall for the first 3 months after migration. After that, most pay about the same or less than today.
50%
off your first 3 months on the new firewall
For every existing customer who migrates.
- Applies to the entire invoice: base fee and usage.
- Starts when your previous-generation subscription closes, so you never pay for both.
- No code to enter. Tell us when you have migrated and we apply it.
- One plan based on what you use most
- Your plan is based on whichever is highest: active users, packages scanned or downloads served. The other two are included.
- Most pay the same or less
- For most existing customers, comparable usage gives a similar monthly price or a lower one.
- Exceptions are clear before you migrate
- A few customers may pay more because of higher usage or Enterprise requirements. We review your setup and confirm your price before you move.
How to get started
Nothing switches at once. Both generations run at the same time while you set up and test the new firewall, so you move at your own pace until December 31, 2026. Evaluating and migrating come at no additional cost.
- 1
Start a trial account
Sign up yourself, no approval needed. Trials start at 14 days, and we automatically extend them for existing customers to cover the full evaluation and migration period at no additional cost. Set up a firewall, point one project or CI/CD pipeline at it, and compare what it allows and blocks against your existing setup.
- 2
Migrate before December 31, 2026
Recreate policies as rules, connect a repository manager and move private packages. Your current setup keeps working until you point traffic away from it, and nothing is switched off on our side before the end-of-life date.
- 3
Tell us when to start your discount
After you migrate, tell us when your offer should start. We close your previous-generation subscription and apply 50% off your new invoice, base fee and usage, for the first 3 months after migration, so you never pay for both.
Guides and support
- Dependency Firewall documentation
How the new firewall works, how to configure rules and exceptions, connect package ecosystems and integrate with your environment.
Explore the documentation- Migration guide
The detailed process for moving registries, private packages, policies and plugins from the previous generation.
Read the migration guide- Talk to us
Every setup is different. Ask us about your migration plan, repository architecture, moving private packages, recreating existing policies, pricing or how the new Dependency Firewall fits your environment.
Common questions
When does the previous-generation Bytesafe reach end of life?
Do we need to migrate immediately?
Do we pay for both generations while we migrate?
When does the migration offer start?
Is the new Dependency Firewall also a package repository?
Do we need a repository manager?
What happens to private packages stored in Bytesafe today?
How does pricing work on the new firewall?
Will our pricing change?
Can Bytesafe help us with the migration?
Start your migration with a trial
The previous generation reaches end of life on December 31, 2026. Start a trial now, evaluate and migrate at no additional cost, and get 50% off the entire invoice, base fee and usage, for the first 3 months after migration.