Multi-tenant on Azure. Your fleet's records sit in their own partition, behind your identity provider, with the OEM manuals we load on your behalf living in storage that has your name on it. Nothing crosses to another customer's data. Ever.
Multi-tenant means we share infrastructure. It doesn't mean we share data. Isolation is enforced at the data layer, not just the screen. Three boundaries do the work.
Your fleet, your users, your equipment, your knowledge entries, your conversations. All live in Azure Cosmos DB, partitioned by your tenant ID. Every query the API runs carries that ID. A query that doesn't carry it returns nothing from your tenant, by design of the partition model itself.
Cosmos DB · partition keyThe retrieval layer that powers chat answers runs on Azure AI Search. Every search the system performs has a mandatory tenant filter, applied by the API middleware before the query ever reaches the index. Cross-tenant retrieval is blocked at the layer above the index, not left to the client to ask for politely.
AI Search · mandatory filterThe original PDFs, scans, photos of binder pages, and voice recordings live in Azure Blob Storage. Each tenant gets its own container. Download links are short-lived signed URLs, fifteen minutes, scoped to a single file inside that container. They expire on their own.
Blob Storage · per-tenant containerWe don't issue passwords. Your team signs in through your existing IdP. When someone leaves, you off-board them where you already do, and they're out of Yardwise the same minute.
We come in with a large library of OEM manuals already prepared for the makes and models you run. The moment they land in your tenant, they belong to your tenant. Same isolation rules as anything you upload yourself.
Every manual we preload is written into your blob container, indexed against your tenant ID, and accessible only to your users. It is not a shared library. There is no central pool that all tenants read from.
Per-tenant copy · per-tenant indexA PDF you upload, a photo of a binder page, a voice note from a senior tech. OCR runs, chunks get embedded, and the whole lot lands in your index. Never anyone else's. Same partition, same container, same filter.
Same path · same boundaryQuestions your techs ask, notes your seniors write, conversations from your bay floor. None of it gets pooled into a global model, sold, or used to train a shared system. The model providers we call follow zero-retention terms on prompt content. Confirm exact retention terms with your account team
No pooling · no trainingEverything runs on Azure managed services. One cloud, one billing relationship, one set of compliance evidence to chase if your security team ever needs it.
Standard for everything Azure manages, plus a few habits we keep on top of it.
Inside a fleet, who can do what is small enough to fit on the back of a card. Outside that, an immutable ledger of every change tells you exactly what happened, who did it, and when.
"I run the workspace. I add users, set up SSO, decide who's a supervisor, and pull usage numbers when procurement asks."
"I run the approval queue. Senior tech writes a note, I look at it, I sign it off or send it back."
"I'm the one with grease on his hands. I ask the question, I listen to the answer, I get back to work."
"Anything that changes a record gets a row. Who. What. When. From which IP."
Some of the specifics that shape how Yardwise handles your data. Worth knowing before you sign anything.
Your data is partitioned by your tenant ID in every layer, from the database through the search index. The API layer won't form a query that crosses tenants. Not for analytics, not for benchmarks.
We trust signed tokens from your IdP. If you off-board someone there, they're off-boarded here at the same moment. No parallel account to clean up, no Yardwise password to forget.
The override your senior tech wrote about the mountain route stays in your index, serving your techs. It is not rolled into a model that another fleet benefits from.
If you're in the EU, your data and the AI calls that act on it stay in EU regions. If you're in the US, US. We don't route calls through wherever capacity happens to be cheapest.
Procurement questionnaires, vendor reviews, DPAs. Send what you have and we'll turn it around. Founders take every call.
Half an hour with someone from your IT or security team. We map our controls to whatever framework you live by, and you leave the call with the document filled in. Or close enough that you finish it in fifteen minutes.