Who Secorvia fits, and who it does not
These pages are for deciding whether Secorvia suits your situation. Each one describes the reader it is for, what the product documents for that case, and where it does not fit, so you can rule it out quickly if it is the wrong tool.
Pick the situation closest to yours
Startups: a small team with no security hire and one or two cloud accounts, perhaps with a customer questionnaire on the desk. It covers what the free plan includes, a first afternoon with the product, and what you can show a customer.
Agencies and MSPs: you manage cloud accounts that belong to clients. It covers how separation between organizations works, access and roles, scheduled reporting, and the questions the documentation does not answer, so you can ask them before you commit.
Compliance: you need evidence for SOC 2, ISO 27001, CIS or NIST CSF. It covers how findings map to frameworks, how snapshots and reports build a record, and why that record is evidence and not a certification.
What the three have in common
Secorvia connects to AWS, Azure, Google Cloud and DigitalOcean with a read-only credential that you create, so nothing is installed in your accounts and it cannot change your environment. It reports problems and does not fix them, so someone on your side still makes the change and confirms it with a new scan. The integrations pages cover each connection in detail.
The free plan has no expiry and needs no credit card, and the plans differ mainly in how many accounts and users they allow and in which features they include. The pricing page has every limit.
If your situation is not listed
Three pages do not cover every team. If yours is different, the features page describes each capability in plain terms, and how it works follows an account from connection to the first list of fixes. If you are comparing products, the comparison and alternatives pages put Secorvia next to others, including where they are better.