New: Automated Design is live

Agents In Your Workspace

Vector Works on Your Wells.

Vector reads your wells, runs RodSim, and drafts changes inside PetroBench, on the wells and sims your team already uses.

Platform / Agents / Well Assistant
Well Assistant

Hi John.

Diagnose individual wells, run sims, interpret dyno cards.

Uses your org wells and sims.

Difference Inside Petrobench

Built on Your Wells and RodSim

Vector runs inside PetroBench on the engine and workspace your team already uses.

  • Engine

    Same RodSim math your engineers already run.

  • Workspace

    Opens on the well already in PetroBench.

  • Review

    Drafts wait for engineer signoff before anything is applied on the well.

Well Assistant

Hi John.

Diagnose individual wells, run sims, interpret dyno cards.

Uses your org wells and sims.

Scoped Access. Write Guardrails. Full Audit Trail

Agents inherit your PetroBench roles. Every run is logged. Live-well writes stay behind guardrails.

Scoped reads

Dyno cards, production, and RodSim history, only for wells inside your scopes.

Write guardrails

Live-well changes stay gated for engineer review. Sims and reads run under your roles.

Audit trail

Every run records inputs and outputs on the log, with who ran it and when.

Same SSO

SAML or OIDC through your IdP. Roles and regions match PetroBench.

FAQ Common Questions

Questions Teams Ask First

What production and engineering managers ask before a Vector pilot.

Yes. Vector calls the RodSim engine your engineers already run. The language model picks inputs and explains the card. Same inputs produce the same numbers as clicking Run in the workspace.

No. Sims and reads run under your access rules. Live-well writes stay behind write guardrails until an engineer approves. Every run lands on the audit trail.

Vector lives inside PetroBench. Chat opens on the well they already have open, same wells, dyno cards, and RodSim. Nothing extra to install.

Yes. Point those clients at the hosted MCP server. Same engine, wells, credential, and scopes as Vector. Vector is the chat surface inside PetroBench; MCP is for agents you already run elsewhere.

The same wells the engineer can already open. Vector inherits PetroBench roles and regions. It does not get a wider view than the signed-in user.

SSO through your IdP (SAML or OIDC), role-based access per team and region, and a full audit log. Live-well writes stay behind guardrails. Well access usually mirrors what you already have in PetroBench.

Yes. Start with a scoped pilot on access you already have. Widen regions once write-guardrail review is in place and the team is reading the audit trail.

Inputs, well-state snapshot, and outputs. You can open the run later and see what was asked, what RodSim returned, and whether a write is still gated.

We cover pricing on a walkthrough once we understand your wells and how the team will use Vector with RodSim.

It stays queued. Nothing is applied on the well until an engineer signs off. The draft remains on the well record so the next reviewer opens the same proposed taper, SPM, or pump change.

Put Vector on Your Wells.

Book a walkthrough for Vector on your wells, or see how MCP connects the AI tools you already use.