GeoShield · powered by OpenPlanter

Who really owns the company in front of you?

Type a 9-digit code. See the owners behind the owners, and whether any of them is sanctioned, politically exposed, or two steps from someone who is.

Screen a company See how it works

Two steps out from the company you searched. That is the link a name-by-name check does not make.

1
Enter the code

Nine digits, or the company name in Georgian or English.
2
Follow the network

4 layers of ownership outward, drawn on one screen.
3
Export the file

A dated PDF that cites its source for every claim in it.

What it looks for

The real owner

Through holding companies and offshore layers, down to the person.

Sanctions

The company, its owners, and anyone within reach of them.

Public officials

Declared assets and interests, and the family around them.

State contracts and court cases

What the company won from the state, and who it has been to court with.

Read from this instance, not from a brochure

5/6 Registries feeding this graph right now Counted from records in the graph: napr, acb, spa, court, opensanctions, foreign_influence.

4 hops Ownership layers each screening follows outward Sanction proximity is flagged within 2 hops.

23 Lookups in the hash-chained ledger SHA-256 in audit_chain.log, mode required, HMAC-sealed. A query that cannot be recorded is refused.

Graph source	unavailable
Loaded
Access ledger	audit_chain.log · required

It runs on your hardware

The graph stays inside your network. The portal answers only this computer and loads nothing from any outside server — the search on this page posts to this same portal, nowhere else.

Try it on the invented four-company sandbox: python run_sandbox.py. No real person is in it.
Install offline from one archive — application, packages and container images. No internet route needed.
Point it at your registry access. Credentials are read from a 0600 file, never a command line, never a log.
Put an authenticating proxy in front. This portal names nobody on its own, and says so rather than guessing.

Personal data is handled for the accountability Georgian law expects: pseudonymised identifiers in the logs, personal numbers masked on screen, one ledger entry per lookup. Whether a given deployment is compliant is your data protection officer’s finding to make, not this page’s.