--- title: "Why Avioverse Starts With Your Own Email" description: "Avioverse starts on a personal account, and companies can run it on company accounts only. Why a personal subscription is not a Part-IS finding, and who owns the AI." url: "https://avioverse.aero/articles/why-avioverse-starts-with-your-own-email" --- # Why Avioverse Starts With Your Own Email Avioverse starts on a personal account, and companies can run it on company accounts only. Why a personal subscription is not a Part-IS finding, and who owns the AI. [Dionysis Kefalas](https://avioverse.aero/articles/author/dennis-kefalas) 24 Oct 2026 11 min read On this page To start with Avioverse you type one thing: an email address. Most people type their personal one. I designed it that way on purpose. Avioverse is a second brain for one aviation professional. It holds your notes, your certificates, the regulations you keep returning to, the way you prepare an audit, and what Metis, the assistant, has learned about how you work. That collection grows over years and over employers. If the only way in were a company account, the company would own that brain. When you changed jobs, it would stay behind, and your method, lessons and context would reset to zero. So the default account belongs to the person, and the person decides how it grows. Companies can also run Avioverse as a normal company SaaS, with company accounts only. The personal default still raises a fair question from quality and security managers: is a personal subscription used for aviation work a Part-IS problem? ## Is it a Part-IS finding? A personal subscription is not, in itself, a Part-IS finding. Part-IS does not regulate who pays for a tool. It requires an organisation to know where its information-security risks to aviation safety sit, and to decide what to do about each one. **Part-IS is addressed to organisations.** [Article 2(1) of Regulation (EU) 2023/203](https://avioverse.aero/regulations/easa/part-is/implementing-regulation-eu-2023-203/cover-regulation-to-implementing-regulation-eu/article-2) opens with "This Regulation applies to the following organisations". It lists Part-145, Part-CAMO, air operators, training organisations and ATM/ANS providers; Regulation (EU) 2022/1645 does the same for design, production and aerodrome organisations. A licensed engineer or an auditor with a personal account is not an addressee, and neither is Avioverse as a software supplier. **What the organisation must do is risk-based.** Under [IS.I.OR.205](https://avioverse.aero/regulations/easa/part-is/implementing-regulation-eu-2023-203/annex-ii-information-security-organisation/is-i-or-205) it identifies its elements exposed to information-security risks, including the services it receives and the data behind them. It also identifies its interfaces with other organisations: > (b) The organisation shall identify the interfaces that it has with other organisations, and which could result in the mutual exposure to information security risks. It then classifies each risk by its potential impact on aviation safety, and accepts it or treats it under IS.I.OR.210. The rule asks for that assessment. It does not list permitted tools, and it does not say who must pay for them. **Paying is not the same as controlling.** A company-paid tool nobody assessed is the same gap as a personal tool nobody assessed. A personal tool the organisation has identified, classified and accepted meets the rule. The auditor's question is "did you identify it and decide?", not "who holds the invoice?". **Avioverse has a risk assessment for each way it is used.** We assessed all three set-ups described below: a personal account, a personal account working in a company Team, and company accounts only. In each, Personal workspaces and Teams are kept apart, so a company can name exactly what it is assessing. The risk assessment is published on the [AI assurance page](https://avioverse.aero/ai-assurance), with the Part-IS asset entry and a supplier questionnaire, ready for a company's own change process. **Contracting is a separate question.** [IS.I.OR.235](https://avioverse.aero/regulations/easa/part-is/implementing-regulation-eu-2023-203/annex-ii-information-security-organisation/is-i-or-235) applies when an organisation contracts part of its information-security management activities to someone else. Using a SaaS for audits, risks or procedures is not that. A company that runs its work in Avioverse assesses it as a supplier, exactly as it assesses its QMS or document-control SaaS. **The company sets the rules.** If its ISMS says company work happens only on company accounts, it runs Avioverse that way: every user signs in with a company email, with no link to a personal subscription. ## Three ways in, each with its own risk assessment There are three ways to use Avioverse, and each company picks the one its own policy calls for. | Way in | Sign in with | Who pays for Metis and the Brain | Who controls the company's records | | ----------------------------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------ | | Personal account | Your personal email | You | Not applicable: no company records | | Your personal account working in a company Team | Your personal email; Team mail goes to your company address | You, from your own plan | The Team's owner and admins | | Company accounts, like any company SaaS | Company emails only, with no link to personal subscriptions | The company, per account or as one company subscription by quotation | The company, through the Team's owner and admins | **The Team belongs to the company.** Anyone can create one, with no plan needed and no limit on members. Inside it, each member adds their company address, proven by a code sent to that mailbox. Team notices and work mail go there, never to a personal inbox, and the address lasts only as long as the membership. The owner and admins hold the controls a quality manager expects: - they open every Team record, including those limited to named people, while confidential reports keep their reporter's protection; - they switch on **Keep records in this Team**, after which only they can copy Team records out to a personal workspace or another Team; - they divide the Team into areas, such as Safety, Compliance or Line Maintenance, and place each person; - they remove a member, which ends that person's access and their company address in the Team at once. The records stay with the Team. **When a personal account works in a company Team, the person owns their AI.** Metis and the Brain are what the person has built: their context, their saved notes, the way they like to work. The employer may pay for them, for example by paying back the person's Pro plan as an expense. Paying does not make the employer the owner: if the person leaves, the Brain leaves with them. This is the same answer as [Who Should Pay for Personal AI at Work?](https://avioverse.aero/articles/ai-subscription-problem-personal-plans-work-jobs): the employer can pay, and paying is not owning. The company pays no licence fee for Team modules; Team files count against the Team owner's storage. **A company can pay for everyone.** An organisation that wants one company subscription for all its accounts emails us at for a quotation. We set it up as a separate contract, invoiced outside the app. The personal start is a default for professionals, not a limit for companies. ## AI that sharpens your thinking, not replaces it Metis is not built to hand you a finished risk assessment or a root cause to sign. It is built to make your own reasoning harder to fault. Take a finding where you wrote "the technician did not follow the procedure". Ask Metis to check it, and the method tests whether that is a root cause at all. Would removing it have prevented the event entirely? Or is it a symptom of something earlier, such as a procedure nobody could follow on a night shift with two people? That behaviour is written into the methods Metis follows, not left to chance: - **Root cause:** "A framework organises evidence; it is not an automatic answer and does not prove causation." The analysis is a draft you review; Metis never closes the finding or decides acceptance. - **Risk assessment:** Metis proposes a draft rating that you review, adjust and own. It never records the final acceptance. - **Airworthiness Directives:** Metis gives a proposed assessment, never the final applicability or compliance determination. - **Closing a finding:** a person makes the risk choice explicitly, either a finalised risk assessment or "No separate risk assessment required". - **Every answer is labelled:** "Checked against sources", "Review suggested" or "Not checked", so you know how much weight it can carry. - **The Brain suggests, it does not decide:** its review proposes a link, a duplicate or a conflict, and never merges, deletes or rewrites anything on its own. The reason is accountability. The person who signs the finding, the risk acceptance or the AD record answers for it in front of the authority. A conclusion you did not reason through is one you cannot defend. **The answer is only as precise as the context you give.** Metis reasons from what is in your account. You can upload your own documents, such as your exposition, procedures and past audit reports. You can work in projects, so each piece of work keeps its own files and history. You can take notes in the Brain and link them, so Metis sees how one lesson connects to another. Metis uses all of this when it reasons. A well set-up account gives more precise answers, built on your documents and your way of working. With no set-up, a precise answer is not guaranteed: Metis can still cite the regulation, but it cannot know your procedure, your fleet or your last finding. ## AI can do more than answer questions Aviation professionals already use AI every day. In [Microsoft and LinkedIn's 2024 Work Trend Index](https://www.microsoft.com/en-us/worklab/work-trend-index/ai-at-work-is-here-now-comes-the-hard-part), 75% of knowledge workers used generative AI at work, and 78% of those users brought their own tools. Often it is the same chatbot that explained the air fryer last night and drafted a risk assessment this morning. That chatbot answers one question and waits for the next. The larger gain is repeating work that gets done without you remembering it. Setting that up no longer needs a programmer. **The biweekly AD review.** Take a CAMO whose procedure says: open the EASA biweekly AD list, check each AD against the fleet, record the outcome. The engineer also receives three AD notification emails a day. In a heavy week both slip: the emails stay unread, the review moves to "next Monday", and next Monday has its own emergency. Nobody decided to skip it; the workload did. In Avioverse the same engineer sets it up once, without writing a line of code: 1. Pick the ready-made watch "New ADs & SIBs for an aircraft or engine" and type the types, for example A320 and CFM56. Or ask Metis in plain words; it shows the job and asks before creating it. 2. Avioverse fetches new and revised EASA ADs and SIBs three times a day. When one matches, Metis reads it and sends a short note: number, subject, effective date and required action, without repeating items already reported. 3. The review itself becomes a Procedure, with its steps written once. A repeating reminder on Tasks and the Calendar starts each run, and each run keeps its notes and evidence. 4. When the run starts, the matching ADs have already been read and listed in the watch's notes. The engineer checks them against the fleet and decides. Applicability and compliance stay with the engineer. The procedure did not change. What changed is that the reading, sorting and reminding no longer depend on a free hour that never comes. ## Free to use, paid to remember Every module is free. You pay when you want Metis to remember you, read your documents and keep working in the background. | | Free | Pro | | ---------------------------------------------------------------------------- | ----------------------------------- | ---------------------------------------------------- | | Every reference library, plus tasks, procedures, forms, audits and registers | Yes | Yes | | Teams, as many as you need, with no member limit | Yes | Yes | | Metis, the assistant | A small monthly allowance to try it | A monthly allowance in three sizes, plus extra usage | | The Brain, with memory across chats | No | Yes, with unlimited recall | | Your own documents, read in chat and in every module | No | Yes | | Background jobs such as the AD watch | On the free allowance | With web reach, memory and room to run | Pro is one membership in three sizes: Light, Frequent and Intensive use, at €9.99, €34.99 and €109.99 a month before VAT. Every size has the same features; only the AI allowance changes. The [pricing page](https://avioverse.aero/pricing) has the details. **Getting started takes about three clicks.** Click Start free, type your email, enter the 6-digit code it receives, and you are in your workspace. With Google it is Start free, Continue with Google, pick your account. Creating a Team is about three more: open the workspace menu, choose Create Team, give it a name and your company address. ## When a company needs its own Avioverse Some organisations need strict isolation: sensitive data on systems no other customer shares. Their own risk assessment, or their contracts with authorities and customers, may require it. They email us at for a quotation, and we set up a dedicated Avioverse on contract. It has its own server, database, file storage and backups, shared with no other customer. The regulation library is copied in and kept up to date the same way as on the shared service. Everything else works as on the shared service: the same modules, Teams, roles and Metis. ## Why the order matters I started with the person because that is where aviation work gets done: the engineer, the pilot, the auditor, the safety manager. Each of them can have a second brain they own. Companies run Avioverse as their own SaaS on company accounts, and email us for a quotation when they want something different, such as a dedicated deployment. Part-IS asks organisations to know their information-security risks and decide what to do about them. Avioverse does not take that decision away from the company. It makes it easier to take, while keeping the professional's brain with the professional. ## Frequently asked questions ### Is a personal Avioverse subscription a Part-IS finding? Not in itself. Part-IS is addressed to organisations and is risk-based: the organisation identifies the services it uses and the interfaces with other organisations, classifies each risk and accepts or treats it. It does not list permitted tools or say who must pay for them. A personal tool the organisation has identified and decided on meets the rule; an unassessed tool is a gap whoever pays for it. Avioverse publishes its own information-security risk assessment on its AI assurance page. ### Can a company use Avioverse with company accounts only? Yes. A company can run Avioverse like any company SaaS: every user signs in with a company email, with no link to a personal subscription. The company pays per account, or as one company subscription by quotation. ### Who pays for Metis and the Brain in a company Team? When a personal account works in a company Team, the person owns their AI. The employer may pay for it, for example by paying back the person's Pro plan as an expense. Paying does not make the employer the owner: if the person leaves, the Brain leaves with them. The Team's records stay with the Team. ### Can a company pay for all its accounts? Yes. An organisation that wants one company subscription for all its accounts emails us at hello\@avioverse.aero for a quotation. We set it up as a separate contract, invoiced outside the app. ### Does Metis write my risk assessment or root cause for me? No. Metis proposes drafts and tests your reasoning. A root-cause analysis is a draft you review, a risk rating is a proposal you own, and an AD assessment is never the final applicability or compliance determination. A finding closes only when a person makes the risk choice. ### What if a company needs strict isolation? It emails us at hello\@avioverse.aero for a quotation, and we set up a dedicated Avioverse on contract, with its own server, database, file storage and backups, shared with no other customer. The regulation library is kept up to date the same way as on the shared service. ## Related - [Who Should Pay for Personal AI at Work? Article · 7 min](https://avioverse.aero/articles/ai-subscription-problem-personal-plans-work-jobs) - [Personal SaaS vs Company SaaS in Aviation Article · 9 min](https://avioverse.aero/articles/personal-saas-vs-company-saas-aviation) - [Shadow AI in Aviation: Personal Tools at Work Article · 7 min](https://avioverse.aero/articles/shadow-ai-in-aviation-personal-ai-tools-at-work) - [Aviation AI Policy: What to Define Article · 7 min](https://avioverse.aero/articles/aviation-ai-policy-what-every-organisation-should-define) Written by Dionysis Kefalas. Retired Hellenic Air Force Captain and founder of Avioverse. [About the author](https://avioverse.aero/articles/author/dennis-kefalas) [Request early access →](https://avioverse.aero/register?redirect=https%3A%2F%2Fapp.avioverse.aero%2Fchat) Metis prepares answers from the EASA, FAA and EMAR libraries you choose for each chat, with numbered sources you can open, so you check the rule text before you rely on it. Opens in October 2026. Share [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Favioverse.aero%2Farticles%2Fwhy-avioverse-starts-with-your-own-email)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Favioverse.aero%2Farticles%2Fwhy-avioverse-starts-with-your-own-email\&text=Why%20Avioverse%20Starts%20With%20Your%20Own%20Email)