Systems of record stay where they are
Rigline connects to all your existing data including databases, data warehouses, file storage, and your enterprise applications - wherever it lives - instantly.
| System | What Rigline uses |
|---|---|
 Peloton WellView | Spud/TD/complete, time logs, NPT, DDR remarks |
| Peloton ProdView | Volumes, allocation, downtime, first sales, shut-in status |
| Peloton LandView | Leases, obligations, ownership |
 Quorum Land | Lease admin, DOI inputs, obligation calendars |
 Esri ArcGIS | Tract/well attributes (cartography stays in GIS) |
 Enverus | Optional public and offset joins |
 Snowflake | Primary analytics spine |
 Databricks | Alternate spine |
 Google BigQuery | Analytics spine for cloud-native stacks |
 Amazon Redshift | AWS-side production and cost marts |
 Azure Synapse | Azure warehouse and serverless SQL pools |
| Amazon Athena | SQL over lake files without moving them |
| Google Cloud Spanner | Distributed operational tables |
 Dremio | Lakehouse queries across sources |
 Teradata | Long-running enterprise finance and production history |
 ClickHouse | High-volume time series — SCADA, telemetry, drilling ticks |
 Trino / Starburst | Federated queries across lake, warehouse, and databases |
 Apache Iceberg | Open tables on S3 or ADLS read in place |
 DuckDB / MotherDuck | Small-team marts and extract-based analysis |
 SAP / ERP | AFE, actuals, JIB, AP |
 Oracle | Legacy production and accounting schemas |
| Microsoft SQL Server | On-prem operational and land databases |
 PostgreSQL | Operational tables, allocation and field apps |
 MySQL | Departmental apps and legacy trackers |
| Amazon S3 | Bulk document, extract and export archives |
| Azure Blob Storage | Scanned land files, DDR exports, document archives |
| Google Cloud Storage | Document and extract buckets on GCP |
| Microsoft SharePoint | AFE packets, JOAs, curative and title files |
 Google Drive | Shared land, ops and vendor documents |
 Box | Contracts, division orders, scanned records |
| DUDirect upload | One-off PDFs, spreadsheets and CSV extracts |
 GitHub | Engineering docs, models and query definitions |
 GitLab | Engineering docs, models and query definitions |
| Azure DevOps | Work items, repos and internal documentation |
 QGIS | Tract, unit and pad geometry exports |
 Trimble | Surveyed surface locations and rights of way |
 P2 / TGS | Well headers, permits, offset geology |
| DNDocument / note stores | DDR text, curative notes (RAG where landed as text tables) |
Documents
Most land and well facts live in paper, not tables. Rigline ingests leases, assignments, division orders, JOAs, title opinions, curative correspondence, AFE packets, permits and daily drilling reports — native PDFs, scanned images and TIFFs, email attachments, and files sitting in SharePoint, Google Drive, Box or S3.
- OCR on scanned and photographed records, including handwritten margin notes flagged for review
- Extracts the fields land runs on: lessor, tract, legal description, expiration, royalty, WI/NRI, depth severance
- Every extracted value links back to the page and clause it came from
- Low-confidence extractions route to a person instead of into a report