Skip to content
MuriOps

Getting started

User guide

The recommended path from a registered URL to a measurable improvement cycle.

  1. 01

    Register the project

    In Projects, enter a name and the public URL to analyze.

    • Use a URL you manage or are authorized to test.
    • Confirm the website is accessible without a private session.
    • The project provides context for analyses, applications and orchestrations.
  2. 02

    Run an analysis

    In Analyses, choose the project and verification type.

    • Standard QA Analysis covers UI/UX, performance, SEO, accessibility, console and network.
    • Security Analysis performs passive TLS/certificate, DNS, HTTP-header, cookie, CORS, exposed-file, HTTP-method and client-library version checks. It does not send attack payloads or replace a penetration test.
    • Wait for completion before comparing scores or creating an application.
  3. 03

    Review findings

    Open the report and assess priority, evidence and context.

    • Scores show trends; they do not replace reviewing each finding.
    • Filter issues by category, severity and status.
    • Review AI recommendations before applying them in production.
  4. 04

    Send to Application

    Convert the completed analysis into a remediation checklist.

    • Download the PDF plan for manual execution.
    • Use the universal bridge or MCP with your development tool.
    • Connect a platform only after understanding what its adapter actually writes.
  5. 05

    Reanalyze and track

    Measure the outcome of changes and continue the cycle.

    • Manual autonomy keeps checkpoints under your control.
    • Orchestration can resume after bridge items are completed.
    • Supervised and Autonomous modes are not available yet.