Back to vendors
A

Archimetis

Also known as: Archimetis Inc

Visit site
Entry priceCustom (contact sales)Full pricing detail

AI operational reasoning system for refineries and process plants that reads DCS, historian and safety-study data, runs unattended between shifts, and returns traceable, ready-to-act recommendations instead of acting on the plant itself.

Archimetis is an operational reasoning system for refineries, chemical plants and other continuous process industries. It connects DCS and historian data, integrity systems, incident logs and formal process safety studies into a single model of the plant, then reasons over that model to tell an operations team what matters at the start of each shift, why it is happening and what to check first. Findings are produced unattended. The system detects conditions overnight, projects threshold breaches ahead of time, and presents ranked items with severity and ownership when engineers arrive. A worked investigation runs as a sequence.

It searches the plant's own Bowtie and LOPA documentation for the highest consequence scenarios, checks each against live and historical data to see whether safety margins are actually being eroded, plots the relevant instrument tags, then generates and ranks hypotheses. Every conclusion can be traced back to the live data and plant document it came from, and the engineer chooses which branch to pursue at each step. The system is advisory by design and does not touch the controls. Engineers define the decision space, set constraints and validate assumptions, and the output is a recommendation a person acts on.

Deployment is cloud only, with each customer in an isolated GCP environment reached through outbound only connections that require no software agents, inbound firewall rules or changes to the OT network. Access is federated through SSO/OIDC, with least privilege service accounts and audit logging of every action. No security certification, hosting region, model provider or developer API is published. The product is sold through a demo engagement, with no public rate card and no self serve path.

Vendor details

Canonical URL

https://www.archimetis.ai

Category

Enterprise operations agent

Funding status

Raised $11.5M (February 2026), led by Inspired Capital, with participation from Homebrew, MCJ, Borusan Ventures, and Incite, plus operator angels including Jeff Dean, Matt Rogers, John Giannandrea, Alfred Spector, and Diane Tang. Founded 2023, headquartered in San Francisco, California.

Company status

independent

Use cases & customers

Primary use cases

Industrial process optimizationFailure prediction and troubleshootingPlant data unification and reasoningPreserving and scaling operator expertise

Target customers

Energy, refining, and chemical plant operatorsPharmaceutical and process manufacturersIndustrial operations and engineering teams

Deployment options

Per customer isolated GCP environment

Integrations

Connects DCS and historian data, integrity systems, incident logs and process safety studies into a single model of the plant, and ingests plant documentation, manuals, historical reports and incident notes. Data moves through customer approved, outbound only, cloud native mechanisms, with no software agents, inbound firewall rules or changes to the OT network. No protocol, named counterparty product or integrations page is published.

In practice

Your night shift has unusual reactor conditions and nobody watching the trends. Archimetis detects them overnight, identifies possible causes and has the actions triaged, with severity and an owner, before the morning meeting.

Your process safety engineers want to know whether safety margins on a unit are eroding. Archimetis searches the plant's Bowtie and LOPA studies for the highest consequence scenarios, checks them against live and historical tag data, and asks the engineer which risk to investigate further.

Your reliability team needs warning before an exchanger fouls past its limit. Archimetis forecasts when equipment such as E4405 will exceed its limit, 14 days out in its own example, and frames the next best investigation instead of raising a bare alarm.

Agentic Index coverage score

5.5 / 14 capabilities · 39%

Integrations & Tool Calling Partial

Plant data comes in by system class, in Archimetis's words "Connect DCS/historian data, integrity systems, incident logs, and process safety studies into a single model of your plant." A DCS is the plant control system and a historian is the time series system of record, both below the application layer. Document classes are named too (Bowtie, LOPA and PHA studies, manuals, historical reports and incident notes). The worked examples reference live data by instrument tag (EI-401, AI-101, TIC-7501.SP, K7502A), which points to a live historian connection.

