Pay for what runs, not for who watches.
This is the pricing model used to scope managed early-access deployments: platform, connectors, operators, and governed actions. The figures are indicative planning inputs, not a public checkout or binding quote. Scope and rates are confirmed in writing before billing starts.
Four dimensions, each with its own unit.
Each dimension is metered independently and appears as its own line on your invoice. No dimension bills on headcount, and no dimension bills for watching.
Platform
The managed deployment scope and governed operating pattern. The generalized kernel and Studio builder remain reference or early-access surfaces.
Connectors
Each system in a managed scope. Connector availability, implementation effort, and any per-source rate are confirmed in the quote.
Operators
Named workflow roles in the planning model. Availability and any per-operator rate are confirmed for the managed deployment.
Governed actions
One vetted, single-flight, idempotent change in the real world. Each plan includes a monthly allowance; usage beyond it is metered per action.
Three planning tiers. One managed quote.
These tiers communicate pricing posture. They are not self-service entitlements, and they do not imply that every listed platform feature is live today.
Per-unit rates, dimension by dimension.
Indicative managed early-access rates. They are not a public price list or contract; every rate and allowance is confirmed during onboarding before billing starts.
Platform
Table 1 · billed per operation, per month| Plan | Rate | Unit | Notes |
|---|---|---|---|
| Managed pilot planning tier | $0.00 | per operation / mo | Indicative scope: up to 2 operator roles, 3 connected systems, and 500 governed actions per month. Live capabilities depend on the deployment. |
| Team | $240.00 | per operation / mo | Planning model: 10,000 governed actions per month, with connector, operator, policy, and retention scope confirmed before launch. |
| Enterprise | Custom | committed volume | Residency, retention, identity, reseller, and volume requirements are scoped contractually. No feature is implied as live until verified in the deployment. Talk to us. |
An operation is one thing you run: a building, a site, a fulfillment pipeline. There is no per-seat charge on any plan.
Governed actions
Table 2 · billed per action, monthly in arrears| Meter event | Rate | Unit | Notes |
|---|---|---|---|
| Sensing | $0.00 | per event | Illustrative $0 metered rate. Source ingestion, storage, model, and deployment costs are confirmed in the managed quote. |
| Reasoning | $0.00 | per evaluation | Illustrative $0 metered rate. Model usage and service costs are confirmed in the managed quote. |
| Included allowance, managed pilot model | $0.00 | first 500 actions / mo | Illustrative allowance in the managed pilot model; not a public free-platform entitlement. |
| Included allowance, Team | $0.00 | first 10,000 actions / mo | Included with the Team plan. |
| Action beyond allowance | $0.01 | per action | Flat rate, no tier jumps. Billed monthly in arrears. A spend ceiling can be set per operation. |
| Vetoed action | $0.00 | per action | In this illustrative model, a policy-blocked proposal is not a billable action. The customer agreement defines billing. |
| Duplicate or retried action | $0.00 | per action | Known retries are intended to share an idempotency key and not create a second billable record; final terms are confirmed in the agreement. |
One governed action is one accepted change under the deployment's billing definition. Single-flight, idempotency, policy, and spend ceilings reduce duplicate and runaway costs; they are controls, not an absolute guarantee.
Connectors
Table 3 · billed per source, per month| Connector class | Rate | Unit | Notes |
|---|---|---|---|
| First-party connectors | $0.00 | per source / mo | Illustrative rate for a quoted scope. Kustomer, Magento, and Amazon Connect are live BearScope listings; commercial treatment is confirmed in the agreement. |
| Premium and partner connectors | from $29.00 | per source / mo | Indicative starting posture. Early-access connector pricing is confirmed in the managed deployment quote. |
Capability over connector: swapping one vendor for another under the same capability is config, not a new line item.
Operators
Table 4 · billed per operator, per month| Operator class | Rate | Unit | Notes |
|---|---|---|---|
| Included operators | $0.00 | per operator / mo | Illustrative included scope. Order Risk and Operations Analyst are live BearScope listings; availability and commercial treatment are confirmed in the agreement. |
| Specialist operator packs | from $49.00 | per operator / mo | Indicative starting posture. Early-access operator pricing is confirmed in the managed deployment quote. |
Operators are named AI workers, not seats. Their actions draw from the same governed-action allowance in Table 2.
A worked example, line by line.
A hypothetical Team deployment: three connected systems, two operators, and 14,200 governed actions. This is an illustrative planning example, not a customer invoice or quote.
Sensing and reasoning across all three systems, all month: $0.00. Overage actions are billed in arrears on the following invoice. Illustrative example; your plan is finalized during onboarding.
Size a month yourself.
Enter a hypothetical workload. The calculator applies the indicative assumptions above and does not create a quote, account, or billing commitment.
An illustrative estimate, not a quote. Scope, rates, allowances, and billing terms are finalized during onboarding.
Pricing, answered plainly.
Not as a public self-service offer today. The $0 tier is an indicative planning posture for a small managed pilot. The generalized kernel, Studio, CLI, SDK, and public API are not generally available, and all deployment costs are confirmed during onboarding.
Because Fibric does the work, not your headcount. Twenty people watching a dashboard cost us nothing. What costs is the operation itself, the systems you connect and the real-world actions Fibric takes. So we size pricing to what you run, not to how many people log in. Invite your whole team on any plan.
An action is a change accepted under the managed deployment's billing definition. Vetoed plans are not actions. Known retries are intended to share an idempotency key; the exact treatment of duplicates and downstream acknowledgements is written into the agreement.
The table models an indicative $0.01 overage, but no rate is binding until onboarding is complete. A spend ceiling and action-volume limits can be configured to reduce exposure; they do not make all downstream failure modes impossible.
Annual and monthly terms are agreed in the customer quote. The two-month annual discount shown above is an indicative planning assumption, not a self-service promotion.
The architecture aims to make a swap a connector configuration change, but only where the old and new connectors expose compatible capabilities and pass validation. Any migration work or pricing change is scoped before the swap.
Tenant isolation is a security requirement, not an upgrade. In live BearScope, tenant context and row-level security protect tenant-owned data. Export, retention, and reseller requirements are scoped separately.
Not through a public workflow today. The SDK and publishing documentation are reference previews. Managed early-access connector work is reviewed and provisioned with the Fibric team.
Scope one system. Verify what can run.
Request a managed deployment review. We will separate the live BearScope capability, early-access work, and reference architecture before giving you a quote.
No public self-service plan is available today. The figures above are indicative until confirmed in writing.