Thirty honest objections a Saudi Aramco evaluator would raise, each with a real fix.

Agreed, and we do not position PetroMap as an HPC or reservoir-simulation product. It is a light triage tier that ranks public-data hypotheses so your scarce EXPEC ARC and GeoDRIVE compute is pointed at the highest-value targets first. We prove fit with a bounded pilot on a defined public dataset, with a published accuracy scorecard, before any discussion of scale. We do not ask you to trust scale claims we cannot yet back.

We are explicit that we have no NOC reference yet, and we will not manufacture one. The honest route in is a small paid pilot on non-sensitive public data whose results are measurable and published, which becomes the reference. The pilot is structured so Aramco risks a modest, time-boxed budget, not production systems or proprietary data.

Fair concern for a small vendor. We mitigate it three ways: source-code escrow so the platform survives us, open output formats so nothing you receive is trapped in a proprietary tool, and a documented, reproducible methodology so a competent third party can operate the pipeline. During the pilot the interim local systems-integrator partner provides continuity of support independent of any one individual.

We hold ourselves to a no-unverifiable-claims rule. Every screening lead ships with its source, its method and a stated confidence, and results are reproducible from published inputs. We make no reserves claims and no accuracy claim we cannot demonstrate on your data in the pilot. If a claim cannot be reproduced, treat it as void.

You could, and for anything proprietary you should. Our value is not a secret model, it is the assembled, cleaned, provenance-tracked public corpus and the honest scoring around it, delivered now rather than after an internal build cycle. Treat PetroMap as a fast, low-cost pre-screening layer you can retire or absorb at will. That optionality, backed by escrow and open formats, is the point, not lock-in.

We do not ask Aramco to underwrite our going-concern risk. Pilot pricing is milestone-based and modest, so your exposure is capped. Escrow, open formats and a transition plan mean the deliverables outlive the company. If you want a stronger footing, the Wa'ed Ventures pathway lets Aramco evaluate us as an investment as well as a supplier.

Correct today, and we treat it as a sequenced commitment rather than a claim. The pilot runs on public data and needs no in-Kingdom entity. On award we file for a MISA licence and Commercial Registration, stand up in-Kingdom hosting and interim local support through a systems-integrator partner, and build toward our own Saudi staff and iktva local content over the plan period.

Understood and accepted. We do not connect to Aramco networks or handle non-public data until we hold the certificate. The pilot is deliberately scoped to public data outside Aramco systems so it can start without it. On award we engage an Aramco-authorized third-party audit firm, close the control gaps, and target CCC (or CCC+ for the applicable classification) before any sensitive integration. We also keep a deliberately minimal supply-chain footprint, with a documented software bill of materials, to make that audit tractable.

Our controls are mapped to the NIST Cybersecurity Framework functions of Identify, Protect, Detect, Respond and Recover, which gives your assessors a standard lattice to score us against and aligns with the SACS-002 control families. We provide the mapping as a spreadsheet in the data room so evaluation is against a known baseline, not our narrative.

Pilot data is public, so residency is low-risk, but we still honour the requirement by design. Production hosting moves to an NCA-aligned in-Kingdom region, whether a Saudi hyperscaler region or an Aramco-nominated cloud, with data at rest and in processing kept in-Kingdom. The platform is container-based specifically so it can be deployed where your residency rules require.

Supported. Production deployments use customer-managed keys, so Aramco holds and rotates the encryption keys through your own key-management service and can revoke our access unilaterally. We hold no keys to Aramco-classified data, and bring-your-own-key is the default posture for any in-Kingdom deployment.

PetroMap is a subsurface and asset screening tool, not a personal-data product, so we minimise personal data by design. Any incidental personal data (for example named authors in public literature) stays in-Kingdom under the production deployment, and we do not transfer personal data cross-border without a lawful basis under the Personal Data Protection Law. We document data flows so your privacy office can verify this directly.

Both are written into the pilot terms. Aramco gets a right to audit our controls and our data handling, and a documented exit and data-return plan with defined timelines. On exit you receive all your data and derived outputs in open formats, escrowed source is released per the escrow triggers, and our access is revoked. Leaving is a planned procedure, not a negotiation.

We commit to incident-response SLAs aligned with the National Cybersecurity Authority and the Saudi CERT (CERT-SA) reporting expectations, including rapid breach notification to Aramco and to the relevant authority within the mandated window, a named incident contact, and post-incident reporting. These SLAs are contractual in the pilot, not aspirational.

Today it is effectively zero, and we state that plainly. We commit to an iktva local-content plan over the engagement: a MISA entity, Saudi hires, local systems-integrator partnering, in-Kingdom hosting spend, and knowledge transfer, with year-by-year local-content targets over a five-year horizon. We would rather show a credible improving trajectory than overstate a starting score.