Archimetis describes the transport only by what it does not need. "Archimetis does not require software agents, inbound firewall rules, VPN tunnels, or changes to your OT network. Data is shared through customer-approved, outbound-only, cloud-native mechanisms." Customers learn what will not be asked of their network but not how the connection is made. No protocol is named, whether OPC-UA, MQTT, a historian API, a file drop or a message bus, and there is no named product or connector catalog.

Archimetis only reads. It describes no writes into a DCS, a historian or a maintenance system, and the product is advisory by design.

Sourcearchimetis.ai/refining Integrate your plant and Enterprise-Grade Security card 03, /chemicalsread 2026-09-13

Workflow Orchestration Partial

A five step sequence runs unattended, but it is Archimetis's fixed method and customers cannot compose their own.

The method reads the plant's existing Bowtie and LOPA documentation to find the highest consequence scenarios, checks each against live and historical operating data, and evaluates whether safety barriers are stressed during upsets, "using control performance, not alarms or trips."

It then turns multisignal trends into an operating picture and surfaces the most likely risk signature and the next best checks. In the worked example, Archimetis searches documentation, extracts ranked scenarios, selects parameters, plots a month of tag data and interprets the margin. It then "formulates and ranks hypotheses, validates them against process data."

Archimetis owns every step. It names no workflow builder, step editor, exposed branching or conditional logic, or orchestration component, and customers cannot author, save, version or reuse a flow. The nearest customer control is "Engineers define the decision space. They set constraints, validate assumptions," which sets parameters for an analysis Archimetis designed.

Sourcearchimetis.ai/refining five-step How-to module and worked HDS example, /chemicalsread 2026-09-13

Knowledge Grounding & RAG Full

Reasoning is grounded in a maintained model of the customer's plant. Archimetis connects "DCS/historian data, integrity systems, incident logs, and process safety studies into a single model of your plant." The model is built once and reasoned over repeatedly, under a step called "Integrate your plant."

Archimetis "ingests plant documentation, manuals, historical reports, and incident notes," and names the formal document classes as Bowtie, LOPA and PHA studies, which make up the plant's approved risk framework.

Each conclusion links back to its sources. Archimetis says "Reasoning is fully traceable. Every conclusion can be traced back to live data and plant documentation, making recommendations easy to inspect, challenge, and refine." The reasoning runs "using the plant's approved risk framework, not a generic AI model."

Retrieval is a discrete step. In the refining worked example the agent says "I'll search our documentation for formal risk assessments, such as Bowtie or LOPA studies, that specifically cover the HDS unit," followed by a progress marker reading "Searching for HDS risk assessment documents." The answers cite named equipment tags and documented consequence bands from those studies, so findings come back attributed to their sources.

Archimetis does not disclose its retrieval technology, such as an index or embeddings.

Sourcearchimetis.ai/refining and /chemicals How we turn your data and expertise into decisions, Steer decisions with human judgmentread 2026-09-13

Human Oversight & Guardrails Full

Engineers steer the analysis before the system reasons. Archimetis frames this as steering decisions with human judgment. "Engineers define the decision space. They set constraints, validate assumptions, and inject real operating context into the analysis." A person bounds the space, approves the assumptions and supplies context.

The output goes to review first. Archimetis calls its approach "AI + human expertise (not AI instead of humans)," and says it "turns data into action, showing the reasoning behind every recommendation so engineers stay in control." The system produces "ready-to-act recommendations," which a person then acts on. Nothing reaches the plant without a person.

The agent asks for a choice at each branch, as the worked examples show. It asks "Which path seems best to you," offering a plant wide search, a focused unit investigation or a specific hazard analysis. It then asks "Which of these risks would you like to investigate further," and, after ranking three hypotheses, "Which of these paths would you like to explore first." The fifth method step says the same thing, that "Rather than issuing alerts, Archimetis frames the next best investigation... so engineers stay in control."

