Live

Connections

The integration stack IBOS plugs into — every external system, where setup happens. Track A = the systems you already run. Track B = what IBOS provisions for you.

Configuration previewNo systems are connected. Credentials shown below are placeholders; fields don't submit anywhere and nothing is saved. Real wire-in happens after approval.

AI & Intelligence

the intelligence layer IBOS provides

Seed-to-sale & ERP

the cannabis system of record

Work & Ops

boards / tasks / CRM that ops already run

Compliance

state traceability — mandatory

Cultivation / Environment

Track A — systems clients already run

Point of Sale

Track A — closes the seed-to-sale loop

Finance

cost basis + revenue threaded to lots
Configure
claude
connectorClaudeThe AI copilot — vision analysis, agentic reports, natural-language ops queries, recall traceback summaries.
Track B · IBOSNot connected
The AI copilot — vision analysis, agentic reports, natural-language ops queries, recall traceback summaries. The intelligence layer IBOS adds on top of every other system.
secret
sk-ant-api03-…
Anthropic API key (console.anthropic.com)
https://mcp.theiaibos.com
Optional custom MCP server for tool access
claude-opus-4-7
Override IBOS-recommended model
Save will be enabled after approval
Note · Track B — IBOS provisions and operates the AI layer. API spend flows through IBOS billing; no client setup beyond approval.
About this page
Every connector listed here is a real integration target with a known field shape. The Configure panel is a visual mockup of the credentials each integration needs — no values are saved, no network calls fire, nothing is wired live. After approval the same page becomes the real settings UI.
Track A connectors plug into systems the client already runs (METRC, Monday, POS, cultivation gear, finance). Track B is what IBOS provisions on top (the AI layer). Together, this is the full integration footprint of the platform.