Who is behind this.
Company details, and the question a buyer should ask a three-week-old company.
| Legal name | Falsify OÜ |
| Registry code | 17574308 |
| Registered office | Narva mnt 5, 10117 Tallinn, Estonia |
| Incorporated | 12 August 2026, Estonian Business Register |
| Editor and contact | Cüneyt Öztürk — [email protected] |
| Verify us | ariregister.rik.ee, search 17574308 |
The continuity question, answered properly
A company incorporated in August 2026 cannot promise it will be here in 2030, and you should not accept a promise as the answer. The better answer is that the thing you would rely on does not depend on us.
- Verification is offline and independent. Re-deriving a manifest hash needs the manifest text and any SHA-256 implementation. It does not contact us.
- The timestamps are not ours. Registry receipts carry an RFC 3161 token issued by a third-party authority and an entry in the public Rekor transparency log. Both verify if every server we run disappears.
- The specification is under the Community Specification License 1.0 and the code is MIT. Anyone may fork, host and continue them, and the conformance vectors are published so a fork can prove it agrees.
- The manifests are content addressed. Mirror the bytes you care about and the hash still identifies them.
What would be lost if we stopped: this website, the hosted registry index, and us. What would survive: every receipt already issued, and the ability to check it. We would rather you buy knowing that than on an assurance we cannot underwrite.