Customer Guide

Know your risks. Protect your business.

Aevyra reviews supported information from services you authorize and turns it into a security action plan: what needs attention, why it matters and what to do next. It provides assessment guidance; it does not automatically repair your services or guarantee that your business is secure.

Before creating an account or approving access, read Privacy, Support and Pricing.

Start your security check

Create and verify your account → connect AWS, Microsoft or both → add authorized websites if needed → Show my results → your security action plan.

After account setup, the app has two stages: Connect the services you use and Your security action plan. You do not need to complete separate business-context or manual evidence-review stages before a normal connected assessment.

1. Create an account and verify your email. Supply your business name and email, open the verification email and set your password. Returning customers sign in to their workspace. A verified new account has one free baseline assessment of up to 5 systems; it does not automatically become a paid subscription.
2. Connect the services you use. Choose Connect AWS, Connect Microsoft, or both. Approve each provider in its sign-in/approval window and wait until Aevyra confirms it is connected. Keep all sources you want assessed selected.
3. Add websites and optional context. Add only websites you own or are authorized to manage and confirm the requested authorization. Optional business details personalize the explanation. Additional supported technical exports can supply evidence for checks the connections cannot establish.
4. Choose Show my results. Aevyra coordinates the selected collections, reports progress, seals the evidence and generates the action plan. A valid baseline or paid allowance and completed provider approvals are required. Signing in or remembering a connection does not itself start collection.
5. Read the action plan and act. Use the embedded report or Open full action plan. Review coverage and urgent findings, open an issue for its next steps, and reassess after changing your services.

AWS approval

Enter your own 12-digit AWS account ID and choose Connect AWS. An administrator authorized to create the workspace evidence role reviews the prefilled CloudFormation stack, acknowledges the requested IAM permissions and creates it. Return to Aevyra; role verification is automatic. Normal setup does not require copying policy text, External IDs or role ARNs.

A new workspace has its own authorization even if you connected that AWS account elsewhere. If a stack already exists, check the existing setup before starting another one. Read the AWS connection guide.

Microsoft approval

Choose Connect Microsoft and approve the requested permissions. If offered, Enable Microsoft security checks requests the additional administrator consent for those checks. Available capabilities depend on tenant permissions and Microsoft licensing. Your Aevyra account login, optional organizational SSO and Microsoft collection consent are separate.

Use both providers in one report

Connect both in the same workspace and keep both included. Aevyra keeps both in the source plan; connecting Microsoft does not replace AWS, or the reverse. You can explicitly exclude a source, but the resulting report then has a narrower scope.

What each source can check

Cloud configuration alone does not prove how employees use AI or that private information was disclosed. The report distinguishes findings supported by evidence from checks that need more information.

Optional additional evidence

Use the extra-information option only for supported technical exports. Do not upload raw private documents, AI conversations, passwords, private keys or payment-card details. When a customer-controlled Collector is offered, use only the approved package for your platform/release, verify its supplied integrity/signing information and follow its preview, consent and upload instructions. Collection provides evidence rather than a remote shell. Build tooling alone does not qualify a Windows/macOS download for distribution.

Resume or fix a collection

1. Read the source-specific error or missing permission. Confirm the provider account/tenant and approval status.
2. Resume saved work when offered. Connections and source selections belong to the workspace; a new workspace is a separate setup. Starting another run can consume another allowance.
3. Resolve the failed source and retry, or deliberately revise the selected scope. A failed required source prevents automatic completion of that selected source plan.
4. Before relying on a report, check its source scope, collection dates and missing-information sections. Missing evidence does not count as a pass.

Optional business context can personalize explanations without changing the underlying technical evidence. Completed assessments preserve their original evidence/results; later technical changes need a fresh assessment.

Try the demo

Choose Try the demo from sign-in, then use the public-demo sign-in and See example results. It uses simulated evidence and the same calculation/report layout. No customer AWS account, Microsoft tenant or visitor infrastructure is inspected. Optional context does not change the synthetic findings or score.

Read your security action plan

1. Check coverage first. The score describes supported checks with enough evidence, not all possible business risks. Unknowns are not passes.
2. Review urgent findings. Critical/High issues remain important even when the score is favorable. The protection score is an Aevyra index, not a probability of safety, NIST score or certification.
3. Use the charts and issue list. Select a chart slice, label, signal or category to filter the matching table. Open an issue for why it matters, what to do next and how to check the result.
4. Understand the units. Systems, checks, AI assessments and signal entries are different counts. Coverage is weighted across the three security areas; its headline percentage need not equal a simple fraction of the raw check counts. Read How this score works for the policy.
5. Review AI and business-impact context. Technical severity and estimated business impact/likelihood are separate. Scenario assumptions and missing inputs limit what a rating establishes.
6. Make changes and reassess. You or your authorized IT/service provider approves and implements the fix. Collect fresh evidence to verify the changed technical state.

The three areas are Protecting your data, Using AI safely and Protecting accounts and services. The detection-coverage catalogue explains remaining evidence requirements. Large reports disclose any interactive/CSV preview limits separately from full-population chart and score calculations.

Plans and billing

The verified-account free baseline is one assessment of up to 5 systems. Hosted paid subscriptions are monthly in USD and renew until canceled:

A system is a distinct assessed resource identifier, not an employee or a whole provider account. One provider account may contain many resources. The workspace shows current usage and allowance. Resume existing work when possible; new runs can consume additional allowance. Limits do not authorize an unaccepted overage charge or automatic upgrade.

Provider licenses and AWS/Microsoft usage charges are separate. Review Pricing and the recurring price, applicable taxes and purchase terms at Checkout. Signed payment confirmation activates the subscription; returning from Checkout is not itself confirmation. If activation is pending, refresh its status or contact support rather than buying a second subscription. A new paid billing period refreshes allowances after matching paid confirmation.

Manage billing provides the available invoices, payment-method and cancellation options. Scheduled cancellation retains access through the paid period. If a new tab has no active session, sign in again. Self-hosted or negotiated agreements may have different prices and rights.

Disconnect, cancel or request deletion

Contact david@tiptoptechknowlogy.com without credentials or raw customer evidence. See retention and deletion details, provider revocation details and Support.

Hosted and self-hosted responsibilities

Hosted customers manage account access, authorized scope, subscription and remediation decisions. Aevyra operates the hosted application. Self-hosted administrators also operate storage, identity, networking, monitoring, backups and updates; see the Self-hosting Guide. Available integrations, SSO and Collector downloads depend on the deployed release and configuration.