There is no approval queue, escalation path, risk tiering per action or sign off record, because the system takes no autonomous action and never touches the controls.

Sourcearchimetis.ai/refining Steer decisions with human judgment, worked HDS example, How-to step 05, /chemicalsread 2026-09-13

Security, Identity & Governance Partial

Customers sign in through "SSO/OIDC identity integration," and Archimetis adds "least-privilege service accounts" and "no standing credentials." It promises "Zero-trust access that satisfies enterprise IT."

Archimetis names no certificate, auditor or report, whether SOC 2, ISO 27001 or a penetration test summary, and has no trust center. It says only that it meets "strict enterprise compliance expectations," without naming a standard or anyone who verified it. Single sign on through OIDC is the one control customers use, and Archimetis names no role based access, SCIM or permission model over the agent.

Each customer runs in an isolated GCP environment, with TLS 1.3 in transit and KMS managed encryption at rest. Archimetis needs "no software agents, no inbound firewall rules, no VPN tunnels, no changes to your OT network," and data moves through "customer-approved, outbound-only, cloud-native mechanisms." These are properties of how the service is built.

Sourcearchimetis.ai/refining and /chemicals Enterprise-Grade Security Built Inread 2026-09-13

Observability & Auditability Full

Audit logs cover every action, in Archimetis's words "complete audit logs for every action." Its actions are agent actions, so that log records what the agent did.

A user can also follow a run step by step in the product, as the worked example shows. The agent states its plan ("I will plot the following key parameters for the reactor over the past month," then five named tags) and emits progress markers ("Searching for HDS risk assessment documents," "Assessing reactor temperature performance against safety limits").

It renders the chart it reasoned over and reports what it found, including the negative result, "While we haven't had an actual runaway event, operating this close to the safety limit reduces our ability to respond." A user can see which documents were searched, which tags were pulled, over what window, and how the conclusion followed.

Archimetis describes no run history view, activity log a customer opens, trace export or admin console. It states no retention period and does not say who can read the audit logs.

Sourcearchimetis.ai/refining Enterprise-Grade Security card 02 and worked HDS example, /chemicalsread 2026-09-13

Memory & State Persistence Not documented

In Archimetis's words, the product "turns ingested plant documentation and history into a living system that learns from every shift, decision, and outcome to preserve and scale institutional expertise." The ingested documentation is the corpus the system reads. The learning is a claim that the model improves over time, with no named store, scope, read or write surface, or lifetime. Preserving institutional expertise means knowledge that used to live in a retiring engineer's head now lives in the corpus.

Archimetis names no memory scope, lifetime or purge path. It describes no cross session recall, conversation history, saved context or preference store, and no case of the agent referring back to a prior run. The worked examples begin cold each time and set the scope again by asking the engineer "Which path seems best to you."

The plant model itself persists as an application data model built from customer documents.

Sourcearchimetis.ai/refining and /chemicals Learn from experienceread 2026-09-13

Deployment & Data Residency Not documented

Each customer runs in a fully isolated GCP environment with VPC peered transfers, so operational data is never shared or mixed. Archimetis names no region and makes no residency commitment. There is no self hosted option, and customers have no published way to choose where their environment runs.

GCP is the cloud Archimetis itself runs on. VPC peered transfers are a private network path between clouds, which changes how traffic reaches a tenant but not where the tenant is. Archimetis installs nothing in the customer's plant, with "No software agents, no inbound firewall rules, no VPN tunnels, no changes to your OT network," so there is no customer hosted option either. TLS 1.3 and KMS managed encryption at rest protect the data in transit and at rest.

Sourcearchimetis.ai/refining Enterprise-Grade Security cards 01 and 03, /chemicalsread 2026-09-13

Prebuilt Agents / Templates / Packs Not documented

