Petrora

STUDIO · COMING SOON

Build the page your work needs.

Studio is where you build custom pages, dashboards, reports, and analyses for your own territory, customers, and questions. Build one once, from your AI or in Studio, and Petrora keeps it current every night from the filings, at a URL you can keep private, share with a team or a customer, or publish.

Status · coming soon

Not live yet. The page format below is designed and versioned; Studio, which writes and renders it, comes after the connector beta. This page is how it will work. Tell us what you would build first and you will shape the order.

Tell us what you'd buildRoadmap

How it works

Ask, or build. Either way a small document is written, and the page is rendered from it, fresh, every night.

1 · You say

Who handles disposal in Reeves, and is volume up on last year?
Five operators hold most of the permitted capacity; the twelve-month volume is up on the prior year.3 sources · petrora.com
Save that as a page, and add a map.

Or open Studio and build it by hand. Same result.

2 · It writes a page document

  • "title""Reeves disposal board"
  • "filters"{ county: reeves, window: 12m }
  • metricpermitted_bbl_per_day
  • metricinjected_bbl · vs prior year
  • chartinjected_bbl by operator, monthly
  • tableoperators · wells · capacity
  • mapinjection_wells

Queries and blocks. No numbers live here; they are counted when the page renders.

3 · Your page, refreshed nightly

petrora.com/studio/you/reeves-disposal-board

Reeves disposal board

Reeves · 12 months

Permitted capacity

Injected, 12 mo

M2+ events

Injected volume by operator

Operators

Injection wells

PrivateBy linkPublicEmail MondaysPDF
An illustration of the flow, drawn with shapes. Every figure on a real page is counted from the record when it renders.

What you make in Studio

Four shapes of the same thing: a document that names its queries and its blocks, rendered wherever you need it.

Pages

A county brief in your words, an operator profile with your framing, the wells in your acreage by formation. One URL, refreshed every night, cited like every Petrora page.

Dashboards

Metrics, charts, tables, and a map on a twelve-column grid. Permitted disposal capacity against injected volume. Permits by operator by month. New entrants this quarter.

Reports

The same page rendered as a PDF or an email on a schedule. The Monday report builds itself from last week's filings and lands in the inboxes you name.

Analyses

Saved questions kept side by side: twelve operators' Wolfcamp programs over three years, every lease in a field ranked by decline. Re-run nightly, so the comparison never goes stale.

How a page is built

A page is a small document, not a screenshot. It names the queries it runs and the blocks that show them: metric, table, chart, map, text. Filters at the top (counties, operators, formations, a window) apply to every block.

No numbers live in the document. Every figure is counted when the page renders, so a page is exactly as current as the record behind it. The same document renders on the web, as an email, and as a PDF.

Because the format is plain and versioned, an assistant can write it, you can edit it, and both can read what the other did. That is what makes the two ways in below the same thing.

A page document, trimmed

{
  "version": 1,
  "title": "Reeves County water board",
  "filters": { "county": ["reeves"], "window": "12m" },
  "blocks": [
    { "type": "metric", "title": "Permitted disposal capacity",
      "query": { "fn": "swd.countyCapacity" }, "measure": "permitted_bbl_per_day" },
    { "type": "metric", "title": "Injected, trailing 12 months",
      "query": { "fn": "swd.countyInjected" }, "measure": "injected_bbl", "compare": "prior_year" },
    { "type": "chart", "kind": "area", "title": "Monthly injected volume by operator",
      "query": { "fn": "swd.countyInjectedByOperator" }, "measure": "injected_bbl",
      "by": "operator", "interval": "month", "top": 5 },
    { "type": "table", "title": "Disposal operators",
      "query": { "fn": "swd.countyOperators" },
      "columns": ["operator", "wells", "permitted_bbl_per_day", "injected_bbl"] },
    { "type": "map", "title": "Injection wells",
      "query": { "fn": "swd.countyWells" }, "layer": "injection_wells" }
  ]
}

Two ways in. One result.

FROM YOUR AI

Ask, then say "save this as a page"

Research the way you do today through the connector: who is ramping in a county, what a field's leases are doing, where the disposal capacity is. When the answer is worth keeping, ask your assistant to save it. It writes the page document with the same tools it used to answer, and the page appears in your Studio for review.

  • ✦Edit by asking: "add a map", "compare to last year", "make it weekly"
  • ✦Works in Claude, ChatGPT, Copilot, or any MCP client
  • ✦The assistant never invents a number; it points blocks at queries

IN STUDIO

Start from a template or an empty grid

Pick a block, point it at a query, set the filters. Save a county's disposal board as your own, swap the county, add your operators. Everything an assistant can write, you can click in Studio. Everything you click, an assistant can read and change later.

  • ✦Templates from public pages others have built
  • ✦Preview before saving; version history after
  • ✦Schedule a render as an email or a PDF

Whichever way you start, you can continue the other way. It is one document.

Private, shared, or public

Private

Only you. Your working boards, your territory, your pipeline.

By link

Anyone with the address: a teammate, a client, a prospect. Send a page instead of a spreadsheet, and it is still current when they open it next month.

Public

Indexed and citable, under your name if you want it. Public pages become templates for the next person and part of the public record of Texas analysis.

What stays true on every page

Counted, not estimated.
Every number on a page is counted from the records when the page renders, labelled with the month it is reported through. No forecasts, no fill-ins.
Every block has its sources.
A table of permits links to the permits. A metric links to the pages it was counted from. Hand the page to someone and they can check every figure.
Refreshed after the filings land.
The Railroad Commission publishes daily. Pages re-run after each load, so what you open in the morning reflects last night's files.
Yours to keep.
A page is a small document you can export, copy, and version. Nothing is locked in a proprietary view.

How it arrives

  1. 1"Save this answer as a live page" from the connector: the assistant writes the document, you get the URL.
  2. 2Templates and sharing: copy a public page, swap the filters, send the link.
  3. 3The full Studio builder, and scheduled renders as email and PDF.
Tell us what you'd buildWhat you can do today: connect your AIAlso coming: digital analysts →