Everything below is cleared for publication and can be quoted without checking back. Where we will not comment, that is stated too, so you are not left waiting on an answer that is not coming.
VerifiedCrude builds the operational intelligence layer for bulk-liquid terminals, storage operators and downstream distribution. Its platform reads the systems an operator already runs, maintenance, tank gauging, HSSE and commercial records, and joins them into one governed operational record with an attributable audit trail, so questions from auditors, insurers and boards can be answered in minutes rather than days of manual assembly. It deploys on-premise or in a private cloud and requires no replacement of existing terminal systems. VerifiedCrude LLC is a Wyoming company founded by Alexander Tabarani.
Shorter version, 25 words: VerifiedCrude is the operational intelligence layer for bulk-liquid terminals, joining maintenance, tank, HSSE and contract records into one governed, auditable operational record without replacing existing systems.
| Field | Detail |
|---|---|
| Legal entity | VerifiedCrude LLC, a Wyoming limited liability company (United States) |
| Founder | Alexander Tabarani, Founder. Italian citizen, United States resident. |
| Category | Operational intelligence infrastructure for physical energy assets. Not a trading platform, not a commodity exchange, not a generic SaaS dashboard. |
| Sector served | Bulk-liquid and tank-storage terminals, fuel and petrochemical distribution, refineries |
| Deployment | On-premise or private cloud. Outbound-only architecture: the platform holds no route into a customer network. |
| Markets | European Union, United Kingdom and the United States Gulf Coast |
| Regulatory relevance | NIS2 Directive (EU 2022/2555). Oil transmission and storage operators are essential entities under Annex I. |
| Media contact | support@verifiedcrude.com. Replies within one business day; same day for deadline requests, say so in the subject line. |
Alexander Tabarani built this platform inside working terminal operations rather than from market research, and will give a direct answer or say he does not know. Topics where he has something specific to add:
Why most of the Article 21 obligations facing a terminal are evidence problems rather than IT-security problems, and what the 24-hour reporting clock actually demands of an operator's records.
Why terminal software projects stall on operational-technology risk rather than price, and why connection direction decides a security review more often than feature set does.
Why older gauging equipment is frequently easier to connect than modern closed systems, and why rip-and-replace is the wrong instinct at a working terminal.
What happens to a terminal's operational knowledge when the two people who know where everything is retire, and why this is an under-covered succession problem in the sector.
Where the honest limits are. Why the hard part of applying AI to industrial operations is the unglamorous data layer underneath it, not the model.
The commercial reality of selling infrastructure software to conservative operators as a single founder, including what does not work.
Stated plainly so you are not waiting on a response that will not come:
NIS2 for bulk-liquid terminal operators: scope, the ten Article 21 measures, and the Article 23 reporting clock.
Read →What auditors actually ask terminal operators for, and why records that exist still fail an audit.
Read →Terminal operations glossary. Useful if you are writing about this sector for the first time.
Read →Email support@verifiedcrude.com. Put your deadline in the subject line and it will be treated as one. You will be talking to the founder, not an agency.