Due diligence files hold some of the most sensitive material an organisation handles: a target's contracts, its people, its disputes. Clients and their regulators rightly ask where that material is stored and processed, and who can reach it. AnKre is delivered as SaaS only, and residency is designed into how the service is organised.
Content stays in its region
Each client's content is stored and processed in the region named in its contract: documents, search indexes, transcripts, findings and backups. Outside that region, only content-free information is kept: who can sign in, what to bill and where to route a request. Access across regions is controlled, and a backup copy outside the residency zone exists only when the client has agreed to it in writing.
Separation contains failures
Regional environments share nothing with each other at run time. A failure, a faulty release or a security incident is contained to one environment instead of spreading across clients and regions. A client who needs more can have a dedicated environment of its own.
One release everywhere
Every environment, shared or dedicated, is deployed from the same release. Regional differences are configuration, not separate products, so a fix or a control reaches every client at once and the behaviour you evaluate is the behaviour you get.
What AnKre does not offer
AnKre does not offer an on-premises or air-gapped edition. Keeping a single SaaS service is what makes the guarantees above consistent and verifiable. Requirements that would once have pushed towards an installation on the client's premises are met inside the service, for example by connecting AnKre to the client's own identity provider.
Principles that apply in every region
- A client's data serves that client only, and no model is trained on it without written consent.
- Each client is isolated, and opposing parties on the same deal are kept apart.
- AnKre staff reach client content only through a procedure the client approves, with logging.
- Nothing is shown before sign-in.