Public site kept separate
The ORELAB public website is a static presentation surface designed without a client database, authenticated customer session, or route into client geological data.
Designed for private geological data
Security & Data
ORELAB is designed to keep public marketing, customer application access, client geological data, and internal engineering operations in separate security boundaries.
Isolated client environments
Client deployments are designed with separate application, data, storage, credential, backup, and audit boundaries rather than pooling geological records into the public site.
Least-privilege access
Access is designed around authenticated identities and permitted capabilities, with server-side controls rather than relying on hidden navigation as a security boundary.
Customer-safe interfaces
Customer workflows are designed to present useful geological and operational information without exposing low-level infrastructure details, credentials, or unrestricted internal diagnostics.
Governed model and data operations
Model preparation, release, rollback, and authorised client-data use are designed as controlled operations with explicit provenance and data-use boundaries.
Traceable decisions
Important workflow, review, correction, and publication decisions are designed to remain attributable and connected to durable evidence rather than existing only in a browser session.
This page describes the target ORELAB deployment and security architecture for the private preview. Detailed contractual controls and deployment-specific commitments remain subject to implementation verification and the applicable customer agreement.