One system covers many process types. Archimetis "adapts to a wide range of processes," with one line each for Bulk Chemicals, Ammonia, Petrochemicals, Specialty Chemicals, Polymers and Fine & Specialty on what it reasons across. Those lines name reforming, heat recovery, compression and synthesis. They also name distillation columns, crackers and reactors, polymerization reactors and downstream processing, and batch and continuous campaigns. Customers do not select among the six.

Ammonia, for example, is a paragraph saying the same reasoning engine understands ammonia synthesis, not a unit a customer adopts.

Archimetis has no page or URL per item, no agent names, and no selection or enablement surface, marketplace, library, template gallery, install action or entitlement language. The industry pages (/refining, /chemicals, /industrials) market one product, Archimetis, which reads, flags and recommends. The four benefit cards on the refining page (Smarter Process Safety, Continuous Cost Optimization, Reliability Informed by Insight, Economic Performance at Full Potential) are outcomes the one system delivers.

Sourcearchimetis.ai/chemicals Archimetis adapts to a wide range of processes, /refining Four ways we improve how your plant runsread 2026-09-13

Triggers & Channel Coverage Full

Detection runs overnight, unattended. "Unusual reactor conditions are detected over nightshift. Archimetis identifies possible causes and begins to triage and prioritize the actions required for operations. Engineers are in control, even before their morning meeting." The work runs with nobody logged in, and the results are waiting when engineers arrive.

Four kinds of trigger are named. The schedule is the shift, with "better decisions, from the first minute of every shift" and start of shift as a named state. Data conditions fire "when the data looks alarming," with timestamps such as "At 17:45, the WABT was detected to exceed its allowed operating window. This continued into nightshift." Forecast thresholds fire on a projection instead of a reading, such as "Fouling rate forecast: E4405 will exceed limit in 14 days," with the normalized fouling rate accelerating toward a 9.0 bar limit. Calendar state fires "when turnarounds loom."

Findings carry clock times in the product UI (7:01 AM, 9:05 AM), with severity High and ownership routed to Panel, Field Operations, Outside Operator or Maintenance. They arrive as detections that have already fired, not a dashboard a person has to open.

Archimetis also says "Rather than issuing alerts, Archimetis frames the next best investigation." That describes the form of the output, a framed investigation instead of a bare alarm, within the same five step sequence that begins with continuous checking against live data.

Archimetis names no trigger configuration surface, webhook, external event subscription or schedule editor. Archimetis sets the triggers, not the customer.

Sourcearchimetis.ai/refining hero scenarios and How-to section, /chemicalsread 2026-09-13

Model Flexibility & Routing Not documented

The model is not the customer's to choose. Archimetis names no model selector, admin entitlement over models, choice per request or per agent, routing policy, or bring your own model or key path, and it sells no tiers.

No provider or model family is named. Archimetis says only "advanced AI," "AI that understands your plant" and "an AI partner." The one line on the subject is about grounding, "using the plant's approved risk framework, not a generic AI model," which ties the reasoning to customer documentation and does not let a customer pick the engine.

Sourcearchimetis.ai/refining, /chemicals, homepageread 2026-09-13

APIs / SDKs / MCP Extensibility Not documented

No developer surface is published. There is no docs or developer site, developer portal, API or GraphQL reference, SDK, CLI, MCP server, A2A card, webhook publisher, marketplace or app listing, and no partner or integrations program page. Demos are requested at /request-demo.

Customers cannot extend the product either. Engineers "define the decision space. They set constraints, validate assumptions, and inject real operating context," which sets parameters for an analysis Archimetis designed. Customers cannot add a connector, author an agent, define a trigger, or call the platform from outside.

Data flows in from the customer's side through "outbound-only, cloud-native mechanisms," and recommendations go back to people. No external system can command Archimetis, query its state or build on it.

Sourcearchimetis.ai homepage and site-wide footer, /refining, /chemicalsread 2026-09-13

Testing, Debugging & Optimization Not documented

