Institutions issue documents. Almost nobody can check them.
That gap is where forgery lives, where days disappear, and where a bank ends up telephoning a registry to ask whether a piece of paper is real.
Edict began with a simple observation about document-issuing institutions — courts, universities, registries, professional bodies. They all run the same process, they all run it on paper, and they all have the same unanswerable question arriving by phone and letter: is this document genuine?
Custom software has been sold to individual institutions for years. Each one pays to build the same request queue, the same approval chain, the same certificate template — and then maintains it alone. Meanwhile the verification problem stays unsolved, because verification only works if there is somewhere for a third party to check, and a single-institution system has nowhere.
So Edict is built as shared infrastructure with each institution's data isolated at the database level, and with verification as a first-class public surface rather than an afterthought. You configure your documents, your workflow and your fees. Anyone holding something you issued can check it in seconds.
Where we are
We are early. We are onboarding our first institutions now. We are not going to put logos on this website that we have not earned, or quote numbers from deployments that have not happened.
What we will do is document the architecture in full, publish our security posture including the parts we cannot yet claim, and be in the room during your onboarding. Early institutions get direct access to the people building the platform and real influence over what gets built next.
Where we build
Edict is built for Nigeria first — multi-currency, multi-language and multi-timezone from the start, with identity verification wired to the providers that actually operate here. The architecture is not Nigeria-specific, and the roadmap is West Africa and beyond, but we would rather serve one market properly than claim several badly.