A
Nothing at signing.
A signature does not trigger an invoice. Deployment is invoiced against milestones as they complete, so what you have paid for is always something that exists. If a milestone slips, the invoice slips with it.
Four prices are ours. The fifth, the one that grows with use, is billed to you by your own cloud provider.
Four prices, and one of them is not ours.
You're not buying seats. You're buying a private AI platform on your own cloud, yours to keep. There is no per-user fee, no minimum term on the monthly, and nothing to pay at signing. The platform is deployed into an account you own, so the compute invoice arrives from your provider and never passes through us.
Four rungs, priced in the open.
PRICING · THE LADDER
Each rung is a decision you make on evidence from the one before it. You can stop after any of them and still hold something real: a written assessment, a running platform, a capability your people use. Nothing here is a subscription to access your own environment.
Every figure below is Canadian dollars, before tax, and is the same figure we quote on a call.
Published price
Scoped with you
Billed by your provider
01 Published
Strategic assessment
$2,500once
A bounded engagement that ends in a written deliverable, not a proposal deck. You keep it whether or not you proceed with anything else.
- A map of how your systems connect and where your data actually travels
- The posture questionnaire worked through with your security owner
- A recommended posture tier with every override written down and reasoned
- A deployment plan sized to your account, and an honest verdict where the answer is no
Bounded · yours to keep
02 Published floor
Deployment
$2,500from
Typically lands around $5,000 once the solutions pipeline is scoped. The platform is built into your cloud account from a tagged release, not assembled by hand.
- orgOS stood up in an account you own, white-labelled to your name
- Your content policy written into the deployment and enforced by cloud identity policy
- Users, roles and grants configured with your administrators
- Infrastructure as code, runbooks and an architecture record checked against what was deployed
Nothing at signing · milestone invoicing
03 Published
Managed operations
$500per month
The service that keeps a deployment current. It buys our work, never access to your own platform, which is why cancelling costs you us and nothing else.
- Releases cut and rolled one deployment at a time, confirmed
- Drift and diff checks before a change, acceptance runs against your real deployment after one
- The model catalogue refreshed as providers change it; access and role changes
- Cost watch with a budget alarm, a dated operations journal, and a direct line to the person who built it
Cancel anytime · no minimum term
04 Scoped
Capabilities
Scopedper deliverable
Enterprise automation and forward-deployed engineering: the modules that carry your way of doing things. Priced per deliverable so an exception is visible rather than absorbed.
- A named outcome, a fixed scope and a gate at the end of it
- Most modules never call a model; a deterministic tool is often the right answer
- Longer engagements are priced in the range of one junior technical hire, without the permanent headcount
- Each one leaves a versioned artifact behind, not a consulting memory
Quoted before work starts
A word this page does not use commercially
On this site, "tier" means security posture, not a price plan. Baseline, Standard and Strict describe how hardened a deployment is: networking, audit trail, key management, residency. They are chosen by the questionnaire during the assessment, not bought off a page. See posture tiers. There are no product tiers and no packages.
If you stop paying, you lose us, not the platform.
ASSET · SERVICE
The most useful thing to understand about this ladder is that it pays for two different kinds of thing. One is an asset that ends up in your account. The other is a service that ends the month you say so. Most software pricing deliberately blurs those two, because the blur is what makes cancelling frightening.
| Question | The asset: your deployed platform | The service: $500 a month |
|---|---|---|
| Where does it live | ✓Your cloud account, under your billing | △Our practice: our releases, our checks, our hours |
| What exactly is it | ✓The running platform, your data, and the infrastructure as code that built it | △Releases, drift checks, acceptance runs, catalogue refresh, cost watch |
| Is it recurring | ✕No. It is deployed once and it is yours | ✓Yes, monthly, cancel anytime |
| What happens if we part ways | ✓It keeps running. You sign in to your own cloud | ✕It stops at the end of that month |
| Is there anything to extract or migrate | ✕Nothing. It never left your account | ✕Nothing. We hold no data of yours |
| What would you need afterwards | △A competent cloud engineer, plus the runbooks we deliver | △Another provider, or your own team, or nobody |
"Yours to keep" is true, and operating it afterwards is real work, which is why infrastructure as code and runbooks are deliverables rather than a courtesy. Moving the platform to a different cloud provider would be a rebuild, not a migration. Ownership and exit spells that out.
The bill we never touch.
COMPUTE · NOT OURS
Structural, not a promise
There is nothing for us to mark up.
Inference and infrastructure are billed by your cloud provider directly to you, at their list price. That is not a discount we are extending. It is a consequence of the architecture: the platform runs in an account you opened, so the invoice has your name on it and we are not a party to it.
- 01We are not a reseller. No compute passes through our account, so no margin can be added to it without you seeing a line we do not have.
- 02You can audit it without asking us. Cost reporting is in your console, per model and per consumer, because every caller runs under its own tagged profile.
- 03Usage is metered per person, in tokens. Settled against the provider's own record of each call. The product holds no currency at all, so it will never show you a dollar figure. Your cloud bill does that.
What we have seenNOT A QUOTE
- Platform at BaselineRoughly $5 to $10 a monthInfrastructure only, excluding inference
- Private-network tiersAbout $110 a monthStandard and Strict add real infrastructure
- Light team usageAn estimated $40 to $120 a monthAll in, on one deployment's cloud bill
- A knowledge questionAbout 4 to 5 centsEstimate at a mid-tier frontier model's list price
- Per seatNothingNo seat concept exists in the product
Observed on real bills·Your workload will differ
Read this as a range, not a quote
Those are figures we have seen on deployments we operate, not a commitment. Usage is the variable and it is yours to drive. A rising query count with flat value is a cost problem, not a success, and a pricing page is the right place to say so rather than month four. The arithmetic, the things that make a bill spike and the controls that bound it are on compute costs.
Terms, in ordinary sentences.
TERMS · PLAIN WORDS
B
Net fourteen.
Invoices are payable within fourteen days. There is no annual commitment anywhere in the ladder, no automatic uplift, and no renewal date that quietly re-prices you.
C
Cancel the monthly anytime.
Managed operations stops at the end of the month you say so. There is no exit fee, no data extraction project and no handover invoice, because there is nothing of yours in our custody to hand back.
D
Scope changes are quoted, not absorbed.
A capability is scoped, quoted and agreed before work starts. The exception gets a price rather than a hiding place inside a platform fee, because a buried exception is how a product quietly becomes a consultancy.
What the price does not buy.
NOT INCLUDED · SAID FIRST
01
Your compute.
Inference and infrastructure are billed to you by your provider at list price. We never take custody of that bill, and we do not quote it because we do not control your usage.
02
The gateway, at a list price.
The operational knowledge gateway is a different product with a different shape, so it carries no published price. It is scoped in the assessment, against your corpus and your assistant.
03
Capabilities you have not scoped.
Deployment buys the governed environment. The modules that carry your operating capability are separate deliverables, each with its own scope and its own gate, and none of them are assumed.
One more thing the monthly does not buy: managed operations is deliberate, scheduled work plus a direct line to the person who built the platform, and it carries no published response-time or uptime commitment. What the fee does buy.
What buyers actually ask.
QUESTIONS · PRICING
01Why is this so much cheaper than a consultancy programme?
Because most of the work is already done and is not being redone for you. A deployment is a tagged release of one product, layered with your parameters and built into your account by a factory that refuses a tag not on the mainline and refuses a dirty checkout. A consultancy programme prices the discovery, the architecture, the build and the governance narrative as bespoke labour every time, because for them it is.
The honest counterpart: a productized deployment means you take our shape rather than an arbitrary one. Where your requirement genuinely does not fit the product, that becomes a scoped deliverable, priced and visible, instead of a surprise line inside a programme. Consultancy programmes, compared.
02Why charge for an assessment at all?
Because it is work, and because a free assessment is a sales call wearing a deliverable's clothes. Yours produces a map of how your systems connect and where data travels, a posture recommendation with every override reasoned, and a deployment plan sized to your account. You keep all of it whether or not you go further, including the version where the recommendation is that governed AI does not earn its place in your organization yet.
It is also the gate that protects you. We would rather charge $2,500 and tell you no than deploy something that should not have been deployed. What the assessment covers.
03What does $500 a month actually buy?
Concretely: releases cut and rolled to your deployment deliberately, one at a time and confirmed; drift and diff checks before a change; acceptance scripts that exercise your real deployment over HTTPS after a deploy, where a replayed ticket, a forged session, one module's session presented at another module's host and a corrupted upload must each be refused; the model catalogue refreshed as providers change it; access and role changes; cost watch with a budget alarm on the account; a dated operations journal; and a direct line to the person who built it.
New capability is not maintenance, so a module, an integration or a new workflow is scoped and priced as its own deliverable rather than absorbed. Managed operations in detail.
04Are there per-user fees?
No. There is no seat concept anywhere in the product, and no place for one to hide: usage is metered per person in tokens against the provider's own record of each call, with quotas that fail closed, and the product holds no currency at all. Adding your tenth or your hundredth person does not change the $500, and it does not change the deployment price. It changes your cloud bill, which arrives from your provider.
05What if we outgrow it?
Outgrowing the platform and outgrowing us are two different events, and we price them that way. If your usage grows, your compute bill grows and our fee does not. If you need a harder posture, that is a change of tier and a redeploy, with the infrastructure difference landing on your cloud bill rather than ours. If you want capabilities your people use daily, those are deliverables, scoped one at a time.
If you outgrow us as an operator, the platform is already in your account with its source, its infrastructure as code and its runbooks, and another provider can take it on. That is the whole point of the split above.
06Can we pay annually?
Ask. We have no published annual plan and no published discount. If annual billing suits your finance team better, raise it in the assessment and we will agree terms in writing.
07What currency, and is tax included?
Canadian dollars, before tax. org.tech is operated by Mind Model AI Inc. in Ontario, Canada, and applicable tax is added to the invoice. Your cloud provider bills you separately, in whatever currency your account is set to.
The claim this page exists to make
You're not buying seats. You're buying a private AI platform on your own cloud, yours to keep.
Four prices, one of them not ours, and a monthly you can end without losing anything you paid for.
- 01The asset is yours. Deployed into your account, with its source and its infrastructure as code.
- 02The service is cancellable. You lose us, not the platform.
- 03The compute is invisible to us. Billed to you at list price, with nothing in between.
⎯⎯ Book the strategic assessment ⎯⎯
Your private AI, inside your control ·
A bounded $2,500 engagement that ends in a written deployment plan for your own account, yours to keep whether or not you proceed.