Transcendence
Change with a way back.
Modernise encryption with control
Encryption has to keep pace with new requirements. Transcendence plans this transition based on the Quantum inventory and implements supported changes after testing and your approval.
Transcendence works locally in your project.
What needs to change, and when?
The inventory becomes a plan for the transition.
- Context
- Target algorithms
- Migration waves
Explore the details
Transcendence connects the findings with how your software is used and what it needs to protect. The result is a plan with target algorithms, deadlines and migration waves. For example, data that must remain confidential for many years needs a different timeline from short-lived information.
The risk of “harvest now, decrypt later” informs the plan. Missing information stays visible.
Test changes in a copy first
This shows you whether the change passes your tests.
- Preserve the original
- Test a copy
- Compare the state
Explore the details
An independent checker examines the change package. Project tests and algorithm checks then run in a copy. When the required Linux conditions are met, this test is isolated from the network and runs with resource limits.
A passing test applies to that exact change package and project state.
You approve the transition
Only then does the tested state enter your project.
- Back up
- Apply
- Verify
Explore the details
A change is applied only after a matching test has passed and you have explicitly approved it. Transcendence backs up first and verifies afterwards. If it finds deviations, it restores the backed-up files. Changes can also be kept on a separate local Git branch.
File contents can be restored byte for byte. Nothing is pushed automatically.
Crypto agility: switch in stages
Introduce new algorithms while existing data stays readable.
Record the existing state
Explore the details
The layer is added at supported locations. It separates algorithm selection from the application. The policy contains references to key sources, not key values.
Read old and new encrypted formats
Explore the details
The software can read both old and new encrypted formats. An existing file, for example, stays accessible while you prepare the next step.
Encrypt new data with the new algorithm
Explore the details
New output uses the new algorithm. Existing data stays accessible through the reading support already in place.
Sign with the new key
Explore the details
New signatures use the new key. Transcendence does not read private keys itself; the application obtains them through the configured key source.
Deliberately retire old signatures
Explore the details
Old signatures stop being accepted only after the prepared transition. You deliberately control the timing.
Targeted change with a way back
Only the verified part changes; the rest of the project remains untouched.
Separate from the original
The original remains in place while the change is tested separately.
With your approval
The change is applied only after a passed test and your approval.
Back to the saved state
If verification fails, saved file contents are restored byte for byte.
Explore the details
Supported languages and changes
Available recipes cover selected outdated hash algorithms and the agility layer for Node.js, Java, C#/.NET, Python and Go. Only changes covered by a recipe are applied.
The Python layer requires an existing use of cryptography. C and C++ findings enter the plan but have no change recipes.
Work directly in your project
The command line and local interface support planning, tests, approval and history. Migrations can be saved and scheduled. CI templates are available for your own Linux runners.
Target environment: Linux x64 with Node.js 24.
A change remains reversible
Files are backed up before the change is applied and checked again afterwards. Rollback restores their contents byte for byte. This also lets you review an approved change separately on a local branch.
Owners and file permissions are preserved. ACLs and extended attributes are not transferred.
Test Avalanche in the beta
Questions about Transcendence
What does Transcendence need to get started?
Your local software project and a Quantum report in JSON v2 format. Information about how the software is used and its protection requirements refines the plan. Transcendence uses Quantum’s findings and does not run scans itself.
Can Transcendence replace any encryption automatically?
No. Planning and the actual code change are separate steps. Only supported recipes are implemented: selected outdated hash algorithms and the introduction or further development of an agility layer. Every application requires a matching successful test and your explicit approval.
What does encryption migration mean in practice?
Encryption moves to another algorithm in stages. For example, software can first learn to read old and new formats, then begin encrypting new data with the new algorithm. The agility layer supports these transitions at supported locations.
When are tests isolated from the rest of the system?
When the requirements of the Linux test profile are met, including root privileges, separate namespaces and limited memory. Tests then run without network access and with resource limits. Otherwise, the missing protection is shown and the run requires your separate permission.
What does a passing test tell me?
That the change package passed the project and algorithm checks run in the test copy. The result is only as broad as those tests; it is not a general security guarantee.
How can I try Transcendence?
Transcendence will launch together with Quantum and Anchor. You can express your interest through the beta registration. We will contact you as soon as the next steps for taking part are ready.