Correct at the outset. On pilot award we file for a MISA investment licence and Commercial Registration and complete SAP Ariba supplier prequalification in parallel, following the published Aramco become-a-supplier process. The pilot itself can be contracted as a small proof-of-concept, including via the Wa'ed pathway, while formal prequalification completes.

That is exactly why we propose a small, fast, low-value pilot rather than a large upfront contract. A bounded proof-of-concept on public data can proceed through a lighter path, or through Wa'ed or Aramco Digital, and produce a measurable scorecard before the full procurement and qualification cycle runs its course. The pilot de-risks the long cycle rather than fighting it.

The engagement includes real transfer: documented and reproducible methodology, training for Aramco and local-partner staff, source-code escrow, and open output formats. Combined with the iktva plan and a local systems integrator, Aramco builds in-Kingdom capability to run and extend the screening pipeline rather than depending on us indefinitely.

It does not overlap, it precedes them. PetroMap is a pre-screening tier that ranks public-data hypotheses and hands the shortlist to your proprietary stack for the real work. GeoDRIVE and TeraPOWERS do the high-fidelity modelling, Metabrain does the generative reasoning on your data, and PetroMap simply makes sure their compute is aimed at the best candidates first. We are a funnel into your tools, never a substitute.

Our outputs already export to open GIS and tabular formats, and a native OSDU ingestion adapter is a scoped, funded pilot milestone so screening results land directly in your OSDU instance as first-class records with their provenance intact. Standardising on OSDU is a feature for us, because open formats are how we avoid lock-in in the first place.

Yes. The platform is container-based and cloud-portable, so it deploys inside an Aramco-nominated in-Kingdom environment and interoperates with a Cognite Data Fusion or CNTXT-hosted data layer rather than requiring our own external cloud. Screening outputs flow into your industrial DataOps platform through open interfaces.

The absence of HPC is deliberate, not a shortfall. PetroMap is the cheap, fast triage tier that runs before the expensive tier. It narrows a large public-data search space to a ranked shortlist in minutes, so your HPC-class simulation is spent on vetted candidates. Putting a light screen in front of heavy compute is standard exploration practice, and it is precisely where a low-cost tool earns its keep.

The visualisation is a means, not the claim. Every mapped feature carries its public source, the method that produced it, and an explicit uncertainty and confidence band, so a geologist can trace any point back to its evidence. The value is the cited, reproducible hypothesis underneath the map, not the rendering. Where public data is thin, the map says so rather than papering over the gap.

Aramco owns its input data and the derived outputs produced from Aramco data, in full. We retain only our base platform IP, the general-purpose pipeline, code and public corpus that exist independently of your data. This split is written into the contract so there is no ambiguity: your data and its derivatives are yours to keep, export and use without us.

Two protections. A change-of-control clause lets Aramco terminate and take a clean exit if we are acquired by a party you object to, and source-code escrow releases the platform source to you on defined triggers, including change of control, insolvency or discontinuation. So a change of ownership never leaves Aramco stranded or exposed.

Pilot pricing is transparent and milestone-based: a fixed, modest fee tied to defined deliverables and an accuracy scorecard, with no open-ended commitment and no obligation to continue if milestones are missed. You pay for demonstrated results on your data, and scale-up is a separate, later decision made on evidence.

We agree to a hard bargain: prove it on your pilot data against pre-agreed thresholds, or we walk. Every result is backed by published methodology, cited public sources, reproducible inputs and a stated confidence, and the pilot ends with an accuracy scorecard scored against a held-out or expert-labelled benchmark. If we miss the thresholds, there is no scale-up and no invoice for unmet milestones.

No, we surface them. The methodology explicitly lists the public-data gaps: coverage holes, dated or coarse sources, and areas where open data cannot substitute for proprietary seismic or well logs. Leads in weakly-covered areas carry low confidence and are labelled as such. Stating where the data cannot support a conclusion is part of the honesty we compete on, and it is why PetroMap screens rather than concludes.

In the interim, support is delivered through a local Saudi systems-integrator partner under a defined SLA, giving Aramco an in-Kingdom, same-time-zone first line from the start. As the engagement grows and the MISA entity stands up, support transitions to our own in-Kingdom staff. You are never left with only a remote team for critical response.

We publish a versioned roadmap and a defined security-patch cadence: routine dependency and security updates on a regular schedule, with an expedited path for critical vulnerabilities, all tracked against the software bill of materials. Patch and maintenance commitments are part of the support SLA, and escrow ensures continuity of maintenance even in a worst case.