Frequently Asked Questions
FAQ
Answers on risk, continuity, compliance evidence, and long-term preservation economics.
What is the Capsyra Ecosystem?
Capsyra is a decentralized preservation ecosystem for critical business data. It combines WORM behavior, cryptographic verification, and policy-based governance so retention is not only immutable, but also independently provable over long horizons.
What happens if Capsyra disappears?
The ecosystem is designed so the coordination layer can disappear while preserved data remains accessible through DayKeeper participants. Data custody, integrity evidence, and preservation state are distributed across legal entities and locations, reducing dependence on a single operator.
How is this different from immutable cloud backup?
Capsyra is not only about immutability. It adds authenticity, integrity, and pre-committed retention logic fixed in time in advance. That means you can prove what was preserved, under which policy, for how long, and with which custody evidence.
Why is one-time funding safer than subscriptions?
With subscription storage, continuity can become uncertain if payment stops, budgets shift, or vendors change terms. Capsyra's funded preservation model is designed to support committed retention obligations upfront, with verifiable evidence that the obligation was planned and financed for the selected horizon.
How does this compare to traditional cold storage?
Traditional cold storage is usually provider-bound infrastructure. Capsyra is an ecosystem model that combines legal audit readiness, cryptographic proof, and independence from a single provider or even a single storage technology generation.
How do auditors validate independently?
Auditors can validate where data is preserved, which legal entity is currently safekeeping it, location constraints, and cryptographic authenticity and integrity evidence. They can also review the preservation commitment context used to support long-term retention obligations.
What happens during post-quantum migration?
Capsyra follows a crypto-agility model. As long as the AES content key remains protected, key-rotation paths can be applied. If that is no longer sufficient, a full re-encryption workflow can be executed as part of the migration framework.
How does Capsyra support legal retention obligations?
Capsyra is designed to support compliance with frameworks such as GDPR, NIS2, and CRA by providing verifiable retention controls, integrity evidence, policy tracking, and audit-ready traceability. Formal compliance outcomes always depend on your legal context, scope, and operational use.
How does Capsyra align with NIS2 requirements?
Capsyra provides controls aligned with NIS2-related resilience and evidence requirements, including traceability, integrity verification, and governance support. Final compliance status depends on your full control environment, implementation choices, and regulatory interpretation.
Can I export archives and verify them without Capsyra?
Yes. You can export preserved data in original formats and validate cryptographic evidence independently. This supports portability and reduces lock-in risk when governance, providers, or tooling changes.
Can I use Capsyra with my existing backup software?
Yes. Capsyra supports S3-compatible integration patterns so backup and automation tools can feed long-term preservation flows without forcing a complete replatform of daily backup operations.
What file formats are supported?
Capsyra can preserve any digital file format, from documents to databases and VM artifacts. Long-term readability still depends on your format strategy and lifecycle planning; preservation keeps evidence and integrity, while format sustainability remains an architectural responsibility.