Start with a seat. Deploy when the workflow is ready.
Build and test oil and gas agents online with Torquay, Sparky, and frontier-model connectors. When a workflow proves itself, Apture can implement the production system, train your team, and deploy custom models in Calgary or inside your infrastructure.
Then teach it the basin.
The World Model Program brings operators into the evaluation and development process for basin-specific models. Contributed history is handled under agreed clean-room, consent, and audit terms; participation does not permit Apture to train another operator’s model on your data without written consent.
Create a Fleet Builder account and prove one workflow with an Individual, Professional, or Team plan. Bring Apture in when the workflow needs custom integrations, a custom model, internal deployment, governance, or staff training.
Where does my data go?
That depends on the deployment you choose. Fleet Builder can use Apture-hosted models and approved frontier connectors. Custom models can be hosted by Apture in Calgary or deployed inside your infrastructure. We define the data path and controls with you before production use.
What does Apture-hosted mean?
Apture-operated custom models run in eStruxture’s SOC 2 Type 2-audited data centre in Calgary, Alberta. That describes the facility controls; it does not claim that Apture itself has a SOC 2 report.
Do you train models on our work?
A custom-model engagement explicitly defines the approved training data. Apture does not use customer content to train models for another customer without written consent.
Can agents take actions without approval?
Professional and Team actions require sign-off. Enterprise can grant bounded autonomy to designated processes, while irreversible, external, regulatory, and financial actions remain gated.
What does implementation include?
Workflow discovery, agent design, integrations, custom-model work where needed, deployment architecture, approval policy, evaluation, staff training, and rollout support.
How is Site Twin priced?
Site Twin is scoped separately from Fleet Builder because facility digitization, source records, integrations, and deployment requirements vary by site.
Can we start on Team and move to Enterprise?
Yes. The intended path is to prove the workflow first, then scope the production deployment once the value, data path, and internal requirements are clear.
Start online or plan the production deployment.
Use Fleet Builder now, or talk to Apture about custom agents, models, integrations, Site Twin, and staff training.
Plan a deploymentOne workflow, a clear boundary, and a path to production.