Films

APIs & AILength 1:32, Captions on screen

How apps talk to each other: APIs and MCP

An API explained with a restaurant waiter, and how MCP, an open standard, lets AI assistants use your apps with you in the loop.

Read the transcript

Every time your phone shows the weather, an app is asking another computer for help. That conversation runs through an API.

Think of a restaurant. You don't walk into the kitchen. You order from the menu, and the waiter takes it to the kitchen and brings back your dish. An API is the waiter. It carries your request to another system and brings back a response, and it only offers what's on the menu.

In an app, it looks like this: the weather app asks for Ottawa, and the weather service answers with data.

Now AI assistants want to use your apps too. But wiring every assistant to every app, one by one, becomes a tangle.

MCP, the Model Context Protocol, is an open standard for that. Its official guide compares it to a USB-C port for AI: one standard plug for any app that supports it.

Here's the conversation. The assistant asks the app: what can you do? The app replies with its tools. You say: book coffee with Sam on Tuesday. The assistant picks the right tool and asks before it acts. You approve, the app does the work, and the assistant confirms.

An API is the waiter between systems. MCP is the universal plug that lets AI use them, with you in the loop.

Azora. Good work, connected.

Sources

Checked on 18 October 2026. The restaurant is a teaching picture, not a definition.

AI & softwareLength 1:17, Captions on screen

AI brings the reasoning. Your records bring the rules.

Why large software vendors tie AI agents to permissions and audit history, and what that means for where a small team keeps its approvals.

Read the transcript

AI is starting to do the work inside business software, not just answer questions about it.

On October 13, Workday and Anthropic announced a partnership to connect AI reasoning to the rules that run the business. Every action follows the company's existing permissions and audit controls.

At ServiceNow, outside agents act only through checks: identity-verified, permission-scoped and fully auditable. Microsoft sells a control plane for agents, because you can't govern what you can't see.

Yet in a Deloitte survey of more than 3,000 leaders, only 21% had mature governance for AI agents.

For a small hardware team, the lesson is practical. If the work lives in inboxes and spreadsheets, an agent has no rules to follow and leaves nothing on the record. It can only follow your rules if your approvals and history live in one place it can read.

So before you add agents, connect the work. AI brings the reasoning. Your records bring the rules.

Azora. Good work, connected.

Sources

Checked on 18 October 2026. Company names are cited from their own announcements and do not imply any relationship with Azora.

QualityLength 1:45, Captions on screen

The quality question

What a quality management system is, why a serious customer asks about it before signing, and why the evidence starts at the prototype.

General information, not regulatory advice.

Read the transcript

Before a serious customer signs, they send a supplier questionnaire. One section decides a lot: describe your quality management system. If your answer is a promise instead of a procedure, the order waits.

A quality management system is the documented way a company designs, buys, builds, checks and improves its product. Procedures say how the work is done. Records prove that it was done.

A unit fails in the field. Can you trace it? The serial number, the component lot, the supplier, the inspection record, the root cause, and the fix. In minutes, not weeks. That trace is the quality system at work.

For medical devices, it is written into law. The European Union's medical device regulation requires device makers to run one. Health Canada asks for an ISO 13485 certificate with Class II to IV licence applications. In the United States, the FDA's quality management system regulation, in effect since February 2026, incorporates ISO 13485.

The decisions you make at the prototype stage, your design inputs, test results and supplier choices, are the evidence you will be asked for later. Record them as you go, not from memory after the first order.

Build the quality system while you build the product.

Azora. Good work, connected.

Notes on the medical-device rules

In the EU, the Medical Device Regulation (EU) 2017/745, Article 10(9), requires manufacturers of all devices other than investigational devices to run a quality management system and keep it up to date. In Canada, section 32 of the Medical Devices Regulations requires Class II, III and IV licence applications to include a quality management system certificate to the National Standard of Canada CAN/CSA-ISO 13485, and Health Canada requires that certificate to be issued by an auditing organization recognized under the Medical Device Single Audit Program (MDSAP); Class I devices need no device licence. In the United States, the FDA's Quality Management System Regulation (21 CFR Part 820), in effect since 2 February 2026, incorporates ISO 13485:2016 by reference. The FDA does not require ISO 13485 certificates, and some types of devices are exempt from its good manufacturing practice requirements.

So the film's line that a quality system is written into law for medical devices holds for every EU device other than investigational ones, and in Canada and the United States within the limits above.

This film describes quality systems in general. It makes no claim about Azora's software. Azora is not ISO 13485 certified.

Sources

Checked on 20 October 2026. The film's end card points to a post for its sources; they are the ones below. The supplier questionnaire, the failed unit and its trace, and the timeline are teaching examples, not sourced claims.

Azora product film

Inside AzoraLength 0:47, 4K · Captions on screen

Connected Solutions

Follow one example from customer feedback through a unit record, a quality investigation, a document revision and training.

Actual Azora interface with fictional sample records. Open the film in full screen to see the product details.

Read the transcript

One record can cross the company without losing its history.

Customer feedback: who reported it, which product, which unit.

Unit 360 follows that serial from build to field.

The complaint links to an NCR.

The NCR links to a CAPA: root cause, action, verification.

The CAPA can't close until the new revision is approved.

Signing records the signer, meaning and time.

When the revision takes effect, re-training is flagged.

The inspection binder packs CAPA, NCR and training records into one zip.

Keep the work and the evidence together.

Azora. One system of record.

About this example

The film follows a fictional linked case. Its CAPA requires a document revision; approval of that revision is a prerequisite for closing that CAPA. Retraining is flagged when the revision takes effect.

Product film prepared for SAAS NORTH AI, October 2026.

Looking for guides, security answers or help for your team? Visit Help & Resources.