No way to test a change to the agent is described. Archimetis names no harness before deployment, scored test cases, regression suite, golden set, A/B or shadow comparison of agent configurations, judge or rubric, or accuracy, precision or hallucination metric, and it publishes no quality figure.

The product itself continuously evaluates a refinery. It assesses whether safety barriers are being stressed, validates hypotheses against process data, ranks causes by likelihood, and forecasts catalyst life. "Continuous cost optimization" and "the platform continuously analyzes energy use and process trade-offs" describe an optimization loop over the customer's plant, not over the agent.

Every suggestion "can be challenged and improved," which is human review of each output. The system "learns from every shift, decision, and outcome," with no mechanism named. When the agent "validates them against process data," it is checking its own hypothesis about the plant during a run. The demo includes a "custom ROI analysis for your operations," which people produce during presales.

Sourcearchimetis.ai/refining Benefits and How-to sections, /chemicalsread 2026-09-13

Browser / Computer-use Not documented

Every connection is a data path into a system of record, not a screen. "Data is shared through customer-approved, outbound-only, cloud-native mechanisms," and the connection is to "DCS/historian data, integrity systems, incident logs, and process safety studies." Archimetis describes no browser session the agent drives, no desktop control and no remote or local computer control.

A DCS vendor could redesign its operator console entirely and Archimetis would be unaffected, because it never sees the console.

Archimetis also needs no "software agents, inbound firewall rules, VPN tunnels, or changes to your OT network," so nothing of its own runs on the customer's endpoints.

The product's own chat and dashboard is Archimetis's client, not an interface it operates for someone. The product replaces a person reading screens ("instead of scanning dozens of trends," "instead of asking humans to stare at more dashboards").

Process plants run decades old instrument software with no modern interface, and screen scraping is a common answer there. Archimetis reads the historian directly and never touches the control network.

Sourcearchimetis.ai/refining Integrate your plant and Enterprise-Grade Security card 03, /chemicalsread 2026-09-13

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Pricing

Custom (contact sales)

Not disclosed. No unit of pricing is published, whether per plant, per site, per seat, per unit monitored or per tag.

Cost watchouts

Pricing is not published. Each customer runs in its own isolated cloud deployment, with data integration across plant systems and domain onboarding, and whether these are priced inside the platform fee or as separate lines is not published.

Variable cost rationale

No unit is published, so what the bill tracks is unknown. Nothing names a plant, site, seat, unit monitored or tag as the meter. Each customer runs in its own isolated cloud deployment, and the platform integrates data across plant systems, so infrastructure, integration and domain onboarding sit inside each engagement. No rate, cap or commitment structure is published, so nothing public limits the bill.

Sales call required

Yes, required for paid access

Free / trial

None published

Lowest paid plan

Not published

Key ambiguities

Archimetis is contact only. The full site has no pricing page, and the purchase path is /request-demo. No free tier, trial, self serve purchase or published enterprise tier appears anywhere. The billing unit is unknown: whether billing is per plant, per facility, per unit monitored, per tag or value based. Nothing published narrows it. The demo offer includes a "custom ROI analysis for your operations," which hints at value based framing but is not evidence of a value based contract. Also unknown is how an engagement starts. No pilot program or proof of value appears on the site, so whether a pilot comes first, and whether it is paid, is not published.

Agentic Index verified 2026-09-13

Alternatives to Archimetis

The closest documented capability profiles to Archimetis among enterprise operations agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

  • Norm Ai5.0 / 14Adds documented Prebuilt Agents, Templates & Packs
  • Validfor5.0 / 14Adds documented Prebuilt Agents, Templates & Packs
  • alfred_5.5 / 14Adds documented Model Flexibility & Routing
  • Balerion AI4.5 / 14Fuller documented coverage on Workflow Orchestration
  • Basis7.5 / 14Adds documented Prebuilt Agents, Templates & Packs
  • Certo6.5 / 14Adds documented Prebuilt Agents, Templates & Packs

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Head to head

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.